And so the wheel of time turns and before we know it, yet another version of Intelligent Advisor has hit the shelves. And this one is a big release, with some fantastic stuff in it, not just for Interview fans but also for those of us who are focussed on REST Services, performance and testing. So what’s new?
So, here is what’s new in Intelligent Advisor 20C. Let’s begin with the Interview Extensions. There are new extensions that help us format the styling for portait entity containers and entity collects. They have styling extension names like portraitContainer and (as child elements of the container) headerCell, row, rowOdd, rowEven and so forth. Some of these were introduced in the second monthly update to 20B but they are so fresh it’s worth mentioning them. They can easily produce nice effects. Here are some of them in techicolor, namely dynamic Buttons, Column Headers and Row colors.
That bunch of things would be enough to get me really excited, but there is a LOT more. For a while now I’ve been militantly asking for functionality where my customers can begin to profile their rules, get performance statistics and execution time data.
Now they can – firstly, directly through Intelligent Advisor REST calls (using the Batch API) via the addition of @time per case as well as processorCasesPerSec and processorQueuedSec in the REST response. This is fantastic for understanding what’s going on with cases in Batch.
Secondly the users of Policy Modeling can now leverage new functionality and obtain statistics from a set of Test Cases in Excel format or from a JSON batch request. For Test Case output, reports and timings (in CSV) are generated automatically and stored in a new TestLogs folder. As development continues, these CSV files will be good sources of information to understand where added rules or entities are causing a slowdown.
Thirdly, they can also delve into the details of execution times via a JSON batch request analysis. For example, shown below is the generation of the rule profiling report obtained by loading a JSON data set into Policy Modeling on the Test Cases tab via the new Analyze Batch Request button.
In summary, for performance hunters there are now 3 useful areas : batch execution timing, test case execution reporting and finally sample batch profiling.
But that is not all! There is an important accessibility enhancement – the ability to flag a control as leveraging the browser’s native auto-fill capability. Select the Screen Control and set the properties :
On the Hub there is a new feature called repository branching to allow copying of a project in the Repository directly on the Hub to create a visible relationship between the source and the new one. If you have ever had to create copies of projects to represent different strands of development or testing, this will be welcome.
When viewing (in either direction) you can see where the project has been branched / is the root of a branch:
There are other new features, notably a component versioning system that becomes apparent when viewing the new release in OPM. The product version might be 12.2.20.X but the component version is 42.0.0. Separation has occured so that the product can evolve at a different rate to the component version. The “component” of which they speak is the core interface between Policy Modeling and the Hub. In light of some of the potential functionality on the roadmap, it makes sense to separate the two.
This release is a big one, no doubt about it. Not just for the new features which bring proper instrumentation and profiling to Intelligent Advisor – which was overdue – but also for the new Interview Extension features. The other elements are laying the groundwork for yet more new features in the future. Read the online notes here.
Have a good day.