Configure the basic properties of a new event type

Related topics

An array of event types come preloaded with DC1 Alert Management. However, it is possible for you to create your own event types that may be required for your field of business. Please contact your System Administrator or DC1 for assistance.

The following describes the process of creating the basic properties of a new event type. The scenario is one of an event being created to inform users of a new sales order being set to a status that is ready for processing.

Select the Work with event types menu item.
On Work with event types, click Add to create a new event type.
You access the detail panel. Here, you will configure an event type that informs the receivers that a sales order is ready for confirmation. The following fields apply:

Event type

Enter a name to identify the event type that you are creating.

Description

Enter a description of the event type that you are creating.

Active

Indicate it this event type should be active. NO is defaulted.

Driver program

Mandatory entry. Enter the program number for the driver that will be used for this event type. Existing records cannot be changed. Note: This value is automatically set to EDSR370 as default. It is recommended that you keep the default, as this is the DC1 standard program which is used to drive DC1 Alert Management. This field has been created with the possibility to assign another program should your System Administrator want to create one. However, this is the only driver program that is shipped with DC1 Alert Management.

Data queue routine

Displays the data queue routine name.

Number of parameters

Indicates the number of parameters that are used for this event type. Parameters are configured at a later time in the process of creating new event types. Until this has been done, NO is defaulted.

Hold limits

Indicates if limitations have been created for one or more of the parameters used for this event type, meaning the parameters are holding limits. Limits are configured within each parameter at a later time in the process of creating new event types. Until this has been done, NO is defaulted.

Hold filters

Indicates if filters have been created for one or more of the parameters used for this event type, meaning the parameters are holding filters. Filters are configured within each parameter at a later time in the process of creating new event types. Until this has been done, NO is defaulted.

Valid for hours

The number of hours entered in this field will be added to the creation time of messages. This is then displayed on the Work with messages panel. However, this value does not delay the presentation of the message to the user in any way and is displayed only for information purposes. Here, leave the field blank.

Alert header text

This field is used as the header text in the message that will be received by the user(s) who is assigned as the receiver for this event type. Essentially, this is the message’s subject line. You are able to also enter variables in here that point to particular parameter fields. Here, enter: Sales order and &P01 is ready for confirmation.

&PO1 points to the parameter that will be configured later in Create parameters for an event type. This value will be extracted from here and placed in the header text of the message received by the user.

Use create API

Indicates which program is used for API purposes and is defaulted to EDSR020.

Restart possibility

Indicate if you want the messages that are created for this event type to be written to a backup file at the time of their creation. Set to YES for those events that you want to have the created messages saved for future reference, should the data queue be interrupted and then having to be re-started for some reason. Here, set to YES.

Note: It is recommended for event types that will occur with great frequency and record non-vital happenings that this field is set to NO. This will speed up the flow-through, since the system will not to create and delete records in the backup file.

Escalation days

When an alert is created and needs to be acted upon by a receiver, there may be instances where this cannot be done, for whatever reason. Through the process of escalation, the system may be configured in such a way as to have these sorts of alerts monitored and be escalated to a higher level, after a certain number of days have elapsed. In this way, you can be sure that someone else tends to the responsibility.

Here, enter 2 days. This indicates that if nothing has been done in terms of follow up on this event after two days, it will be escalated to the next level.

Escalation program

If you are aware of a new program that has been created for escalation, then enter its name in this field. However, in most instances the default program will be automatically entered.

Click OK. Exit the routine.