Deleting data by using DSO
In Developer Studio, you can delete data from the target server for the respective forms by using the DSO delete filters on the source server.
Before you begin
- Before attempting the procedures in this section, ensure that you are familiar with distributed operations. For detailed information about performing individual distributed operations, see Setting up DSO to synchronize data across multiple AR System servers.
- Make sure that the servers create records with unique IDs:
- Configuring-forms-to-use-DSO-unique-prefixes
- Hub and Spoke Prefix Manager (For a Hub and Spoke environment)
To configure the DSO environment for data deletion
In Developer Studio, perform these steps on the source server to delete data.
- Create distributed mappings for the forms based on matching IDs, field names, or custom field mappings. Set these only once for each form that you want to use with DSO.
- Create filter workflow for the DSO action to specify the Distributed Delete.
- The only required qualification for a DSO delete filter is $USER$ != "Distributed Server". In a two-way distributed environment, where the target also has the DSO delete filters, this qualification prevents processing of the DSO delete filter in the target server.
- You can set the filter to execute on Delete with no Run If qualification if the scenario is data replication through DSO from one server to another.
- You can create more than one DSO delete filter for different specific use case scenarios of how and when you want to delete data.
Audit forms handling
The audit log entries are not deleted in BMC Helix ITSM applications. In addition, an audit log record is created when the parent record is deleted. If you have a business requirement to delete audit log entries when the parent record is deleted, create custom filters for the parent form on the source server as well as the target server. The following process describes how to create the custom filters.
Filter | Result |
|---|---|
The parent form filter qualification should contain $USER$ != Distributed Server and should execute on Delete. | After the record is deleted from the parent form on the source server, the custom filter removes the record in the audit log form. |
The custom filters qualification should contain $USER$ != Distributed Server and should execute on Delete. | On the target server, the DSO filter removes the entry in the parent form and the audit log form. |
Notification forms handling
The following notification forms process transactions and do not store data. No DSO delete workflow is required for these forms.
- NTE:Notifier Log
- NTE:SYS-Define NT Events
- NTE:SYS-Group NT Control
- NTE:SYS-Individual NT Control
- NTE:SYS-NT Process Control
Software License Management (SWLM) rules engine forms handling
The following rules engine forms process transactions and do not store data. No DSO delete workflow is required for these forms.
- RLE:LoadRule
- RLE:LoadRuleSet
- RLE:LoadRuleSetType
- RLE:LoadRunTag
- RLE:LoopRuleSpecificData
- RLE:RuleEngineFireInterface
ITSM application delete filters
The DSO delete filters on the source server execute on a Delete action and delete the records on the target server for the respective forms.
As the DSO delete filter removes the target records, a skip workflow is introduced in the BMC Helix ITSM applications to prevent the out-of-the-box delete filters for those forms from executing.