Document or package custom logic rule firing order
Closed this issue · 1 comments
Currently, it's possible to have a rule that will fire both document custom logic as well as package custom logic, such as for "Party retrieved document" or "Party completed" etc. events that may be defined in each.
Currently, document rules are evaluated before package rules. This creates issues when needing to pre-fill data, for example, from one document into another via "party retrieved document" events in the package, and when the document also has a rule for "party retrieved document" and attempts to make references to those same pre-filled fields. In this case, the document looks at the field values before the package has prefilled them.
Need to make it so this order can be controlled.
Added the ability to specify in a package custom logic rule whether it should run before the document rules (new feature) versus running after document rules (the way it previously always did). Included in 17.4.8 release.