Event Registry

An event is part of a transaction and generates a method call to the condition handler which decides, by evaluating the conditions, whether the registered action should be performed, or not. This is known as the ECA rules with ECA referring to: Event, Condition and Action.

Read more about the concept Events.

Contents

Setting up an event

Setting up an event includes two basic steps

  1. Register the event in an ins file using method Event_SYS.Enable_Event. Specify information about which entity and name the event has, the description, the variables that can be used for conditions and actions, and the type of the variables (string or number).

     

    Event_SYS.Enable_Event(<Entity_Name>, <Event_Name>, <Desc>, <Condpars>)

     

    <Condpars> is the the name and type of parameters for conditions and actions, example: 'contract/string^'.

     

     

    It is recommended to add some standardized parameters. This is important to let the administrator at customer site use the Event Registry in a good way. These parameters are:

    EVENT_DATETIME
    USER_IDENTITY
    USER_DESCRIPTION
    USER_MAIL_ADRESS
    USER_MOBILE_PHONE
    ROWKEY

    ROWKEY parameter is used in Event actions to simplify navigation to the record, for example from an IFS Task or a mail message.

    The standard event parameters should be followed by the primary key.

     

  2. Add the call Event_SYS.Event_Execute to execute the Event in the business logic (plsql-file). First check if the event is enabled, if so construct an IFS_Message according to the specified Event and set the attribute values. The message is created with the same name as the event.

     

    Example

Adding Attachments to an Event

If you want the possibility to add Large OBjects (LOB's) to an event, e.g. as attachments to an e-mail Event action, you do that by using Event_SYS.Create_Attachment_Parameter. The Rowkey and Filename parameters must be added to the Event Parameters.

Event_SYS.Create_Attachment_Parameter(<Entity_Name>, <Event_Name>, <Event_Parameter>, <LOB_Type>, <Description>, <Filename>, <Attachment_Method>);

Event_Parameter The name of the attachment parameter
Lob_Type Type of LOB
CLOB for text attachment

BLOB for binary attachments

Description Description of the attachment. Visible in the client.
Filename Name of the attachment
Can be a static name (like Document.txt) or substitution variable
Attachment_Method Method used to fetch the attachment from the database. Only one parameter is accepted of the type ROWKEY.

Example (changes in registration of events)

Example (changes in runtime)

Custom Defined Events and Application Defined Events

The difference between Custom Defined Events and Application Defined Events and how to set them up in IFS Solution Manager is explained in IFS Administrators Guide.