The Oracle Policy Automation (OPA) team is pleased to announce that OPA Release 18D (12.2.13) is now available for public and private cloud customers.
File uploads can now be organized into categories (upload groups). You can configure interview upload behavior by choosing the maximum number of files, the prefix of uploaded files, the allowed file extensions and the object to associate with each upload group. This provides intuitive upload experiences for interview users by clearly nominating the number and type of evidence files and other supporting documents that must be provided. It also makes it easier for agents to find the right files via the use of meaningful prefixes, that are independent from the name of the file uploaded by the end user.
These enhancements are supported by Connector Framework v12.2.13, and work with any Oracle Service Cloud version (Engagement Cloud support is not yet available).
Note that for existing projects, an upload group is created on upgrade for each entity with an upload control.
OPA 18D allows you to use the existing version of Policy Modeling to update deployments, even when Policy Automation Hub is a newer version. This means that enterprises can roll out new Policy Modeling versions across desktops on their own timetable, and users can confidently work on and deploy new versions of OPA projects even during critical project phases. This is particularly beneficial for projects that are being used by a specific version of OPA mobile app or SDK, ensuring maximum compatibility and enabling enterprises to set their own mobile app update schedule.
You can choose to defer the download of a new Policy Modeling version available from Policy Automation Hub, and also turn off requests to upgrade particular projects to a newer Policy Modeling version, all while continuing to work with existing projects.
This enhancement allows client certificates to be uploaded to Policy Automation Hub, and for OPA connections to be configured to present a particular certificate when they make calls to a customer’s web service connection. Customers provide a web service connection endpoint to OPA so that interviews can load and update often sensitive data on behalf of an authenticated end user. Client authentication (two-way SSL) ensures that calls to these configured web service connector endpoints can only be performed by OPA sites to which the customer has explicitly granted permission (by uploading the client certificate).
The OPA Hub REST API can be used to manage client certificates.
Forms using collected data and decisions made can now be generated when an OPA mobile assessment is submitted to Oracle Service Cloud. You can choose which Service Cloud object to attach the forms to, just like for online OPA web interviews.
OPA now provides a simple text only control for date and time entry. This interface complies with UK government standards. Interview extensions can be used to enhance the style of these controls.
The appearance of tabular entity collection controls and containers can now be altered using interview styling extensions. This enables interviews to meet design requirements when collecting and displaying data rows.
The same form can now be generated for more than one entity in a single interview, and saved to the connected application on submit. For example, a document can be generated for both parent and child records. In this way, the audit trail can be captured and forms processed on all the required business objects.
A working example of how to do user-friendly text length validation using interview extensions has been added to the documentation.
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.