The Travel Dates Confirmation process enables the relocation coordinator to ensure the accuracy and compliance of travel dates, based on the confirmation date submitted by the remote employee. After completing the remote work period, the employee will receive a link to confirm the specific dates for their travel.
Note: Make sure that the respective Quick Workflow supporting this feature is active before using it to fully utilize this feature.
Employee Confirming Travel Dates
The Travel Date Confirmation page can only be accessed via the link on the email automatically sent by a Quick Workflow (QWF) and can only be accessed by a logged-in user. All unauthorized attempts to access this link will result in an "Access Denied" message.
The form includes a welcome message step, and the travel destination location which includes the
Assignment Destination Start Date Start Date (ASSIGNMENT_DESTINATION!START_DATE) and
Assignment Destination End Date (ASSIGNMENT_DESTINATION!END_DATE)
Note that upon approval of remote work, the Assignment Destination Start Date and End Date values are copied to Original Start Date and Original End Date fields.
The employee will be then asked when the employee Arrives and Leaves the country which will be treated as the confirmed dates.
The submitted dates of the employee will be confirmed travel dates and will be the new values of the 'Start Date' and 'End Date' fields.
The employee then needs to click the
button to submit and confirm the entered details.
Once the form is submitted, the 'Travel Dates Confirm' field will be updated with a value of 'Yes' in the internal case record screen.
In the event that the submitted confirmed dates exceeds the approved dates for a location, an email and notification will automatically be sent through a Quick Workflow to the relocation coordinator.
If the employee has already confirmed the travel dates, attempting to access the link again will result in a notification that the dates have already been confirmed. The employee will no longer be able to make changes to the travel dates unless the coordinator uses the 'Undo' feature.
Internal User and the Confirmed Travel Dates
The relocation destination screen allows the internal user or the coordinator to check the confirmed travel dates. This feature makes it easy to identify any deviations from the expected travel dates and generate reports to review any dates that do not comply with policies.
The following fields will store the originally approved start and end dates:
Original Start Date (ASSIGNMENT_DESTINATION!ORIGINAL_START_DATE) and
Original End Date (ASSIGNMENT_DESTINATION!ORIGINAL_END_DATE)
These fields are read-only fields on the internal assignment destination page and would appear for all Assignment Destinations associated with the move. Note, that the original start and end dates fields will not appear on the Mobility Manager Widget.
When the Assignment Destination record associated with a move has an Approval Routing Stage equal to Approval Confirmed, the following values will be observed:
Original Start Date = Assignment Destination Start Date
Original End Date = Assignment Destination End Date
After the employee confirms the travel dates post-trip, the Assignment Destination Start Date and Assignment Destination End Date fields reflect the new values (if changed).
The 'Travel Dates Confirmed' (boolean) checkbox field will also be updated with a value of 'Yes' or checked.
Undo Button
If an employee accidentally submits incorrect dates, internal user can reset the confirmed dates by clicking the
button. This is supported by a Quick Workflow (QWF) that notifies the employee to confirm the dates again and an email will be sent for re-confirming.
Note, that using the Undo function will clear the Original Start and Original End Date values regardless of if they were populated by the confirmation process or an approval process.
This button is dependent on Execute page rights in the Role Maintenance Screen. If the Original Start and End dates are important in any process, it is not recommended to use this feature. In such cases, it should be hidden by removing execute rights to the Assignment Destination page.
Things to Note
The following Quick Workflows are created in v24.2 to support this feature and set inactive by default:
'Send Travel Date Confirmation to Employee'
'Remote Work Confirmed Dates Exceed Approved Dates'
'Send Travel Date Reconfirmation Notification to Employee'
When setting up this feature, ensure that the “Send Travel Date Confirmation to Employee” QWF is activated as the whole feature of confirming a travel date is based off of this QWF.
The 'Travel Dates Confirmation' checkbox is set to read only via default by a DDMO override. Removing this override is highly discourages for it could affect other downstream processes.
The 'Remote Work' term used in this form can be changed in the 'Remote Work Label Override' field within the Remote Work Request Configuration settings.








