Policy Automation – Translations, HTML and Substitutions Ideas

Policy Automation offers rule designers several ways to personalize a Web Determination session, the goal being to make the interview more streamlined and friendly.  This post is a continuation of a discussion about substitutions during a recent training.

Settings on the Attribute to handle minimum and maximum and regular expression validation.

OPA - Attributes

Settings on the Screens used to collect information:

OPA -Screen

Screen Order and Screen Flows to Control Logic:

OPA - Screen Flow and Subflow

Obviously as these grow more complex and your interview becomes more involved, the need to manage any translations of your rulebase becomes ever more important. Policy Automation provides the easy Translation File system to let you manage the translations of your rulebase questions and texts.

OPA - Translation

The warning message let’s us know that there are some strings used in the Excel Translation File that have not been translated. This can be quite confusing. Obviously most translations are obvious in the file, for example:

OPA - Excel File Translation Example

But even after going through all the texts, you might still get the warning message and wonder why. That is because even if something is not really translatable, then you need to either translate it anyway or mark it to be ignored. Consider the following example:

OPA - Ignore Translation Example

The car manufacturers included in the dropdown list are not required to be translated – they are to stand as-is. Then you should mark them to be ignored using the relevant button as shown in the example, and the text will change color as demonstrated.

As you add more Question Screens to your interview, the output in the Assessment Summary will become progressively less readable, especially in the case of an interview involving multiple records for multiple entities, as shown below.

OPA - Assessment Summary

By judiciously adding Labels and Folders to your Summary Screen, as well as substitution to your Translations and a little bit of HTML you can quickly come up with something more readable.

OPA - Assessment Summary Edited

This gives the following output:

OPA - Assessment Summary Improved

Further addition of substitution can improve it even further with  minimal effort.

OPA - Substitutions Galore

This in turn will improve the output of the Decision Report as well as our Assessment Summary of course. For instance clicking on the “Why?” next to “The mechanic does not have more than 3 cars waiting” in Janet’s section gives the following display.

OPA - Decision Report First Try

But we should be mindful of the performance impact of large amounts of information in the Decision Report, since it might be destined to be integrated with Siebel CRM or saved as a file. So we can return to our Attributes and change the Decision Report settings to either Invisible (it disappears) or Silent (it hides the providing Attributes). The options for Relationships and Attributes are slightly different:

Which gives us the slimmed down version below:

OPA - Decision Report Final

Working to reduce the amount of static text through substitution, maintaining an updated Translation file and managing your Decision Report output can improve the user experience, reduce overhead and clarify your interview. Until next time!

More on this topic

Substitution and the 2nd person in Intelligent Advisor 12

LOVs and Translations in Intelligent Advisor 12

Decision Reports in Intelligent Advisor 10 and 12

Author: Richard Napier

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 intelligent-advisor.com, he also is Co-Founder of the Siebel Hub.

Logo by Southpaw Projects LLC