Advanced Algorithm Tips

Initiating Actions that Cannot be Rolled Back

If you have an algorithm that creates a sync request or performs some other logic that could cause a message to be sent and cannot be rolled back, you should be sure to cater for warnings in the design.

• The algorithm should be performed after all validations that could accumulate warnings.

• The algorithm should include a step to call the Business Service F1-CheckWarning and see if any warnings have been accumulated.  If so, don't perform the action.  It means that the user will get a warning and if they click "OK", all the processing will happen again, but this time without accumulating any warnings.  Refer to the plug-in script F1-GnChgDCap for an example.