Propagation and Rulebases

Propagation should be designed to work in one direction. If you have the following scenario, you may get unpredictable results:

  • Propagate from Repo A to Repo B
  • Propagate from Repo B to Repo C
  • Propagate from Repo C to Repo A or B

Depending on the change and the use case when the propagation happens in both directions, the order of propagation may be different.

While propagating the entries to related records, note that updates are not allowed if the related records are already modified, unconfirmed and part of another workflow. In these cases, you must specify the target record state as Draft in the EvaluateRulebase activity to isolate the changes.