The Oracle Policy Automation (OPA) team is pleased to announce that OPA Release 17D (12.2.9) is now available for both public and private cloud customers.
As usual, we have included many features and enhancements requested by customers and partners. The three headlines features for this release are:
Dynamic reference data loading: OPA now supports the loading of any additional data from Service Cloud or the connected application, even if it is unrelated to the contact, opportunity and so on for the interview. You can define conditions for which reference data items to load, using filters and rules. Data is retrieved automatically during an interview session, as soon as the specified conditions are met.
Sales and Engagement Cloud interview styling: A Sales and Engagement Cloud interview theme option is now provided so that OPA interviews that are embedded in Sales and Engagement Cloud can have a consistent look and feel. The styling matches the default Sales and Engagement Cloud styling and can be easily updated as needed to match the actual Sales and Engagement Cloud theme configuration. The default styling changes the appearance of buttons, puts buttons inline with the navigation bar, moves question text beside the control, and more.
Identity Cloud Service integration: The OPA Hub user life-cycle can now be centrally administered through a linked Identity Cloud Service tenancy. This provides Single Sign-On for OPA Hub users, including authoring, administration, mobile and API user roles. (Fine-grained permissions are still managed within the OPA Hub administration experience.)
Configure submitted form name and location: OPA has simplified the finding and identifying of generated forms in connected applications. Interview designers can now configure the generated form name and have attachments saved to any entity. For example, if multiple opportunities are created, a summary document could be generated and added to each one.
Easily debug generated forms: Interview designers can now easily ensure the correct appearance and behavior of uploaded documents. The Debugger shows which forms will be attached on submit, and enables uploaded forms to be previewed directly.
Round-trip test case debugging: Testers can now navigate from a test case to the Oracle Policy Modeling Debugger and back again. When launching the Debugger from a test case you can see which test case is being debugged, and while debugging you can navigate back to where a test case value is defined.
Provide names for screen layout containers: To simplify the maintenance of nested interview layouts, meaningful container names can now be added to explain their purpose and how they contribute to the screen layout.
Collect global/parent data on entity screens: Interview designers can now add Global (parent) entity content to entity-level screens. This could be used to collect data for global and parent entities on multiple screens, for example, so that the user could update certain data (like product choices or notes) on every screen of an interview.
Change language during an interview: The user interface language of an interview can now be changed at any time. This is done through the inclusion of a change language button in the header or footer (or both) of the interview. This can simplify the integration of multi-language interviews into customer portals. This feature also works with interview extensions.
Show icons for optional questions: When optional questions are less frequent than mandatory ones, a visual indicator of only the optional questions can be used to simplify the interview experience.
Set attribute values in resumesession URL: You can now specify that reviews or other special behavior should be triggered when an interview is resumed. For example, if an interview is being resumed more than 14 days after it was started, you could require the interview user to reconfirm their previously provided answers.
Seed entity level data via startsession URL: Using the startsession URL you can now pre-populate entity collections or provide some dynamic reference data when an interview is launched.
Set default channels for any collection: Hub Administrators can now specify the default channels for any collection. This eliminates the need to manually reconfigure every new deployment to use the correct channels. There is also the option to lock the channels for existing deployments.
If and Default rule functions: Several new rule functions have been added that can be used to simplify rules.
Faster migration of Word documents from 10.4: OPA 10.4 projects containing large rule documents can now be migrated to OPA version 12 quickly, enabling the migration to be repeated if necessary.
Public cloud: You can upgrade your testing sites at any time via Oracle Cloud Portal Service Cloud Configuration Assistant. All sites will be automatically upgraded according to the published schedule.
A summary presentation of the key features and benefits in this release can also be found on OTN.