Event type
Modifying this entity requires certain user authorization. For more information, see User Groups.
Event type is the type definition for an Event created at runtime, either by a processing definition, a Timer or the system runtime. Event types are used in Event configurations to decide how to proceed when an Event of a specific type happens.
Event types can be system-defined or user-defined:
- System-defined Event types are created by iCore runtime. For more information, see System defined Event types.
- User-defined Event types are created by an iCore user/developer to represent key parts of a business flow. Example: File received, File fetched from ERP-system, XML-file created, EDI-file sent.
Properties
| Name | Type | Description |
|---|---|---|
| Created | DateTime | Date and time when the Event type was created. Automatically generated by the system. |
| Description | String | A brief description of the Event. |
| Entity type | EntityType | Specifies the entity type. The property is Read-only and is only displayed in filter listings to identify the entity type. It can be used for example when filtering on entities with a filter containing an 'All' part. For more information, see Entity filters |
| Error if no match | Boolean | Specifies whether an error is to be raised if no match is found for the Event configuration. Only applicable if Selection rule is 'AllMatch'. Options are:
|
| ID | Guid | The entity ID of the Event type. Automatically generated by the system. |
| Modified | DateTime | Date and time of the latest modification of the Event type. Automatically generated by the system. |
| Name | String | The name of the Event. In Edit mode, the Name property is Read Only. |
| Selection rule | SelectionRule | Specifies whether the Event is to execute all matching Event configurations or the single best match. Available options are:
An Event configuration based on an Event type with Selection rule = 'All match' does not need to have unique combination of Partner, Node type and Node type version as selection criteria. Consequently, you may set up several Event configurations based on the same Event definition with identical Partner, Node type and Node type version. if the Event type has Selection rule = 'Single best match', the combination of Partner, Node type and Node type version must be unique. See also Remarks below. |
| System Internal | Boolean | Specifies whether the entity is a built-in system entity (True) or a customized application entity created to meet the requirements of the business flows (False). A system entity is read-only and cannot be deleted since it may be used by system script(s). New system entities can only be added by certified iCore personnel. |
Remarks
A synchronous Event that gets status NoMatchFound will still be reported as failed to the creator of the Event.|
Selection rule in runtime
In runtime when an Event is created, the following applies:
- If Selection rule is 'Single best match', the first matching Event configuration is executed.
- If Selection rule is 'All match' and the Event is asynchronous, a new Event is created (Cascaded events) for every Event configuration that matches the selection criteria (Partner, Node type and Node type version).
- If Selection rule is 'All match' and the Event is synchronous, only the first matching Event configuration is executed. This is due to the fact that a synchronous Event expects a result before anything else may happen.