Sync Page

assign sync object,sync object assignment

{"URL":["/*.*/awa/pa_view_sheet_sync"],"heroDescriptionIdentifier":"ice_sync_page","customCards":[{"id":"ice_sync_object","title":"Sync (SYNC) Objects","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_Sync.htm","languages":["en-us"]},{"id":"ice_exporting_tables","title":"Exporting Tables","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/_Common/CommonFunctions/CF_CSVExport.htm","languages":["en-us"]},{"id":"ice_working_with_tables","title":"Working with Tables","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/24.2.0/Automic%20Automation%20Guides/Content/_Common/CommonFunctions/CF_WorkingWithTables.htm","languages":["en-us"]}]}

As an object designer, you add the Sync object object that you want to apply to an object on its Sync page. You also define the actions to be taken when the conditions they specify are met.

Sync objects synchronize tasks. They contain definitions on status, conditions and actions that are combined to specify the order in which tasks are executed. The dependencies defined in Sync objects can result in tasks not being processed because they are waiting for the conditions to be met.

When a task is processed, the system checks the Sync objects inserted on the Sync page one by one. The order in which you insert the Sync objects is important. The system tries to apply the first Sync object in the list by calling its Start Action. If this is not possible (for example, because the current condition of the Sync object prevents it), the action that you select in the Else column applies.

The task itself starts after all Sync objects have been applied. Depending on the end status of the task, either an abend or an end action is processed.

You can add up to 500 Sync objects. All Sync objects assigned to an object can contain a maximum of 5000 rules. Rules are the actions that are specified in the Sync object.

Task processing is handled by Work Processes but only the primary work process can release a Sync object for the ended task. For this reason it might take several seconds to release a Sync object after the related task has ended. In this case, different end times will be displayed in the various execution reports.

Important! Sync objects are a powerful tool to automate task processing according to rules. However, applying many Sync objects and rules can result in complex task configuration that is difficult to maintain. Keep the number of Sync objects to a reasonable minimum, and consider using Schedules (JSCH) instead.

To Access the Sync Page

In the Process Assembly perspective, open the object.
On the left navigation page, expand the General page.
Click Sync.

To Define the Sync Properties

Click Add Row.
Click a field in the row and select the values for a sync item:
- Sync Object
  
  Object that is used for synchronizing the task.
- Start Action/ Abend Action/End Action
  
  Actions that are executed when the task starts/aborts/ends successfully. The available actions depend on the configuration of the Sync object.
  
  If the Start Action fails, the Else condition is applied.
- Else
  
  Defines what happens if the start action cannot be executed:
  - Wait: The task waits until the start action can be executed.
  - Abend: The task ends abnormally.
  - Skip: The task is skipped.

To Remove/Cut/Copy a Sync Element

Select the check box next to the element.
Click the corresponding button.

Viewing the Details

After adding a Sync object to the list, select it and click the Details button in the toolbar to open a pane with the details of that object. For more information, see Viewing Object and Task Details.