Sync objects help coordinate the processing of multiple executable objects. You use them to define states, status transitions actions and values, and assign them later to other objects.
Object class: Active object
Object type/Short form: SYNC
Two processes in your organization are completely independent from each other; you have created two workflows to automate them, which also run independently. However, these processes share a job, which is therefore included in both workflows. You want the job in one of the workflows to be started only if it has already finished in the other one.
This is but one example of external dependencies among processes that you probably face. Sync objects help you easily manage them.
In a Sync object you define states that depict the stages of your processes. You link these states to particular actions and define further follow-up states and actions to build the conditions that control when and how executable objects will be processed. Additionally, you can (but must not) assign values to those actions that help fine-tune those conditions.
You then assign the Sync object to the executable objects you want to control this way. You can assign a Sync object to as many other objects as you need. As soon as the executable objects are activated, the system checks what is the current state of the Sync object and, depending on the action (and value, if set) assigned to that state, the executable object is processed or not.
Sync objects created in client 0 are available for all clients.