Action List Edit MXEH

The Action List determines which programs are to be run in response to a given event occurring. When an action is created, the system will generate a unique System Reference code for it.

Opens from System Controls Action List.

• Click Insert and Action List Edit MXEH opens.
• Select the entry you want to edit, click Amend and Action List Edit MXEH opens.

To create an Action, you must enter the following:

• The Object to which the given Event belongs
• The role of Object keys in the execution of an Event
• If 'Object Keys' is not set then the Action will be triggered for all occurrences of the related Object
• If 'Object keys' is set then it indicates Key values have been set up limiting the triggering of the Handler program to a Specific Object

For example: Given a set up for a Supplier Event , then, if no Object Keys are provided, the Handler Program can be triggered when the Event occurs against any Supplier. If the Key values for a Supplier are given then the Handler Program can only be triggered against that specific Supplier. See MXEI for the setting of Object Key values.

The use of key values in the establishment of an Action is determined by the 'Keys Allowed' field on Event - Edit MXED.

• The Event to be handled
• The Handler Program which is to be triggered should the Event occur. This program must be a Handler Program and must have been set up as a handler for the given Event. See MXEF.
• The Handler Program will default in as the generic handler program XFK, use of this program as a handler invokes additional functionality.
• Additional functionality invoked by the generic handler program XFK includes;
• Substitution - Where the object key fields are listed and can be checked to be included in the email or SMS substitution text.  
• Program to Call - Where a list program may be entered.  This will then be invoked when a user performs the action 'Run Program' from the diary event.  
• Action User Role may also be defined, which can be used as a distribution list of users to receive this particular diary event.  
• Notification is a list of user fields extracted from the object table, these users are available to be selected for notification.
• For the generic handler program XFK, if no user is selected for notification, then the user who initiated the BEM event will receive the diary entry.
• If the Handler Program creates a Diary Event, you must specify a target user. If a User ID is given then this user will receive the Handler Diary Entries rather than the default user

For example: For a Goods Cancelled event Handler Program XE0 normally creates a Diary Entry for the relevant buyer. If a relevant Action List entry is created with a Target User then that user will receive the Diary Entry. This field is only used by event handler programs XE0, XE2, XE3 and XFK. It is ignored by all other Handler Programs.

• If the Event can occur more than once for the chosen Object, then set the 'Multiple' flag. If not set, then the Event can occur only once, after which the appropriate Action is automatically deleted from the list
• The delete date after which the Action List entry can be deleted from Event Manager. If no date is specified the entry will remain on the system until removed by a user
• You may also optionally enter text that will appear on any emails or SMS messages that are generated as a result of the Event.  An email or SMS footer can be applied via e5 System Controls. See MAAB
• A send QED Mapping may be optionally be defined which would be executed to send the event email notification.
• A send Include may be optionally defined which could contain up to 2000 characters of BEM event email text along with substitution of any base table or diary data.
• A Remote Event can be flagged which allows for remote actioning via email as defined by the each Users BEM level. Up to 6 action Keywords/Descriptions for each event can be defined along with an optional Confirmation email QED Mapping and/or Include text.  

Only Order Authorisation is currently available.

See also

• Action List List MXEG
• BEM Trigger List MXF2