Synchronize attributes
Not all attributes are synchronized back from SM to OMi by default. When the SM incident is initially created from an OMi event, event attributes are mapped to the corresponding SM incident attribute. Out of the box, after the initial incident creation, whenever the incident or event subsequently changes, only a subset of the changed event and incident attributes are synchronized. The following describes how to customize the list of attributes to synchronize upon change.
Unidirectional synchronization: OMi to SM
The following attributes are transferred to SM from OMi on a one-time basis, that is, when the event was initially created, and the transfer of control of the event was configured in the Connected Servers manager.
These attributes support bidirectional synchronization, but are disabled out-of-box:
- Title
- Severity
- Priority
- Operator: the operator assigned to the event who forwarded the event
- Category
- Subcategory
- Related CI
OMi event annotations are synchronized to SM activity log and there is no back synchronization from SM to OMi.
Bidirectional synchronization
Attributes that support bidirectional synchronization between OMi and SM are:
- Description
- Lifecycle state (the state is only updated when the state changes to closed)
- Solution
- Contents under the Forwarding tab in the Event Details
Attribute synchronization using Groovy scripts
If you want to change the out-of-the-box behavior regarding which attributes are updated, you can specify this in the Groovy script used on the OMi side for synchronization or incident creation. In the Groovy script, you can specify which fields are updated in SM, and which fields are updated in OMi. You can also specify custom attributes in the Groovy script.
For more information, see Tips for customizing groovy scripts.