OIPA Release Notes 12.1.0.0
Oracle Insurance Policy Administration (OIPA) is a next-generation, flexible, rules-based insurance solution for life and annuities that supports policy processing across multiple lines of business. OIPA greatly enhances the ease of use and speed for business analysts, actuaries and others involved in the product configuration process. Robust navigation also makes it easy for users, including CSRs, to locate policy information and drill down into a granular level of customer detail. This allows insurers to respond more rapidly to customer inquiries, reduce call times and improve customer service. These release notes contain the enhancements made to Oracle Insurance Policy Administration release 12.1.0.0.
Oracle Insurance Policy Administration
This section describes configuration, features and technology specific enhancements for GA release 12.1.0.0. OIPA now supports the following functionality:
Enhanced Audit Capabilities for Client Phone Records
OIPA now tracks the complete history of client phone number changes, improving auditability and data transparency. A new History tab has been added to the client phone screen to display all additions, updates, and deletions made to a client’s phone details. This ensures every phone record change—whether made through an activity, web service, or ABR such as createPhone or copyToPhoneFields is recorded for full traceability. Two new database tables, AsPhoneHistory and AsPhoneHistoryDetails, support this enhanced audit trail. This feature strengthens data transparency and compliance by providing a clear audit trail of client contact updates.
Consolidated Accounting View for Activity Results
Users can now configure multiple accounting result field entries to appear under a single column in the Accounting tab of the Activity Result screen. This improvement simplifies the financial review process by consolidating related data points into a unified view. The enhancement introduces the <QueryPart> element in the Table component of the Activity Result business rule, enabling flexible data operations such as COALESCE, CONCATENATE, CASE, NVL/ISNULL, and IIF. This allows users to combine or conditionally display values, making accounting data easier to interpret and manage. This change provides flexibility, simplifies financial review and improves clarity by consolidating key accounting information in one place.
Improved Copy Functionality for Agreement Class Groups
A new copyAgreementClassGroup option is now available on the agreementClassGroup screen, resolving previous limitations in copying class groups. This enhancement improves efficiency by allowing users to duplicate agreement configurations seamlessly, reducing manual setup and potential errors.
OptionText Support for Multifield Spawns
The Multifields spawn configuration now supports OptionText for combo boxes and radio buttons. This usability enhancement ensures that spawned activities display descriptive option labels.
Enhanced Group Plan Fund Management
Group Plan Fund management has been significantly improved to give users greater control over plan level fund selection and security. A new Plan Funds tab is introduced, allowing business users to define and manage Group Plan Funds by selecting from Product level funds. The enhancement ensures data accuracy through validations preventing fund removal if active allocations exist and introduces a PlanSliceGUID column to track historical fund modifications. Enhanced security through the PlanFundGroup page ensures only authorized users can access Plan Funds and Allocation tabs, providing stronger governance and compliance control. This enhancement provides greater flexibility and control in managing plan level investments, reducing configuration errors and enhancing data security.
Redesigned Activity Detail Screen for Group Bill Management
This release enhances the Billing tab of Activities Results screen with an improved, tab-based interface that replaces the earlier section expander design. The new layout introduces a Billing tab with a search filter and Find and Clear buttons, enabling users to quickly locate and manage specific bill line items.
These enhancements significantly improve usability and navigation, especially when handling large billing datasets, allowing group customer users to review, filter, and manage group and member billing information more efficiently.
Status Filter on Requirements Screen
The Requirements screen now includes a Status Filter at both the Application and Policy levels. This enhancement allows users to filter and view requirements based on their current status, streamlining the review process and improving visibility into pending or completed items. Users can filter by one or multiple statuses, or view all requirements by default.
Workflow Task Generation at Group Customer Level
OIPA now supports generating Workflow Tasks at the Group Customer level, in addition to existing Client and Policy contexts. Tasks can be generated both manually and automatically (via Cycle, DI, AsFile, or user-initiated actions), enabling better tracking and management of customer-related workflows across the application.
Configurable Default View in Impairment Summary Screen
The Impairment Summary screen now allows configuration of default filters for Level and Category. This flexibility enables organizations to tailor their default view to display only relevant impairment data. Supporting codes for 'ALL' values have been added to AsCode table under codeNames - asCodeImpairmentLevel and asCodeImpairmentCategory, making configuration more adaptable to business needs.
New Codes for AsCodeImpairmentLevel and AsCodeImpairmentCategory to support the value 'ALL' are added to AsCode table.
| S.no | Code Name | System Indicator | Value | Definition | Short Description | Long Description |
| 1 | AsCodeImpairmentLevel | Y | ALL | It encompasses all the three levels of Impairments | ALL | Includes all the three levels of Impairments |
| 2 | AsCodeImpairmentCategory | Y | ALL | It encompasses all the defined impairment categories | ALL | Includes all the impairment categories |
Encryption Key Management
In earlier releases, the OIPA application stored encryption keys in two separate locations — one part in a .dat file (as defined by the encryptDecryptFilePath parameter in the PAS.Properties file) and the other in the AsEncryptiondatabase table.
Starting with this release, both keys are consolidated into a single PKCS12 keystore (oipakeystore.p12), which is password protected. This unified keystore is now used for all encryption and decryption operations, improving security, simplifying key management, and reducing configuration complexity.
