The DRM is imported into iCM as part of the standard site release process. This will import all of the relevant forms and end points, but you will still need to set up the Form App Shortcut and create the nightly scheduled task.
Form App Shortcut
Create a shortcut for an iCM user group with access to the "Retention Manager" form. You could add this to an existing administrator group, or create a new group which will only grant certain users access to the form app.

Scheduled End Point
Set up a scheduled task to run the
My Account Integration
The "User Delete Retention Manager" form can be used by website users to delete history records that relate to them.
If you want your users to be able to delete data via My Account, first create an article using the Forms Service template and relate the "User Delete Retention Manager" form to it. Next select that article as a "List item" in the My Account article extras.
See the My Account - Advanced Layout documentation for more information.
Configuration
A configuration end point includes some feature flags and support for batching in custom deletion end points.
function(params, credentials) {
return {
flags: {
formData: true
},
processHistory: {
getHistoriesBatchSize: 500,
maxRunTime: 240
},
customEndpointsForBatchDeletion: []
};
}
| Property | Type | Description |
|---|---|---|
| flags.formData | Boolean | Set this as false to disable the ability to schedule the deletion of form data |
| processHistory.getHistoriesBatchSize | Integer | The batch size for processing histories. Defaults to 500 if not set |
| processHistory.maxRunTime | Integer <minutes> | The length of time to run when processing batches. Defaults to 240 minutes if not set |
| customEndpointsForBatchDeletion | Array <string> | If you have written custom end points to delete data (which can be picked using Creating Policies for History Records and Process Instances - The Scheduling Form) and your end points support batching the data before it's deleted, enter the full namespaces of your end points here (a comma separated array of strings). If your custom end points don't support batching, there's no need to enter their names here, they'll be called as part of the normal processing of schedules |
