DT312 Events

DI065523 UUID

Universally Unique Identifier (UUID) of an event. It is created automatically.

DI065526 Changed on

When a record is modified, the modification date is automatically entered here.

DI065529 Changed by

When a record is modified, the ID (code) of the logged-on user is automatically entered in this field.

DI065537 Function name

Full name of the (static) class method to be executed including its path.

Examples

ppms.start_migration.doSomething
de.planta.server.events.EventManager.insertNewEvent

DI065538 DT

ID of the data table to which a data-driven event refers.

DI065543 Condition

Condition which analyzes a Jython function before the start of a data-driven event. If this function returns True, the event is started.

Note

If the condition is empty, the method is always executed without Jython check function.

DI065544 Parameter

Freely definable string for the method to be executed.

DI065545 Activated

Values

- The event is executed.
- The event is ignored.

DI065557 Position

Integer value for sorting data-driven events.

Details

If several data events are triggered at the same time because they have been defined in the same table for the same event type, the events will be executed starting at the lowest position number.
If two data events have the same position number the following sequence applies: 1st Java, 2nd Jython, 3rd Python.

DI065862 Event type

Determines the event type of data-driven events.

Values

Value	Description
1: Pre-insert	Is executed for insert tasks before saving.
2: Pre-update	Is executed for update tasks before saving.
3: Pre-delete	Is executed for deletion tasks before saving.
4: Post-insert	Is executed for insert tasks after saving.
5: Post-update	Is executed for update tasks after saving.
6: Post-delete	Is executed for deletion tasks after saving.
7: Pre-save	Is executed for insert and update tasks before saving. A pre-insert and pre-update-event.
8: Post-save	Is executed for insert and update tasks after saving. A post-insert and post-update-event at the same time.
9: On-change	Is executed before saving whenever a data field is changed.

See also: Programmable Events

DI065864 Function type

Determines which type of method is called.

Values

1: Java
2: Jython
3: Python

Currently, only Jython and Java functions are supported for time-controlled events.

DI066389 Name

Name of a time-controlled event

The parameter can be edited in the following module by users with modification rights:

Time-Controlled Events

DI065866 Status

Status of a time-controlled event. Is automatically adjusted to the execution of an event.

Values

0: Waiting
- The event is currently scheduled to run at another time.
1: Is executed
- The function assigned to the event is currently running.
2: Terminated
- The event was terminated without errors and will not be executed again.
3: Failed
- An error has occurred during the last execution. The event will be executed again after server restart.

Note

A manual change of the status has no influence on whether an event is executed again or not. Execution only depends on the Activated parameter as well as of the interval settings of the event.

DI065871 Starting date

Date at which the time-controlled event will be started the next time.

DI065872 Starting time

Time at which the time-controlled event will be started the next time on the defined date (DI065871 Starting date).

DI065922 Data table

ID of the data table which a data-driven event refers to.

DI065923 Data table

DI066054 Day

This parameter serves to define on which date a time-controlled event is to be executed for the first time.

DI066055 Time

This parameter serves to define at which time of the day a time-controlled event is to be executed for the first time.

DI066057 Recurs every (number)

Interval (in numbers) between the recursion of a user-defined time-controlled event. The unit is defined via the DI066074 Recurs every (unit) parameter.