Jarvis Pizzeria: Summary of a Decision Model Use Case

We have written a blog series of 6 posts describing a Decision Model Use Case. Because it concerns a series of multiple blogs and it may be difficult to oversee the whole. We will outline the full picture in this blog.


The Use Case is about accessing a Decision Model via ICS from PCS. The data used in the DM is retrieved from a Business Object in ICS and sent to the DM. The DM request data and the DM outcomes are stored in a BO in JSON format via an integration.

Using a DM in PCS (how to manage versions …)

In the first blog we make the first version of the Decision Model. In this implementation we call the Decision Model directly from PCS. We also pay attention to the difference between versions and snapshots of Decision Models, and how to use them.

Using a DM in ICS

In this blog we adjust the call from PCS so that the call from PCS goes through ICS. Hereby the creation of this ICS integration is explained step by step.

How to manage Masterdata of a DM (part 1)

In this blog we show a way to move the constant data in the Decision Model to the integration, with the purpose that the Decision Model therefore needs to be adjusted less often. It also emerges that this does have an impact on the internal structure of the Decision Model. The model has been changed from a decision table to nested if-then-else constructions.

How to manage Masterdata of a DM (part 2)

In part 1 we moved the constant data from the Decision Model to the integration. In the integration, use was made of variable with a constant value (as was the case in the DM). In this blog we show how we can get the values ​​from a database table (Business Object) instead of this constants.

Managing DM Masterdata Validity Period

In this blog we will expand the Use Case further with a validity period for the masterdata in the Business Object. Because this only contains changes to already existing components, the overview image does not change.

Input and Output Storage of Decision Model Invokes

In the sixth and final blog we have further elaborated the Use Case. The whole has been expanded with the storage in a BO of the DM input and output messages. A piece of javaScript was also discussed with which XML messages can be converted to JSON.

The image below shows the final result.

note: click this link for a list of all Jarvis Pizzeria post.

One thought on “Jarvis Pizzeria: Summary of a Decision Model Use Case

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s