Synchronization with external systems
The source-specific behavior on this page applies to the currently documented Czech eNeschopenka integration.
Incoming absence information
eNeschopenka information is received from ORDS.
ORDS provides eNeschopenka records in which a change occurred during the previous seven days. A record can therefore concern an eNeschopenka created recently or one created much earlier.
Each supplied record contains complete eNeschopenka information, not only the values that changed. The source can provide information about the beginning of incapacity, the end of incapacity, or both.
ORS does not provide information about deleted eNeschopenka records. AristoTelos can therefore create and update eNeschopenka records, but does not delete one merely because it is missing from a later import.
The imported scope does not include stay addresses or information about permitted walks.
Identifying the external absence
An eNeschopenka is identified by its decision number and personnel number.
AristoTelos expects the decision number to be unique. The personnel number identifies the employee contract to which the eNeschopenka belongs.
A person can have more than one personnel number. An eNeschopenka associated with one personnel number does not automatically apply to another personnel number of the same person.
A personnel-number change for an existing eNeschopenka is treated as an error.
Creating and updating eNeschopenka records
When an eNeschopenka received from ORDS does not exist in AristoTelos, AristoTelos creates it.
When it already exists:
- no update is made if the supplied information is unchanged;
- the stored information is updated if the supplied information differs; and
- changes affecting employee association, absence interval, or absence type are passed to synchronization to the shift plan.
Associating eNeschopenka with an employee
AristoTelos associates eNeschopenka with the employee contract through the personnel number.
If the employee cannot be found, the eNeschopenka is still created. The employee association and the related period time-off cannot be completed at that point.
Later import runs try again to associate eligible unassigned eNeschopenka records with an employee. Once the employee is found, the related period time-off can be synchronized.
Determining the period time-off type
Illness information and work-accident information from eNeschopenka determine the related period time-off type.
If the information cannot be associated with a period time-off type, the related period time-off is not created or updated.
If the eNeschopenka interval is invalid, the related period time-off is not created or updated.
Processing outcomes
The processing result records whether eNeschopenka information was created, updated, unchanged, or could not be processed.
The result also records situations in which:
- the employee could not be identified;
- the employee identifier changed;
- the period time-off type could not be determined;
- the interval was invalid; or
- the source information could not be processed.
Changes to eNeschopenka information are recorded in the audit log. The import result is available for review after processing.
Was this helpful?