Tag: May 2017

Siebel and Oracle Policy Automation May 2017 – In (em)bed together

Siebel and Oracle Policy Automation  12 May 2017 – In (em)bed together

Siebel and Oracle Policy Automation 12 May 2017 : Since the release of Oracle Policy Automation May 2017 edition, teams of Siebel developers are breathing a sigh of relief. Finally, Oracle Policy Automation can fully integrate into the Siebel Open UI JavaScript API thanks to the arrival of it’s own Extension API.

It does not take long to compare the advantages of this Siebel and Oracle Policy Automation integration method :

  1. No longer having to use the static HTML file-based integration that was proposed in Siebel Innovation Pack 15.5 and above. This means that all the native Oracle Policy Modeling components (sliders, image controls, explanations, Form downloads just to name a few) can be displayed in Siebel Applets or any other element you can imagine in the Siebel Open UI object model (I’m thinking Plugin Wrappers and so on)
  2. Allowing the Oracle Policy Modeling users to concentrate on optimizing the experience and the Siebel Developers to concentrate on delivering the data model to Oracle Policy Modeling. Separation of concerns
  3. Avoiding IFRAME. Always a good thing.
  4. Implementing different Physical Renderers depending on user situation – perhaps to display the Oracle Policy Automation Interview in a jQuery Dialog if the screen is big enough, otherwise using the full Siebel Applet
  5. Potentially creating a Presentation Model with User Properties to allow Siebel Developers to pass properties into the JavaScript API which then can be used to implement some logic on the middle layer – perhaps passing the Rulebase name into a generic Applet.

It doesn’t really matter if you are not a Siebel person, this opens up a lot of great possibilities. Here are some of the basic steps

    1. Find a Form Applet in Siebel that you want to show an Interview from Oracle Policy Automation in. Using Duncan Ford’s template generator, create an empty Physical Renderer for a Form Applet. This is the starting point for any integration using Siebel and Oracle Policy Automation 12 May 2017 Extension API.
    2. Populate the ShowUI Framework hook with your code to inject the Oracle Policy Automation interview into an available <SPAN> or just make space for yourself. You will want to write much tidier code than this example, but you can get the idea – select, inject.

Siebel and Oracle Policy Automation 12 May 2017 - ShowUI

    1. Add the new Physical Renderer to the Manifest, along with any other files that you downloaded (if you are referencing statics copies of the interviews.js and the CSS files for example)
    2. Restart Siebel and navigate to the View with your Applet in it.

Siebel and Oracle Policy Automation 12 May 2017 Embedded

No IFRAME, no HTML files. Just the magic of the new Extension API. It’s breathed new life into Siebel and Oracle Policy Automation.


Oracle Policy Automation May 2017 – New Features #5

Oracle Policy Automation May 2017 – New Features #5

In every release of Oracle Policy Automation there are stand-out features. Already in this series about Oracle Policy Automation May 2017 we have seen so many great features :-

  • PDF Templates for Forms
  • Dynamic List Values
  • Styling via The JavaScript Extension API
  • Control Extensions via The JavaScript Extension API

For this, the fifth post in the series about Oracle Policy Automation May 2017 we have definitely arrived at a major, triumphant upgrade in functionality. Finally we are able to embed our interviews without the use of the hated IFRAME tag. For too long we have been stymied by the use of an outdated, unresponsive and frankly quite horrible tag to get our great interviews into existing website content. The JavaScript extension that we looked at in videos three and four in this series once again comes into play, and using a simple technique redolent of jQuery we embed the interview in a DIV tag.

To accompany this new feature we also have two pieces of required infrastructure : firstly the style sheets and JavaScript files to support the embedding, and secondly the new administration feature in the Oracle Policy Automation Hub, whereby we can add the required external sites to our “Authorized” list, thereby removing Cross Origin scripting issues from the browser and ensuring the functionality works smoothly.

Oracle Policy Automation May 2017- CORS

In the video that accompanies this article, you will discover the basic structure of an example HTML file, observe live debugging and updating of the “Authorized” list and lastly you can watch my jubilation as the interview kicks off in my embedded DIV without a single IFRAME in site. I look forward to helping my clients move away from the various hacks and other cosmetic touches to hide an IFRAME to a more modern, JavaScript extension-based approach.

For more videos you can check out our Video Gallery. The other posts in this series concerning Oracle Policy Automation May 2017  are parts 1, 2, 3 and 4.

Oracle Policy Automation May 2017 – New Features #4

Oracle Policy Automation May 2017 – New Features #4

Oracle Policy Automation May 2017 – New Features #4

Following on from the previous post, in this third video about the Oracle Policy Automation May 2017 – New Features, we look at a functionality that is actually making a comeback. In Oracle Policy Modeling version 10, it was possible to hide or show values in lists (for example, a drop down control on an Interview Screen) based on a Boolean attribute value. This was shelved in version 12 but now it makes a welcome return in May 2017.

The functionality is easy to implement, and simply requires a Value List, a Drop Down control or similar, and some logic to power the decision whether to display a value or not. The display of each value, including uncertain can be powered by the same or a different Boolean attribute.

The functionality extends the Interview experience by allowing for a better user experience and an easier manner than jQuery or some such client-side smoke and mirrors to implement a state model or logical transition model within the Oracle Policy Modeling environment. The video that follows this article walks through a simple example and hopefully shows you the way. Catch up with the other tutorials and videos in this series in the links below

Whats New May 2017 Part One

Whats New May 2017 Part Two

Whats New May 2017 Part Three

The Walkthrough Video

Oracle Policy Automation May 2017 – New Features #3

Oracle Policy Automation May 2017 – New Features #3

Following on from the previous post, in this third video about the Oracle Policy Automation May 2017 New Features, we look briefly at the second capability of the JavaScript extension API. Yesterday I looked at custom styling, and today we look at custom rendering. Providing a more robust and upgrade-proof framework for customized interview experiences, it can be used to modify the behavior of labels, input boxes and other controls as well as major elements like the header or the navigation elements of the interview. There are a few examples of the new API in the Example Projects, but I found that they did not really explain to a neophyte how this works!

The API provides for several event handlers, to manage the life cycle of the DOM and your custom control renderer. In addition there are a raft of interesting Methods available to get property values such as the current value of the control, or the control type and so forth.

Oracle Policy Automation May 2017

The format of the JavaScript file will have a structure very similar to the previous example, essentially a JavaScript Object using a familiar notation. In future videos we will investigate further controls but in this first demonstration of the Oracle Policy Automation May 2017 New Features we will produce a custom renderer for the Labels in our interview.

In the example, we will use three of the four handlers available, and demonstrate how the API provides enough information to enable us to quickly add our rendering engine to the Interview.

You can find the YouTube Playlist for these videos here. The next post in this Oracle Policy Automation May 2017 series will look at the return of dynamic values in lists, as well as the (most welcome) capability to embed interviews in something other than an IFRAME. See you soon for more!

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!

Oracle Policy Automation May 2017 – New Features #1

Oracle Policy Automation May 2017 – New Features #1

As you may have noticed the latest version of Oracle Policy Automation has hit the virtual shelves. And so, in the fine tradition of the OPA Hub Website, we are going to be reviewing some of these new features.

The first subject is an easy one – the ability to add and work with PDF files as Forms, as well as the traditional RTF files. The workflow is exactly the same – create attributes, give them public names, write rules, then bind explanations to the Form in the Project Tab, Form Pane before opening the Form in your chosen Editor – Word for BI Publisher Desktop, or any PDF Form editor. Clearly Acrobat Reader will not do the job.

The new possibility is accompanied by a new PDF Form Assistant, that looks a little like the screenshot you can see here – notice the ability to select Fields or Explanations, Repeating Fields and so forth to add to the PDF document you are building.

OPA - PDF Form Assistant

For those of you that prefer to watch a walk-through video, we have that too. Just click on the video at the end of the post and see the OPA Hub Website running through a quick PDF Form creation with an example Project as a sort of mini OPA tutorial, with as a bonus some magic disappearing menu items. There will be more about Oracle Policy Automation May 2017 in the next few posts here on the OPA Hub Website.



GA release of Oracle Policy Automation May 2017 (12.2.7)

GA release of Oracle Policy Automation May 2017 (12.2.7)

The latest and greatest version of Oracle Policy Automation has just been posted on the relevant Internet sites for download and installation (in the case of Public Cloud of course you would be either on the published schedule for upgrade, our you can use your Cloud Administration to move up.)

There are some cracking new features in this Oracle Policy Automation May 2017 release which we will be covering here are usual. To whet your appetite here is a little list of the highlights:

PDF form templates
Form templates can now be maintained as PDF files. This might be the beginning of the end of the BI Publisher Desktop as the chosen tool for building PDFs.

Interview extensions
JavaScript-based extensions are back with a much improved strategy for ensuring they are upgradeable!

Embeddable interviews
IFRAME begone! Now we can embed interviews without the hated IFRAME tag. End of “Trusted Sites” and other nasty issues in older browsers (Internet Explorer I’m looking at you). This included support for authorizations as to where you can embed the interview.

Batch Assess REST API
A new REST API for Batch Assessments. About time!

Some more things to get excited about:

    • Mark test cases as passed or failed with an extra column in the Excel file
    • Conditionally show individual items in a value list – The return of conditional list items. Make a drop-down list entry show or not based on logic. A welcome return!
    • Show controls on a screen only when they are relevant – Awesome flexibility to help screens that have many questions or have lots of flexibility in the pertinence of questions.
    • Forms can now open inline or in another window. (man, I could have done with that a few weeks ago!)

Watch this space for our articles reviewing the functionality!

Logo by Southpaw Projects LLC