Job Migrate WD2 Travels

Purpose and status

The job migrates travel expense reports from Webdesk 2 or the associated Domino system into the current Travel structure. In the job catalog it is inactive by default and interruptible.

Prerequisites

• A reachable Lotus Notes/Domino environment and valid access credentials must be available.
• The configured Domino database must be openable. The Webdesk server and database details are read from the "Setup" profile.
• The configured personnel number from the WD2 abbreviation must be assignable to a person in Webdesk.

Configuration

• Domino server (serverName), database path (dbPath), user name (username) and password (password).
• Search string (searchString): Notes search expression for the main travel documents to be migrated. The job automatically appends & migrated="" so that documents that have already been processed are not selected again.
• Domestic region: technical short name and UID of the Webdesk region for calculating the travel expense report.
• Trip type mapping: WD2 trip types or abbreviations to Webdesk trip types. Several import trip types can be mapped, separated by commas, to the same Webdesk trip type.
• Receipt type mapping: WD2 receipt types to Webdesk receipt types per trip type.
• Additional fields mapping: WD2 field name, optional JavaScript expression and current Webdesk additional field.

Behavior

• For each main travel document found, the associated documents of the trip are searched and transferred into a new Travel object with the status "Trip migrated".
• The assignment to the person is made via the WD2 abbreviation and the personnel number contained in it.
• The migrated field is set during the attempt; upon successful migration a timestamp is stored. If the person is missing or errors occur, the record is released again for a later attempt.
• Trips without matching or successfully migrated travel expense reports are not saved.
• A workflow history from Webdesk 2 is not transferred; the job does not create a workflow procedure for the migration.
• Processing can be interrupted. Individual errors are logged; an unhandled overall error ends the job with a job exception.