Oracle Policy Automation May 2017 – New Features #2

Oracle Policy Automation May 2017 – New Features #2

Following on from the first article in this series, which dealt with the new features in respect of PDF Forms and using PDF as the basic template instead of an RTF File for use with Oracle BI Publisher, this second video from the Oracle Policy Automation May 2017 – New Features series looks at the enhancements around JavaScript.

To be more specific, this video looks at the use of JavaScript to handle styling of interviews or controls on screens. Unlike previous iterations, this new version manages the process in a much more robust and upgrade-friendly way. Gone are the jumble of JavaScript files, to be replaced by JavaScript Extensions of the Oracle Policy Automation space. You will be using JavaScript objects to define the styling attributes of your controls or interviews.

There are a couple of pitfalls along the way which I draw attention to – not necessarily bad things, just points to be aware of when you begin using this styling technique. In a later video I will look at using the same Extension concept to move beyond styling into actual customizing of controls with handlers and so forth. The official documentation regarding Styling Extensions can be found online, at this address at time of writing.

Oracle Policy Automation May 2017 JavaScript Extensions

I’m very pleased to see the return of this functionality, in a much improved, more industrial grade framework. Until the next article, enjoy the video and Oracle Policy Automation May 2017 New Features Part Two.


In the next articles we will look at JavaScript Extensions again, and then the new features around dynamic values in selection lists (back to the future again!). Until then, have fun!

Richard Napier

Author: Richard Napier

After 8 years in case management and ERP software roles, Richard Napier joined Siebel Systems in 1999 and took up the role of managing the nascent Siebel University in Southern Europe. He subsequently was Director of Business Development and Education for InFact Group (now part of Business & Decisions) for 8 years. He now runs Intelligent Advisor IT Consulting OÜ. Owner of, he also is Co-Founder of the Siebel Hub.

2 thoughts on “Oracle Policy Automation May 2017 – New Features #2

  1. Hi Richard,
    I had a query on custom styling. I wanted to hide a particular label on the screen during on load. For e.g. My Label had text – “Random text ” and I wrote a simple styling as below

    style: {
    label: function(control) {
    return {
    style :{

    The below styling works perfectly in the browser however in the standalone debugger entire screen is showing blank. I am not able to understand why the debugger and browser debugger is showing different behavior.

    1. Hi. Thanks for your message. Here is the reason, and I have a question in return. The embedded Browser in the Debugger is IE11. If you open your Interview in IE11 (not Edge) outside the Debugger you get exactly the same thing : a blank screen. So whatever the issue is, has little to do with the Debugger and a lot to do with IE11. When I try to run the interview in IE11 I see an error in the Console. It says “Object doesn’t support property or method ‘includes'” and indeed if you look up the Internet, you will see that IE11 does not support includes() for Strings.( so there is your answer. It will not work in IE11.

      My second point, and it is really a question, is this : can you not find a way to use the standard, non-JavaScript “Show / Hide If” functionality on the Label, based on attributes of the Project? Just asking…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Intelligent Advisor IT Consulting Serving Customers Worldwide
Hide picture