Configuring business events for follow-up actions
The following procedure explains how you can create a business event and decision model for follow-up actions:
Procedure
1. In Field definer , select the Business events business object and create a user-defined business object: Follow-up action event.
For more information on what to configure, see Configuring user-defined business objects.
2. In the Attributes TSI, create an attribute set: Follow-up action event.
3. Create the following attributes and link them to the set:
 | When specifying attribute definitions, make sure to copy the exact names and enter these in the Code field - the system will use these as look-up value. If you forget to add a mandatory attribute, or if you made a configuration error, this is indicated in the Error log and Failed fields of the business event. For a comprehensive overview of the attributes used in the Decision model for follow-up actions and the related business events see: Attributes overview. |
◦ FollowUpActionCode - single line [mandatory]
◦ Comment - multi line
◦ DueDateTime - date-time
◦ ExpectedCost - decimal
◦ ObsPriorityCode - single line
◦ StdObservationCode - single line
◦ ObservationGroupCode - single line
◦ SpaceCode - single line
4. In the Decision models TSI, create a decision model: Follow-up action model.
5. Define decision rules for this model.
Each rule must have a condition and an action worker. If the worker requires additional information, you must link the correct attribute set for the worker to the decision rule. See Configuring action workers for a decision rule.
6. In Field definer , configure the relevant business object settings on the Follow-up actions (base) business object.
Business object definition => Select user-defined business object Follow-up action event.
Attribute definition set => Select attribute set Follow-up action event
Decision model => Select the Follow-up action model
The business event and decision model for follow-up actions are configured. You can also configure other business events, to automate:
◦ the creation of observations;
◦ the creation of follow-up actions based on topic scoring;
◦ the creation of follow-up actions based on answers given in an assessment.