Assume you make changes to an existing workflow design but you don't run the Bulk Update Jobs. What will happen to any records which existed before making the changes to the AWF?
Options:
A.
The active jobs for these records will fail
B.
The jobs will be marked as cancelled
C.
The records will process in the original version they were enrolled in.
D.
The records will automatically enroll in the new version of AWF
In Archer Advanced Workflow, "Versioning" is a core concept designed to ensure data integrity. When a record enters a workflow, it is "enrolled" in the specific version of the workflow that is active at that moment. According to the Advanced Workflow Beyond the Basics curriculum, if an administrator modifies the workflow (e.g., adding a new node or changing a path) and saves it as a new version, the existing records do not automatically move to that new version.
Instead, they remain in the original version they were enrolled in. This prevents active records from "breaking" if a node they were currently sitting on was deleted in the newer version. To move existing records to the latest logic, the administrator must manually use the Bulk Update Jobs tool found in the Advanced Workflow tab of the application. This tool validates whether the records can safely transition from the old version's current state to a corresponding state in the new version. Without this manual action, the records will continue to follow the "legacy" path until they complete the workflow.
