There is a way to customize the message in the text file using an override configuration XML:

You can use the following Override Configuration option to specify a custom message:

<Settings>

                <Remediation>

                                <M2Secure>

                                                <Msg>This is test custom message</Msg>

                                </M2Secure>

                </Remediation>

</Settings>

You can further define the source and target locations using variables. See explanation and examples below:

Specifying source and target location in user defined custom message:

For a user defined custom message (i.e. non-default custom message) it will be possible for the user to specify source and target locations in the custom message which will be left behind at the file location. The user will have an option to specify source and target location in custom message using variable ?$source? and ?$target? in the custom message. For example, the user may specify a custom message (for either manual remediation or automatic remediation) like below:

?This file is remediated using DLP MoveToSecure remediation action. This file is moved from source location $source to target location $target.?

The variables $source and $target in the custom message above will be replaced by actual source and target paths when custom message is created.

If user does not specify these optional variables in custom message, then source and target paths will not be shown custom message file.

Another example using the above example:

<Settings>

                <Remediation>

                                <M2Secure>

                                                <Msg>This file is remediated using DLP MoveToSecure remediation action. This file is moved from source location $source to target location $target.</Msg>

                                </M2Secure>

                </Remediation>

</Settings>