Designing Event Delays

Because event delays can only detect data changes that happen after the event delay starts, you must model your cartridges so that the event delay starts before the task or process that triggers the data change.

For example, imagine you have a cartridge project with two parallel processes. Process A includes an event delay that pauses until Process B updates some order data. If you model the project so that Process A reaches the event delay before Process B begins, when Process B updates the data, the event delay detects the data change, evaluates the order rule, and resumes Process A if the rule evaluates as true.

However, if you model the project so that Process B updates the data before Process A reaches the event delay, the event delay does not detect the data change, does not evaluate the order rule, and continues to delay Process A indefinitely.