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 and server startup events. Determines in what sequence the events are executed.

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 order applies: 1) Java, 2) Jython, 3) Python.

DI065862 Event type

Determines the event type of data-driven events.

Values

ValueDescription
714: Pre-insertIs executed for insert tasks before saving.
715: Pre-updateIs executed for update tasks before saving.
716: Pre-deleteIs executed for deletion tasks before saving.
717: Post-insertIs executed for insert tasks after saving.
718: Post-updateIs executed for update tasks after saving.
719: Post-deleteIs executed for deletion tasks after saving.
777: Pre-saveIs executed for insert and update tasks before saving. A pre-insert and pre-update-event. 
778: Post-saveIs executed for insert and update tasks after saving. A post-insert and post-update-event at the same time.
883: On-changeIs executed before saving whenever a data field is changed.
7: Timed eventIs executed at a particular points in time regardless of changes made to data (time-controlled events)
8: Simple repeatingSimplified, time-controlled event which is executed every x minutes (only used internally)
9: StartupEvent which is only executed once upon each server start
10: Session startupEvent which is executed each time the user logs-in to the session.


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:

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. Its 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.

DI066059 Recurs: Monday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066060 Recurs: Tuesday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066061 Recurs: Wednesday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066062 Recurs: Thursday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066063 Recurs: Friday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066064 Recurs: Saturday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066065 Recurs: Sunday

Parameter for user-defined time-controlled events. Defines whether the event can run on the respective weekday.

DI066066 Never ends

Parameter which determines the end of a user-defined time-controlled event. If the parameter is activated, the event has no end.

DI066067 Ends on

Parameter which determines the end of a user-defined time-controlled event. Here you can specify the date on which the event is to be terminated.

Note

  • In order for the event to be terminated on the defined date, you have to activate the checkbox of the DI066069 parameter.

DI066068 Ends after

Parameter which determines the end of a user-defined time-controlled event. Here you can specify the number of repetitions after which the event is to be terminated.

Note

  • In order for the event to be terminated after the defined number of repetitions, you have to activate the checkbox of the DI066070 parameter.

DI066069 Ends on - checkbox

Parameter which determines the end of a user-defined time-controlled event. If the parameter is activated, the event ends on the date which is specified in the DI066067 Ends on parameter.

DI066070 Ends after - checkbox

Parameter which determines the end of a user-defined time-controlled event. If the parameter is activated, the event ends on the date which is specified in the DI066068 Ends after parameter.

DI066072 Recurs

The frequency at which a time-controlled is executed.

IntervalDescription
OnceThe event is executed once at the planned point in time and does not recur.
HourlyThe event recurs every hour.
DailyThe event recurs every day.
WeeklyThe event recurs every seven days.
MonthlyThe event recurs the next month on the same week day, e.g. on the first Monday or on the last Friday of a month.
Yearly

The event recurs on the same date in the following year. Events on 02/29 only recur in leap years

User-definedA user-defined interval is specified. This allows for a more detailed configuration.

DI066074 Recurs every (unit)

Time unit which defines the interval between repetitions of a user-defined time-controlled event. The exact interval is defined in numbers using the DI066057 Recurs every (number) parameter.

Values

  • minutes
  • Either
  • days
  • weeks
  • months
  • years

DI066077 Last execution date

Date of the last execution of a time-controlled event

DI066078 Last execution time

Time of the last execution of a time-controlled event

DI066092 Number of executions

Specifies how often a time-controlled event has already been executed.