Sync rules define the data to be synced from assets, users, or software installations to CMDB. The synced data is populated as CIs in CMDB and linked to the corresponding asset, user, or software.
You can perform various actions on CIs and their relationships based on the synced data. Any changes made to data in the asset, user, or software installation will be reflected in the corresponding CI and vice-versa.

Sync rules will not be applied while importing assets, workstations, mobile devices, and asset components.
Role Required: SDAdmin
Create Sync Rule
- Go to Setup > Customization > CMDB > Sync Rules.
- Click New Sync Rule.
- Fill out the form using the pointers below:
Field
| Description
|
Name
| Enter the name of the sync rule.
|
Description
| Describe the sync rule purpose and usage.
|
CI Type
| Select the destination CI type where the data from the source module is synced.
|
Sync with
| Select the source module from where the data is fetched and synced as CIs. You can sync data from:
Assets
Users
Software Installations
 Only Managed Software of software installations can be converted as CIs using sync rules. |
Applies to
| Select the asset or user type where the sync rule is applied.
This field is not applicable while syncing software installations as CIs.
|
Status
| Enable or disable the sync rule. Disabled sync rules cannot be executed using the Run Through option.
|
Actions
| Define actions to be performed when the sync rule is applicable:
- Create CI
- Create asset from CIs
- Map fields between CI and records in other modules
- Create relationships
- Delete CI
- Delete asset
|
Click Save.

You can create multiple sync rules for a particular CI Type. However, if the source is Assets, then only one rule per asset type is allowed.
Sync rules are automatically applied when the asset, user, or software installation is added, updated, or deleted. You can also manually apply sync rules using the Run Through option.
Sync Rule Actions
Create CI from [x]
Create/link new CIs based on the specified condition. The CI will be created from the configured asset, software installation, or user.
- Specify the condition to apply the sync rule:
- Based on conditions - Define the criteria to apply the sync rule by selecting the column, operator, and value. Use the Add icon to define multiple criteria.
- Without condition - Apply the sync rule to all records in the selected module.
- Enable Configure default values to create CI to create CI with all details in the source module record. You can also add custom values to various CI fields by mapping them.
Create [asset] from CIs
Create/link an asset from CIs based on the specified condition. The CI data will be auto-populated in the asset; you can also map fields to populate data.

This action is applicable only when the sync rule is configured for assets.
- Specify the condition to apply the sync rule:
- Based on conditions - Define the criteria to apply the sync rule by selecting the column, operator, and value. Use the Add icon to define multiple criteria.
- Without condition - Apply sync rule to all CIs in the selected CI type.
- Enable Configure default values to create [asset] to create assets with all details in the CI. You can also add custom values to various asset fields by mapping them.
Map [x] fields
Map the asset, software installation, or user fields with the selected CI type fields.
- Select a field in the source module.
- Select a corresponding CI Type field.

Only fields of the same type can be mapped.
You can map multiple fields. To add new fields to a CI Type or to know more, click here.
Changes to Assets/ Software Installation field values will be reflected in the corresponding CIs and vice-versa. If CI Type has unique fields, then they should be mapped with the fields in Assets/Software Installation records.
If the mapped field is non-editable, then it will not be synced.
Create relationships
Define relationships between the CI with other CIs based on asset, user, or software installation fields.
- Select the relationship type by using predefined or custom relationship types.
- Select the destination CI type
- Select the relevant asset/ software installation field.
- Click
to define multiple relationships.

The associated asset, user, or software installation must already be a CI.
Delete CI
Delete the CI when the corresponding asset, user, or software installation is removed.
Delete [asset]
Delete asset when the corresponding CI is removed. This action is applicable only when the sync rule is configured for assets.
List View Operations
- Click
to edit or delete sync rules. To bulk-delete, select the sync rules and click Delete on the toolbar.
- Click Organize to set the order in which sync rules will be executed. Use
and
to reorder the rules and click Save.
- Click
and select Run Through to execute a sync rule manually. You cannot execute sync rules manually.
- You can enable or disable existing sync rules using the toggle button under the Status column.
Related Articles
Form Rules
Form Rules allow you to define rules to automate certain actions on form fields based on custom conditions. Supported Form Types: Incident request forms, service request forms, change forms, problem forms, and release forms. Form Rules are executed ...
Closure Rules
Closure rules automate the collection of vital details and execute relevant actions before a record can be closed in the service desk. Supported Modules: Requests, Problems, Changes, Releases, Purchase Orders, Tasks Role Required: SDAdmin Benefits: ...
Business Rules
Configure Business Rules Business rules are used to automate actions on a request that fulfill certain incoming criteria. The criteria for the rules are set using the request fields. Business rules can be used to automate actions on incident, ...
Notification Rules
Notification rules allow you to specify conditions when a key event must be alerted to users. Supported Modules: Requests, Problems, Changes, Projects, Release, Solutions, Assets, Purchase, Contracts, Tasks, and other general events. Role Required: ...
Configure Custom Scripts for Form Rules
Tabulated below are some of the sample scripts that can be performed as actions in request/change Form Rules. Requirement Script Examples Remarks Alert (Requests & Changes) await CS.alert(“message”); await CS.alert("Alert message"); Confirm (Requests ...