Comparing datasets with the Reconciliation Engine
The Compare activity operates against instances in two datasets and either produces a report or executes workflow based on the Compare results. The report shows those instances that appear in only one of the datasets and details the differences between instances that appear in both.
Compare lets you compare an expected configuration against an actual one, which you could use for more than one purpose. You might use Compare to alert you that something has changed in a configuration that you expected to remain static. Alternatively, if you have a change request in progress, you might use Compare to verify that the configuration reaches its expected new state.
Only instances that have been given a reconciliation identity can be compared, and they are compared only against other instances with the same identity. If you choose to execute workflow as a result of the comparison instead of creating a report, that workflow can execute against instances from either dataset but not both.
To compare instances, you must create a Compare activity and specify the two datasets that you want to compare. From that activity you can choose to exclude particular attributes from the comparison by creating Exclusion rules for them.
To execute workflow as a result of the comparison, you must also create a Workflow Execution group to associate with the Compare activity and from that group, create a Workflow Execution rule for each qualification that, if true, causes workflow to execute. The qualification can evaluate attributes from both datasets.
You also must create one or more BMC Remedy Action Request System (BMC Remedy AR System) filters to perform the workflow for each Workflow Execution rule.
For more information about comparing, see Comparing datasets by using the Reconciliation Engine.