# Required Manual Configuration Updates

## Presentation of Accounting information resulting from Activity processing

With the 12.0.1.0 release, the Accounting data table and its exchange data presented in an Activity’s Accounting tab becomes configurable. This requires configuration in the ActivityResultsScreen business rule that is attached to the transaction’s definition. The existence of the Accounting configuration in the rule triggers the new behavior. Without this configuration, past behavior continues.

## Activity Archiving

OIPA can process a large volume of Activities with each Activity storing the results of calculations and documenting updates to various entities. Over many years the Activity data has grown larger than practically needed for daily processing and relevant research into business issues. To alleviate the issue, user can archive the Activity data by initiating a REST API. The request payload must indicate an archival entity (Client Activities, Policy Activities, or both) and an Effective Date. All Activities from the requested entity or entities, and their data from 24 related tables, dated for the Effective Date and earlier are copied to a customer’s designated archival database and then removed from OIPA’s database. Some activity data is retained in OIPA to properly display the entity’s historical progression of Activity processing, however archived Activities will not retain full details to accurately display the Activity’s results and updates. Since all Activity details no longer reside in OIPA’s database, they can no longer participate in Activity processing. Therefore, the choice of Effective Date value should be far enough in the past so that there is little need for Activity processing near the archived Activities. OIPA will prevent users and processes from attempting to insert Activities on and before the Effective Date of an archived Activity. For more information refer to the Archival and Retrieval REST API documentation.

The upgrade to 12.0.1.0 includes database changes that support Activity status maintenance through the archival feature. The Upgrade Utility will assist with added data and the creation of new tables. However, the customer’s configuration may need to be manually reconfigured due to new Activity statuses. The logic needing re-configuration cannot be systematically discovered and modified by the Upgrade Utility. This will include customer configuration that filters or identifies Activities by status value. The result of such configuration cannot lead to an Activity’s re-processing or modification if it is archived or pending archival.

## Requirement Processing on Updating Requirement Field

The math contained within Requirements and their attached business rules are executed when the Requirement’s status is updated. There are scenarios when the math and attached rules should be executed after any of the Requirement’s fields are modified. The ability to execute a Requirement’s processing upon any Requirement field update becomes OIPA’s default behavior in 12.0.1.0.

A new PAS property, executeRequirementOnAllStateChanges, controls this by switching between the old and new behaviors.

No: It will retain the older behavior of processing a Requirement only when its Status has changed.

Yes: It will process a Requirement with a change to its field’s values, including Status.

With the latter behavior becoming the default behavior, existing user may desire the older behavior and add the new PAS property with a No value.

## Removing BOLD and ITALIC visual impact to comply with Redwood standards

Oracle’s Redwood UI standard has been applied to all OIPA pages. The standard does not allow individual screen fields, their values, or the values in columnar data to be bold or italic. Configuration that defines the BOLD and ITALIC attributes on field-oriented and column-oriented data are ignored by this release and will not cause exceptions. These attributes can be removed from configuration, at a customer’s desired pace, and over time provide a consistent definition reflective of OIPA’s actual behavior.

| Copyright © 2025, Oracle and/or its affiliates. All rights reserved. | About Oracle Insurance | Customer Support