Time-Controlled Events MOD009DLK

Access

PM Administration → PMO: Control modules → Time-Controlled Events

Time-controlled events are programmable events which are run independent of save processes and other activities at defined points in time. For further information on events, see the PLANTA customizer help area.

Information

In this module you can review time-controlled events and edit their settings.
You can also view the event history.
In this module you cannot create or delete events. For this purpose, the respective Time-Controlled Events customizer module is used.

Module Structure and Functions

Information

Each event is displayed in a box which contains all of its data.
On the left hand side of the box, general event information is displayed.
On the right hand side, the interval settings of the event are displayed.
At the very right you will find the following buttons:
- Configure - via this button you can open the Configure User-Defined Interval module in which a user-defined recursion interval can be configured for an event.
- History - via this button you can open the Event History module which contains the history records of an event.

Event Settings

Information

In the Status field, the status of the event is specified and adjusted automatically by the system.
- The following Status values are used for time-controlled events:
  - 0: Waiting
    - The event is currently scheduled to run at another time.
    - This is the default status of any event at its creation.
  - 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.
- 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.
The Activated parameter determines whether the event is executed () or ignored ().
- An event is only executed if the Activated checkbox is activated.
Below the modifiable event settings, information on the next start time, the last execution and the number of effected executions is displayed.

See also: For a description of all module parameters, please click here.

Interval Settings

Information

By default, the interval settings consist of the Day, Time, and Recurs fields.
- Day and Time define the initial start time of the event.
- The Recurs listbox specifies whether and how often the event is to recur. The following entries are offered for selection:

Interval	Description
Once	The event is executed once at the planned point in time and does not recur.
Hourly	The event recurs every hour.
Daily	The event recurs every day.
Weekly	The event recurs every seven days.
Monthly	The 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-defined	A user-defined interval is specified. This allows for a more detailed configuration.

User-defined interval settings will only be displayed if the User defined setting has been selected in the Recurs field. The fields in question are output fields (grayed-out) which cannot be edited in this module.
- In order to edit user-defined interval settings, click on the Configure button. The Configure User-Defined Interval module will be displayed in which the changes can be made.
- Changes which are made in the Configure User-Defined Interval module are directly adopted in the output fields of the event record.

See also: For a description of all module parameters, please click here.

Standard Events

The following events are made available by PLANTA by default:

Nocturnal replanning	Carries out a nocturnal replanning (calculation of all planning objects).
Anonymize resources left	Data of Persons left such as name, first name, e-mail address, etc. are pseudonymized. The configuration is made in the customizing via listbox category 00000502. Here, you can enter the data items to be pseudonymized. The following parameters are defined per data item: Category: Python ID of the data item Number 4 digits: Pseudonymization code 1: ID. Here, the Python ID of the table which corresponds to the resource ID from 467 is entered. The HQL search_record is constructed based on this Python ID 2: pseudonymize, causes the DI to be filled with a random value 3: empty, important for, e.g., e-mail fields Number 9 digits.: Table ID to which the DI with this Python ID belongs In pseudonymization, IDs (codes) of persons/resources are changed via the Change Person/Resource ID function. In the case of an implementation of individual records with person data you therefore have to make sure that the DT and ID data item in question are additionally included in the mapping for Change Person/Resource ID. The technical person ID is not changed during pseudonymization. The sex of all pseudonymized persons is set to "male" by default.
Jira Hybrid synchronization Pulse Hybrid synchronization	Are used for the automatic synchronization of PLANTA project data with external systems (synchronization with PLANTA pulse and synchronization with Jira). The respective event is automatically activated when the API-URL is defined for the corresponding external system.
Send automatic e-mails for resource requests	Is used to inform the responsible department manager/project manager when resources are requested or approved/rejected when using the Resource request function.. The event is automatically activated when the global Resource requests active setting is set to "1" or "2".
Delete archived planning objects	Deletes archived projects which are older than 10 years and which are not assigned to any portfolio and do no contain any external links.
Start underposting correction	Is required for the automatic correction of underpostings. The event triggers a module (009DSP) every night, which in turn executes the Python code that checks whether an underbooking correction is to be carried out on this day. For detailed information on the automated correction of underpostings/overpostings, please click here.
LDAP Import	Carries out a nocturnal user import (at 4.30 am) via LDAP.
Notification function for missing bookings	If this event is activated, the missing bookings for the working days of the previous week are checked every Monday. If the working hours are exceeded by the hours of presence, the person concerned is informed by e-mail or, if activated, via adaptive cards.
Notification function for missing status report	If this is event activated, the system checks whether all projects in the current month have a released status report. For projects without a status report, the project manager is informed by e-mail or, if activated, via adaptive cards.

Notes

In general, events are deactivated by default and can be activated by activating the Activated checkbox. Some events are automatically activated if the underlying function is activated. See table.
You have to define the clientless session user for all events (except Send automatic e-mails for resource requests). In the PLANTA standard system it is PLSYSTEM. If you want to change the user, you have to use the Time-Controlled Events customizing module.