This documentation supports the 9.1 version of BMC Remedy ITSM Deployment.

To view the latest version, select the version from the Product version menu.

Special scenarios during AR customizations reconciliation

You might encounter the following scenarios while using BMC Remedy Developer Studio.

Data source modified for all Set Fields action

If the Set fields data source is changed, some of the properties may appear as deleted or added. To reconcile this change, you must change the data source of the Set Field and then add the values of added properties in the new definition to your overlay. These changes will be visible in the Differences List as well. For example, when your data source is modified from CURRENT TRANSACTION in the old definition to SERVER in the new definition, you must manually verify and reconcile the data source again. As new fields related to the SERVER data source, such as form name, Qualification, and fields are added in the new definition, you must compare your overlay definition and the new definition to see what needs to be reconciled. 

You can also choose to copy the Set Field from the new definition and paste it in the overlay definition. However, the fields and value are not retained in the overlay definition because the data source has changed completely. 

For all types of set field actions, all the changes are displayed and the data source for the set field action is changed, you will have to reconcile all the properties/attributes.

Note

You may see a list of properties in the Differences List that are modified or deleted in the new definition and indicating that you must reconcile them. However, because the data source has changed, all the related properties will also change, and you do not need to reconcile those properties. 

Display type modified for fields

If you see an added or deleted property for a field, check to see whether the display type for that field has changed. To reconcile field changes, you must change the Display Type in the overlay and then set the other properties.

Filter all differences versus only manual reconciliations

Because the filter is ON by default, the Differences List only shows the differences that need to be reconciled.

Conflict when new definition and overlay definition have the same value

When the new definition and the overlay definition contain the same value that is different from the old definition, there is no conflict and you do not have to reconcile your object. However, when you turn the filter OFF, the Differences List still shows a conflict for this situation because the object has been modified in the new definition and the overlay definition when compared to old the definition.

Conflict when new definition and overlay definition are both deleted

When the new definition and the overlay definition properties are deleted and a property still exists in the old definition, there is a conflict but you do not have to reconcile your object. However, you can move your old definition to your overlay definition using Move Old option.

Difference due to change in the index value for actions

In workflows, the position of the Change Field action changes inside objects due to the addition or deletion of actions. Although no reconciliation is required, the Differences List still shows a change when the filter is OFF.

Empty Differences List

If the filter is turned ON and the list is still empty, it means that there are no differences to reconcile. The list displays the message No Differences for Manual Reconciliations.

When the new definition and the overlay definition have changed from the old definition and the overlay definition contains all the changes from the new definition, a conflict is not displayed in the Differences List when the filter is ON. However, you can view the changes by turning the filter OFF. The Differences List displays a conflict but there is nothing to reconcile because all the permissions from your new definition are already present in the overlay.

Was this page helpful? Yes No Submitting... Thank you

Comments