10 ways to get the most out of substitution in Intelligent Advisor #2 #3 and #4

So here we are with the next part in this series, and I bet that at least one of the substitution techniques you are going to see is maybe new to you, or you’ve forgotten about it. So here goes. We will use the same basic project as last time, with some minor tweaks just to have some more examples. Here is the data model:

Data Model for the following examples

We want to find out how much people spent, and whether they are eligible for a discount because of their loyalty. There are three discount levels : gold, silver and zero (nothing). We calculate that based on customer spend in the last year. No need to go over that part.

So now we want to look at the three examples of substitution. Let’s start with the one everyone (hopefully) knows. A label on a Screen. In this case, the Screen is using the person as the entity context, so it makes sense to display the person’s name when entering purchases for a given person. So this is number two in our top ten, but probably everyone has this one at the top of their list:

Screen using the person as the screen entity and a suitable substitution.
That’s what it looks like at runtime.

Now the second example. We want to have an explanation to show the interview user why (or why not) the customer obtained a discount. We have a Boolean for that.

Explanation in a Screen showing a Boolean attribute for which we want to display the decision report.

So far so good. But our discount is a different attribute:

Example discount rule for our explanation

And we want to have an explanation on the Screen. Well, we end up with two, because we have two attributes. That’s not friendly at all. So just give the explanation control an extra substitution. Maybe you didn’t think to do that before:

Explanation control with two substitutions

And it all looks better now, and we only need one explanation:

The third and final one is still looking at the explanation. First let’s add some details to the child entity instances:

Some data in our child entity

The detail of the explanation sucks when you look at it:

Those phrases like “” and “” are really not friendly at all. “The price of Hat is £200.00” – who says stuff like that? So what can we do? We can edit the text used for the attribute and that can contain substitutions too:

Customizing text in the Attribute Details

Of course one has to use these features wisely, but that makes three more uses of substitution. So now our explanation looks much better (We also used the Explanation Options to hide some lines for brevity).

So, did you know them all? See you soon for the next post in this series…in the meantime you can read more about substitutions in the online documentation.

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

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