|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.
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.
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.
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.
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.
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.
The image below shows the final result.