Note: This is regarding the deprecation date for TLS 1.0 on cx.rightnow.com. The deprecation date for your instance(s) of Oracle Service Cloud may be different and has been communicated to your site administrators via email.
What is new in Oracle Policy Automation February 2017?
Oracle Policy Automation (OPA), new features
Do you have a deployed project created in an earlier version? There are a few things you should check.
The February 2017 release of Oracle Policy Automation Cloud Service includes:
Service Cloud connection enhancements
New capabilities allow various users – including anonymous users, logged in customers, and call center agents – to use the same Oracle Policy Automation (OPA) interview definition. Using this feature, call center agents can use the exact same interviews that are used anonymously by Contacts that don’t yet have a Customer Portal login. For example, a loan advisor experience that creates an opportunity in Service Cloud can be used by both self-service users and agents. Interviews can create a new Contact record for anonymous users if needed. This allows central management of these experiences, simplifying upgrades and ensuring consistency across all customer interactions. For more information, see:
Custom lists of values can now be centrally maintained in Service Cloud and used to define selections in OPA interviews (and other customer and agent experiences). When a policy model is deployed, the latest list of values is used. For more information, see:
OPA interviews will now work in cloned Service Cloud sites without any manual widget updates required. That is, the February 2017 OPA widget automatically builds the correct OPA interview startsession URLs for the connected OPA site, and uses an automatically configured shared secret. For more information, see:
Enhanced user management
There is a new integration user account type in OPA Hub, designed for application integration. The integration user account type supports automated deployment, non-interactive use of Determinations API and user synchronization. For more information, see:
OPA Hub can now use an external identity provider to authenticate users that login interactively via Oracle Policy Modeling, the OPA Hub user interface and the OPA mobile app. This feature is only available to OPA private cloud customers. For more information, see:
Export project data model
OPA now has the capability to export to CSV files some or all of the attributes that define a project’s data model. Detailed entity and relationship information is also provided. This allows users to review and analyze attribute metadata using external quality tools, for example, to validate mappings, attribute names, explanation options or any other data attribute settings in an OPA project. Integration tools can also be developed that auto-configure middleware or mapping interfaces to conform to the data model of deployed policies. For more information, see:
Browse entity and relationship usage
The Data view in Policy Modeling now shows inferred entities in italic text to make them easily identifiable. Also in the Data view, you can right-click any entity or relationship to see and navigate to the rules and screens that use the entity or relationship in the policy model. For more information, see:
Use images on sliders
Images can now be used for values on a slider input control. This has the benefit of reducing on-screen text, and can be especially suitable for mobile experiences and non-native language users. For more information, see:
Restrict uploads by file extension
Interview authors can now restrict which file extensions are permitted on upload controls. This can be used to ensure that interview users only upload appropriate file types, for example, images and documents). For more information, see:
Optional prompt when leaving unsaved interviews
To ensure interview users don’t accidentally lose unsaved data they have entered, interview designers can now turn on a warning that will be shown to users when they try to restart or exit an interview (or close the browser window) that has unsaved data. For more information, see:
RuleScript now supported in Java 8 environments
It is now possible to develop and deploy Policy Modeling projects containing RuleScript on environments using Java 8. For more information, see:
For a list of issues addressed in this release, see the Policy Automation Change History (Active customers only).
Would you like help collecting this information?Yes, let's chat!