Job Create Reallocations

The Create Reallocations job automatically creates an account correction workflow process for selected active persons. The first work step of the generated process is accepted immediately. This allows, for example, reallocations or overtime payouts to be processed according to the workflow defined in the process.

Prerequisites

• The TA and Workflow modules must be active.
• A current process definition configured as an account correction process must be selected. The process definition provides, among other things, the account, correction type, and minimum and maximum values.
• The persons to be processed must be active users and have a TA ID. Persons without a TA ID are skipped.
• The accounts referenced in the process definition must be valid if minimum or maximum values are read from accounts.

Process

1. The job determines the target or proposal date.
2. It reads the selected groups from the configuration and derives the persons from them. The client selection in the form serves to restrict the available groups; the groups subsequently selected are processed.
3. Persons for whom a matching open or completed process already exists for the same process definition and the same target date are not processed again. If a person is contained in multiple selected groups, they are only considered once.
4. For each remaining person, the account values described in the process definition are read. By default, a process is only created if the minimum value is less than or equal to the maximum value.
5. After successful creation, the first activity is accepted automatically. If mail notification is enabled, a mail is then sent to the affected person.

Job configuration

Date logic

If the reference date is left empty, the job uses the date default of the selected process definition. In the code, the defaults ultimoLastQuarter, ultimoLastMonth and yesterday are implemented. An unrecognized or missing default falls back to the current date.

The group assignment is determined using the current execution date, independent of the reference date. The reference date therefore controls the account value determination and process creation, not the selection of group members.

Operational notes

• The job can be run repeatedly. For the same person, process definition and target date, no further matching process is created.
• Persons without a TA ID, as well as persons for whom the value check is not satisfied, are skipped.
• Errors during the processing of an individual person are logged; processing of the remaining persons continues. If processes are missing, check the job log and the configuration of the process definition.

Felder