Core TSIs : Event Connector : Field descriptions : Decision models/rules - fields
Decision models/rules - fields
Field
Description
Code
A code to identify the decision model.
Name
A name to identify the decision model.
Remark
Free-definable field, you could e.g. include a description of the decision model.
Decision rules
Sequence
Enter a value for processing the rule. A decision model can contain various rules, they will be executed in the order defined here (1 being the first rule to be executed).
Decision model
Select the decision model to which you want to link the rule.
Triggering status
The user-defined intial status that triggers the condition rule.
Condition
Specify the filter criteria to be verified. By using And/Or operators you can expand the filter criteria.
If the condition is true, the next rule will be executed. If there are no more rules to be executed, the required action is carried out.
If the condition is false, the process stops and the decision model status changes to UsrRejected.
If the condition cannot be determined, the status of the decision model changes to UsrAwaitingAssessment.
Action worker
Select the action (business rules) to be executed once the conditions are met. The business rules are available in the Apps TSI (and constructed in the Planon Platform IDE).
* 
If the field is empty then only the status of the business event will be set (via the Resulting status field)
Resulting status
The status in which the rule will be set once the condition has been verified (UsrApproved or UsrRejected UsrAwaitingAssessment)
Partner identifier
The namespace (PartnerID, App name, Module name) is used to select and find the class in a decision rule.
App name
App module name
Remarks
Free-definable field, you could e.g. include a description of the decision rule.
Settings tab
Settings
The settings that apply to the decision rul (JSON format). The user has to define the values of the various settings in this field.
When the app is upgraded (introducing new or changing settings), this field is not automatically changed. When this happens, you must manually update this field.
Settings example tab
Settings example
A calculated field with example of the settings, in JSON format. This is intended to help define the correct settings in the Settings field.
When the app is upgraded (introducing new or changing settings), this field is updated according to the new settings.
Settings schema tab
Settings schema
A calculated field with the type/format and constraints that apply to the settings, in JSON format.
When the app is upgraded (introducing new or changing settings), this field is updated according to the new settings.