| Start Triggering via Job Timer (datrg1200m000) |  |
| use.session.to implement an 'active' trigger. By default, defined triggers simply wait until they are invoked. Through this session, a trigger can be started regularly without invocation from another application. Enter a trigger, or a range of triggers, and optionally specify a class, an event type and up to four attribute names plus values. For details, refer to the online field help. When executed, this session invokes the selected trigger(s) only once. To start the triggers multiple times, you must link this session to a job. Run the Make Job command to do so. The triggers are executed sequentially. The session gives a message if an error was reported. When running in a job this message is stored in the job history. You can also use this session to test a trigger implementation, by running it directly instead of creating a job. But note that the possibilities to define the event contents are limited, because you cannot define events having many attributes or having a complex structure. Related topics Triggering
Fields | Description
Class | A class to be set in the trigger or in the client application. In theory you can use any class name, but in practice the client application that receives the trigger may expect a specific class name. Additionally, the class name can be used in the trigger definition (e.g. in the trigger condition script or in the trigger action script). This field is optional.
Event Type | The event type to be set in the trigger. This can be a standard event, such as 'create', 'change' or 'delete, or a specific event such as 'printAcceptedOrders'. The trigger may require a specific type of event; in that case the name(s) of the event type(s) that you can use can be found in the trigger definition (e.g. in the trigger condition script or in the trigger action script). Additionally, the client application receiving the trigger event may expect certain attributes to be present. This field is optional.
Attribute | The name of an attribute to be handled by the trigger(s). The attribute name depends on the selected trigger(s). The trigger may use specific attributes in the trigger's condition or in the action script. Additionally, the client application receiving the trigger event may expect certain attributes to be present. Example:
Class: | BusinessPartner
Event Type: | change
Attribute Name: | businesspartner
Attribute Name: | status
This field is optional.
Value | The value for the attribute specified in the previous field. Example:
Class: | BusinessPartner
Event Type: | change
Attribute Name: | businesspartner
Value: | 2147483647
Attribute Name: | status
Value: | inactive
Note The attribute names and values depend on the selected trigger(s). This field is optional.