Custom event types

If the provided event types are not suitable for a specific purpose in a process, you can create your own custom event type. You can create custom Asynchronous and Timer event types that can be used in the same ways as other event types. You cannot create custom Exception events.

Another process can listen for that event, filter it based on order quantity, and then trigger a particular behavior. For instance, the other process can send an email or route a form or data to an inventory clerk or a production manager.

For instance, suppose you want to provide a mechanism to inform a process by way of an event that a purchase order has been created. To do this, you can create a PurchaseOrder event type that contains the purchase order number, the name of the company placing the order, the part number being ordered, and the quantity of the order. You then create a process that throws this event type when the order occurs.

Creating subfolders in the application tree is a recommended way of organizing your assets inside the application. For example, create a folder named customEvents to store custom events.

When you create a custom event type, the combined length of the Name field and the Enter Or Select The Parent Folder field must not be greater than 260 characters. For example, if the name of the event is SampleEventTypeDemo , and the parent folder path is /SampleDemo-AssemblerService/1.0/CustomEvents/ , the combined name is: /SampleDemo-AssemblerService/1.0/CustomEvents/SampleEventTypeDemo . The combined length is 65, and is an allowed name.

Create custom event types

* New for 9.5 *

  1. Select File > New > Event Type. You can select an event that is located in the current application or in another application that is either local or remote.

  2. In the New Event Type dialog box, in the Name box, type a name for the event type that is meaningful and descriptive to other users.

  3. (Optional) In the Description box, type a description of what the event type is used for.

  4. (Optional) Create a subfolder by completing the following steps:

    • Below the application tree area, click New Folder.

    • In the New Folder dialog box, in the Folder Name box, type a name for the folder and click OK.

  5. In the Enter Or Select The Parent Folder box, specify the path to the event location within the application hierarchy. The path must include the name and version of the application and, optionally, subfolder names. You can either type the path or select the required location from the application tree. The application you choose can either be local or remote. An example of a valid path is /MyApp/1.0/customEvents.

  6. Click Next.

  7. Under the Event Category label, select the Asynchronous or Timer option. (See Event categories .)

  8. Import an XML Schema Definition (XSD) file to use for event data by completing these steps: (See Creating data schemas for event data and event message data .):
    • In the Data Schema tab, click Import Schema.

    • In the Data Schema dialog box, select the location of the XSD file in the application tree, and then click OK.

  9. Import an XSD file to use for additional event message data by completing these steps: (See Creating data schemas for event data and event message data .):

    • In the Message Schema tab, click Import Schema.

    • In the Message Schema dialog box, select the location of the XSD file in the application tree, and then click OK.

  10. In the Configuration tab, configure the custom event type by completing these steps:

    • Below Event Priority, select the priority level of the event type. The value of 1 represents the lowest priority and 10 represents the highest priority.

    • Below Event Severity, select LOW, MEDIUM, or HIGH to set the severity of the event.

    • Below Event State, select Active or Inactive. Select Active if you want the event type to be active when it is first created.

    • Below Event Activation, select Upon Notification or Never. Upon Notification specifies that the event is deactivated after it is received.

  11. Click Finish.

Delete custom event types

* New for 9.5 *

Do not delete an event type that is being used in any process diagram. If you try to delete such an event type, an error dialog box appears. If you are not using a custom event type, you can delete it.

In the Applications view, right-click the Event from an Application version,

and select Delete.

// Ethnio survey code removed