|
|
This screen lists the diaries in the system.
Event Manager Diary
Diary entries may be created as a reminder to take some future action, or link an event, to a particular date.
Event Handler programs may create Diary Entries as notification that an Event has occurred. The system automatically generates a list of outstanding diary entries when you log-on.
The list of outstanding Diary Actions may be viewed or amended, as appropriate. If a Diary Entry has an associated program, that program can be run by double clicking the diary entry.
Field |
Description |
Selection (filter) |
|
Date From / To |
The dates that indicate the beginning and end of the search for diary entries. If no dates are entered the 'Date From' field will default to the earliest date on the system, while 'Date To' defaults to today's date. |
Object |
The Object to which the diary list refers. |
Program |
Optional entry. Program identifier for program attached to Diary Entry. |
Source User |
Enter a user code of the originator of the diary entry. |
Priority |
Optional; used to restrict the list to those Diary Entries which match this priority indicator mask. The default value is underscore which matches all priority indicators. Low, Normal, High. |
Receipt Status |
Set this parameter to display those BEM entries which match the given individual or group of indicator values. |
All Entries |
Tick to include diary entries regardless of the action user. |
Include Complete |
Tick to include diary entries with a status of 'complete' in the list. If blank only entries that are outstanding will be included on the list. |
Key Flag |
This is a non standard operation. Prompt (F4) to transfer to Action Keys Edit (MXEI) to either view or provide which displays the search key values for the Object. |
Include Batched |
Set this parameter to display those BEM entries that are marked for staged (batch) notification. Policy controls can be set for staged delivery as an overall preference and can be overridden at Event level, or User / Event intersection level. |
Diary List |
|
Action |
The description of the object/event. |
Priority |
Details the priority of the event. |
Complete |
This will be set on if the Dairy entry action has been completed. |
Action User |
The User identifier of who is to execute the outstanding event. This will default to the signed in User. |
Action Date |
The date on which the entry should be actioned. This field is mandatory and for new diary entries must be greater than today's date. |
Contact Name |
The name of an individual who can be contacted with reference to this diary entry. |
Phone |
The contacts' telephone number. |
Escalated To / From |
Details the user ID of the user from who the event was escalated. |
Transferred |
Details the transfer status. |
Transfer User |
The User ID of the person who this event was either transferred to or from. Note: if an event was transferred to many other users through the use of proxies then this field will show the first user. |
Menu options
Go Object Key | Click Go: Object Key to transfer to the Object Keys screen MXEI for viewing the key values associated with the entry Object. |
Go Program Params | Click Go: Program Params to transfer to the Diary screen MXEL for viewing the parameters associated with the entry. |
Go Program | Click Go: Program to transfer to and run the program (if any) associated with the diary entry. |
Edit Transfer | Click Edit: Transfer to transfer to the Diary - Transfer screen MXEK. It allows you, as the Action User, to transfer an entry to another user for them to action. |
You can change the appearance of the list view:
If not described in this topic, click on a field and press F1 to view help. See Common Fields for more information.
Fast prompt allows you to quickly view a list of options for certain fields.
See Using the Command Line on opening the screen without going through the menu.
See also
Business Event Manager Home Page