|In this blog we describe a way to store the Input and Output of Decision Model Invokes (in JSON format).|
From an administrative point of view, we at Jarvis believe it is important that we can always see how we have achieved certain results. In this case this means that we want to know with which variables the Decision Model was invoked and what the outcomes were. How we do this is subject of this blog.
Saving the results is e.g. possible after performing the ‘Calculate Delivery Time’ integration in the Process.
However, we have chosen to do this in the integration that we have already created (Managing DM Masterdata Validity Period) so that the process is not polluted with this technical step. As will appear later in this blog, we have to slightly update the payload of the call.
The integration looks like this at the end of this previous blog.
And here the integration as it should be. The DMStorage step with associated mapping has been added.