Vergleichsreport

Purpose

The job synchronizes absences and intraday time intervals from the TA system unidirectionally into the groupware calendar. It writes or deletes calendar appointments in groupware, but does not change any TA data.

The job is inactive by default in the job catalog and requires the TA and Groupware modules.

Population of personsPersons

• Without a client and without a group, the persons designated for groupware synchronization are processed.
• With a client and without groups, the currently valid persons of the client are processed.
• With groups, the currently valid persons of all selected groups are merged.
• Persons who, according to the groupware configuration, should not be checked are removed.

Job configurationConfiguration

• Synchronization Typetype: 0 (Synchronize all Absence Reasonsabsence reasons) synchronizes approved and unapproved absence reasons; 1 (Synchronize approved absence reasons only approved Absence Reasons) only approved absence reasons. A new configuration is preset to with 0. If the value is missing, the code uses only approved entries by default.
• Months into Pastin the past and Months into Futurein the future: The synchronization period. A new configuration is preset to with 0 for each (current day only); if the XML values are missing, the code defaults to one month each.
• Description Prefix for Events created (Prefix)exported appointments: Prefix of the generated subject texts (preset wd_); the fallback is the job default setting or wd3_.
• Postfix Suffix for approved Entriesabsences and Postfix Suffix for unapproved Entriesabsences: Postfixes for approved and unapproved entries respectively (preset (allowed) and (not allowed)). If both are identical, an underscore is appended to the second one.
• Client and Groups: Restriction of the population of persons.
• Use universal layertime configuration: Determines whether the list Absence Codes reasons to Synchronizesynchronize offers the universal absence reasons or the absence reasons of the time system for selection.
• Absence Codes reasons to Synchronizesynchronize: List of TA absence reason and optional custom subject. Without an explicit list, the job's default absence reasons are used; if these are also missing, the job aborts with an error.
• Synchronize half-day absences?: Enables synchronization of half-day entries.
• Synchronize partial day absencestime corrections in the future?: Enables synchronization of intraday absence intervals (journal/booking intervals). This variant is currently not supported for Lotus Notes.
• Expression for Calendar Entry Subjectcalendar entry subject: Optional expression. Among others, $person, $calendarTimeRangeEvent, $wdPrefix, $wdPostfix, $approvalPostfix, $nonApprovalPostfix, $absenceReason, $requestComment and $dateFormatter are available in the context.

Synchronization behaviorBehavior

• For each checked person context, TA entries and groupware appointments are matched via comparison keys.
• Missing appointments are created or updated in groupware.
• Appointments that no longer exist in the TA system are only deleted if they were originally created by Webdesk. A stored Webdesk marker value is used for this.
• Before processing, the job checks groupware synchronization readiness. Missing permissions or person-specific errors are logged and skipped; an error for one person does not automatically end processing for all other persons.
• An interruption ends further processing after the current person step.

When activating, check in particular the time range, the absence reasons to be synchronized, and the marking of appointments created by Webdesk.