Scope-based grouping not working

If the ScopeID is based on the field values that are available at the event insertion time, then the Scope Based UI can be used to create a scope-based policy.

If the ScopeID is based on any enrichments (fields that are not available at initial event insertion time), then the ScopeID must be updated manually. Any policy created with the Scope based UI is not effective for updating the ScopeID based on enrichments.

To update the scope-based grouping after enrichment, you must update ScopeID manually. For example, if you use the Scope Based UI to define a policy and set ScopeID equal to SiteID. At insertion time, the SiteID value is blank and its value is enriched using IBM® Tivoli® Netcool®/Impact in the aggregation layer. Manually update ScopeID to equal SiteID, either in the Netcool/Impact policy or in the ObjectServer trigger. The scope-based group is then re-created based on the updated scope.

If you configure a scope-based grouping policy, such as setting CEADismantleSingleMemberGrps=1 or CEAMinimumChildren=2 in the master.cea_properties table, these settings indicate that groups are created only when a minimum of two child events are present. However, the policy is not triggered even if you send events through that would normally trigger the scope-based policy.