Notifications 

MDM workflow can send email notifications when a step has exceeded its allotted time or number of iterations. The notification from the owner of the workflow is sent to all assignees who have received but not yet completed the step, along with a “cc” to the specified users.

A sample email notification is shown in the figure below.

You must add a Mail Server entry in the mds.ini for every repository that uses workflow (for example Mail Server=mail.domain.com). The timeout for mail server responses is 1 second. If MDM doesn’t receive a response from the mail server within the timeout period, it aborts the email task and will not attempt to resend the email. You can adjust the length of the timeout period in the mds.ini file’s Mail SMTP Timeout parameter.

Also, MDM verifies the first “sender” and “recipient’ email addresses for an email notification. If either or these are not valid, MDM aborts the email task and logs the error in the Workflows log.

The Subject and Body properties of a user-defined Notification step can include variables for job-specific information, as listed in the table below.

Variable	Description
%RepositoryName%	The repository name
%TableName%	The table name
%JobId%	The job id
%JobName%	The job name
%StepId%	The step id
%StepName%	The step name
%Records%	The record id and display fields of the job records

Because it may include multiple lines, the %Records% variable should not be added to a notification email’s Subject property.

MDM separates a record’s display fields with a “|” delimiter when populating the %Records% variable.

When populating the %Records% variable, MDM only looks up one level when a job record’s display field is a lookup field. If the display field of the lookup table is itself a lookup field, MDM substitutes the job record’s display field value with the RecID of the “first” lookup table record.