Version Selection
In most cases, the version in which precedence is considered is the version that is served as the base. However, this may not be the case in some use cases.
When import is done, the draft record is created. This draft record may be modified to create additional versions in the workflow. If you want to ensure that each subsequent modification does not violate the precedence criterion, the use of version, which is previously confirmed or unconfirmed (to this version), is more appropriate.
If you want to apply flexibility in precedence logic, it is possible to configure the workflow to have a separate step, EvaluateRulebase, applied to precedence. In this case, irrespective of what changes have happened during workflow for the draft records, it is possible to look up the previously confirmed or latest version.
To support these use cases, the precedence action can accept an argument to indicate which version should be used. The version keywords are the same as those used with CHANGED condition: PREVIOUS_VERSION and PREVIOUS_CONFIRMED_VERSION. If nothing is specified, the parent version is used.