This example illustrates how you can configure EZ-MES to send emails to users when a Part is placed on hold. In this example we assume that you already have configured an Email Template.

Email Document Configuration

The example template we will be using will have the following HTML configuration:

You will notice that it consists of only 4 different variables, although, you can make your own template as complicated as you would like. 

• <%PNAME%> will be the Part Record Name
• <%UID%> - will be the Unique ID of the Part Record
• <%sDefaultWebPath%> - this is the standard default web path or URL to your application.  This does not need to be defined in the Document Definition.
• <%sJob%> - internal Job Number used by the system to access the Part Record UID.  This does not need to be defined in the Document Definition.

Event Configuration

After you have completed configuration of your Email Template Document you can know began Configuring your Event.

• Event Name: Hold Notification Template
• Event Type: Records
• Event Description: Will fire when Part enters Hold Flow
• Allow Manual Fire: False
• Do not check on Time Loop: True

Trigger Configuration

The following is an example of how to  Create your Trigger so that the Event can fire when it enters the first Hold Step.

It is fairly simple with this Trigger because it only consist of 'true' statement.  This is because we want it to fire immediately upon entering the Step.  There is no other validation necessary.

• Trigger Name: Hold Notification Template
• Description: Will fire when Part enters Hold Flow
• Done String Formula: true

Action Configuration

Create your new Action with the Email Type.  It should be configured as follows.

• Action Name: On Hold Email
• Description: This email will be sent
• Action Type: Email
• Email Template: DC12-000000015 (or whichever document number is required)
• To Select: This email address is being protected from spambots. You need JavaScript enabled to view it. (or whichever required, you can use Group also)

Add Action and Trigger to Event

After verifying the Action and Trigger are correct and in the Active State you can now add them to the Event.  Once they are added, you can now move the Event Definition to Active as well. 

Adding Event To Step Definition

The final step is to attach the Event Definition to the Step Definition.  Choose the Step Definition you would like to monitor.  In this case it would be as follows

• Add Event: Hold-Disposition Event
• Attach Event to: Part