If you work with rules functionalities, you can easily and quickly create or change a lot of data records. In the worst case, cycles, with endless changes or creation of new data records, can develop.
Rule administrators must know exactly what they do and must have been trained on how to use rules.
Please pay special attention to the following information and recommendations, particularly if you are an administrator.
The notification and action service is a server based service and runs on the CAS genesisWorld application server.
The service checks all rules for monitored data records in a predefined Monitoring interval. If an event occurs, the corresponding actions are executed.
To not overload the application server, the service only runs for a certain period of time depending on the load of the application server. As a result, the time between an event occurring and the execution of the action may vary.
If you open the rules to check them, you should click Cancel to close the window. By clicking OK, a rule is newly initiated and the execution of the notification and action service is delayed.
The application server load depends on the Monitoring intervals of the rules. If the application server's load or the number of actions means that the monitoring intervals cannot be adhered to, you have the following options:
We recommend to only assign the Rule administrator option for specific users and to train these users on how to work with rules.
Please also note the following when using the notification and action service:
Cycles
Multiple rules from one or more users can lead to cycles or infinite loops.
No workflows
You cannot match a multi-step workflow with the notification and action service. The depiction of elements like workflow chains, conditions, branches, and so on, is not intended.