You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 19
Next »
To download above documents:
Click on desired document
Click on cloud symbol in the upper right-hand corner of your screen, this will allow you to download, save and/or print
Click on video above to see full demonstration (Coming soon)
Pre-Trip Approval (PTA)
Overview
Pre-trip approval (PTA) is a process put into place to better manage business travel by allowing a trip to be approved or declined before it is ticketed. It offers an automatic method of controlling travel spending by designating travel approvers who can approve or deny a user's travel request.
Useful Terms:
Primary approver: User responsible for approving or declining trips triggered by the process.
Secondary approver: User identified to take action for trips triggering the process if the primary approver does not take action within the configured amount of time.
Expired Bookings: Bookings which have not been approved or declined by the primary or secondary approvers within the configured amount of time. These are not automatically canceled.
Benefits, Limitations and Need to Know
Task | Process / Helpful Hint |
Benefit | Robust policy capabilities – Deem uses JavaScript, which allows for creativity when configuring approvals or notifications. Allows for offline and online approvals Simple and quick process for Approver, simply click on the Approve or Decline button within email Set up notifications and/or approval based on groups
|
Limitations | Offline bookings – Etta is limited to what they can pull from offline bookings Approvals and notifications are completed through email only Single layer approval process. Unable to require approval from more than one person
|
Need to Know | |
Task | Process / Helpful Hint |
Contact Deem Channel Sales Director | Statement of Work (SOW) is required and there is an initial cost to have Pre-Trip Approval set up. Your Deem Channel Sales Director can discuss this further with you. Deem will help you set up your first site. Once you have Pre-Trip Approval set up on your Deem company domain, you will have the ability to program PTA on each of your clients’ sites as needed.
|
Open Support Ticket | |
Task | Process / Helpful Hint |
Approvals or Notifications | |
Policy | |
Queues | |
Configuring PTA
Task | Process / Helpful Hint |
Custom Field Collection | Configure pending queue under Custom PNR Under Line No. enter line number which script will reside in your mapping. In this example we are using line 159 PNR Field Type: select Pre-Trip Approval Custom PNR Requirement: Enter Script Requirement Type: Select Script GDS: Click on GDS your mapping should write to
The below example Is for a Sabre client, script written to line 159 follows the screen shot. You can adjust the output based on the GDS you are writing to PNR Script: //Ticketing Field for PTA Pending Approval function zeroPad(num,count) { var numZeropad = num + ''; while(numZeropad.length < count) { numZeropad = "0" + numZeropad; } return numZeropad; } if ((UserPnrData.DataType=="new" || UserPnrData.DataType=="purchase_hold")&&(UserPnrData.UserBooking.PreTripApprovalInfo.CurrentApprovalState=="WAITING_FOR_APPROVAL")){with (UserPnrData.UserBooking.AgencyTransactionDate) { var day=UserPnrData.UserBooking.AgencyTransactionDate.Day; day=zeroPad(day,2); out.print("7TAW" + day + Month + "/HOLD");}} |
Approved, Ticketed/Declined and Expired Queues | Programmed under Agency Configurations Enter Pseudo-city and Queue for each Approved, Declined and Expired bookings Enter the time window for the primary approver to approve or decline the trip, and the time window for the secondary approver. The primary approver window is best set to 4 – 6 hours, with the alternate approver well before the 24-hour void window Click on Save
|
Setting Passenger Name Record (PNR) Configuration
Task | Process / Helpful Hint |
Tip | |
| |
Setting Up Approvals and Notifications (Custom fields)
Task | Process / Helpful Hint |
Creating Custom Field Collection | Enter the collection name into the Name field for each collection, such as PTA, pretripapproval or pretripnotification. Use a label which clearly defines the collection. Be sure to click the checkbox for Ask for User Input on the Purchase Page. This will display on the Trip Purchase page, allowing travelers to enter additional notes to approver.
|
Creating Custom Fields | Click the radio button for Approval required or Notification only Decide whether to send the approval email to the manager within the profile, or to a default approver If you would like the manager listed in the traveler’s profile to receive the approval/notification email, click the box next to Send approval email to traveler’s profiled approver Leave unchecked if you would like the approval/notification email to be sent to the default approver email, which you will need to provide in the next section Note: If the setting for "Send approval email to traveler’s profiled approver" is used, the default approver email value is ignored unless the traveler doesn't have a profiled approver (secondary approver field is still applicable)
Enter the email addresses for the default approver and the secondary approver. If the default approver has not approved or declined the itinerary within the defined period, an email is sent to the secondary approver default email address Decide whether or not to automatically cancel declined itineraries Click the Advanced link at the bottom of the Field Type Preference section to enter the JavaScript criteria for this field
|
Use Case JavaScripts | PNR and Pre-Trip Approvals JavaScript are in many cases interchangeable. For further Information: JavaScript Examples Need further help creating a script, please open a Support Case
|
Example Script | //Alaska and Hawaii if((UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="ANC")|| (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="FAI") || (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCodee=="HOM")|| (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="JNU") || (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="HNL") || (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="KOA") || (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="LIH") || (UserPnrData.UserSession.AirSearch.FlightLeg[0].DestinationAirportCode=="ITO")) {out.print("true");}else {out.print("false");} |
Add to Custom Field Set | Once you have completed programming PTA collection, you will then need to add it to the custom field set |
Setting up Permissions
Task | Process / Helpful Hint |
Designating Approver Status Manually | |
Assigning Manager Manually to Traveler Profile | Click on User tab Click on Personal and Employee Info Click on Travel Approver Name Select Approver from list Click on Save
|
Upload Approver | You can upload a file to establish user-approver relationships. Templates are available under the Profile tab. Before preparing your profile upload, consider, as a profile upload can be damaging if not managed correctly. See Preparing a Profile or Delegate Upload File, and keep in mind the following: Follow these general steps when assigning the approver role to any profile: Consulting the User Profile Fields page, locate the Role column (roleSet.role) in the new file for each approver Enter ROLE_TRAVEL_APPROVER in the Role column (roleSet.role) for each user to be designated as a travel approver Upload this new file to establish the approvers in your site
Follow these general steps to assign approvers to users: After uploading the file to establish approvers in your site, you can then assign approvers to users Consulting the User Profile Fields page, locate the Travel Approver ID column (userInfo.travelApproverID) in the new file for each user Enter the external ID of the approver for this user, defined previously as ROLE_TRAVEL_APPROVER in the Role column (roleSet.role). For example, if the userInfo.travelApproverID value is 28846, then the user whose external ID is 28846 should already have been uploaded and already have been assigned the role of Travel approver (ROLE_TRAVEL_APPROVER) in the Role column (roleSet.role). Upload this new file to establish the approver-user relationships
Ensure that all custom fields, corresponding collections, and custom field sets are created first before uploading profiles containing custom fields. If not, the upload will possibly fail.
|
Pre-trip Offline booked PNRs
Task | Process / Helpful Hint |
Steps | Deem processes reservations based on PTA set up on site If reservation is not out of policy it will be sent back to ticketing queue for processing If reservation is out of policy an email will be generated to the approver. once approved or declined it will be sent back to the agency for processing Special Note: In the event the fare will expire, the hotel is within the cancellation policy, or a trip will commence within the first approvers time window, the system will auto approve the reservation. This is not a configurable item.
|
Pre-trip approval messaging
Task | Process / Helpful Hint |
Pending Approval Message | To Traveler – ‘Your trip is pending approval for travel. You will be notified once it is approved, and the trip will be sent to [agency name] for processing. Online changes are not allowed until the tip is approved for travel, please contact your agency directly for changes.’ To Approver 1 – Pre-trip approval required [rules description]
|
Reminder Approval Message | |
Approval Message | To Traveler – ‘Your trip has been approved for travel.’ Existing confirmation message – Your reservation has been completed. To Approver 1 – Pre-trip approval has been received and the trip has been sent to [agency name] for processing To Approver 2 – Pre-trip approval has been received and the trip has been sent to [agency name] for processing
|
Declined Message | To Traveler – Your trip has been declined for travel. The trip has been sent to [agency name] for processing. To Approver 1 – This trip has been declined for travel and sent to [agency name] for processing To Approver 2 – This trip has been declined for travel and sent to [agency name] for processing
|
Declined Auto Cancel Message | To Traveler – Your trip was declined for travel and auto canceled. [existing auto cancellation message] To Approver 1 – This trip was declined for travel and auto canceled To Approver 2 – The trip was declined for travel and auto canceled
|
Expired Approval Message | To Traveler – Pre-trip approval was not received for this trip. The approval process has expired, please contact your agency for further assistance. To Approver 1 – Pre-trip approval was not received for this trip and the approval process has expired. To Approver 2 – Pre-trip approval was not received for this trip and the approval process has expired.
|
Notification Only Email | |
pre-trip Status
Task | Process / Helpful Hint |
Waiting for Approval | Bookings have not been approved or declined and are within the configured amount of time for review |
Trip Declined | Bookings have not been approved or declined and are within the configured amount of time for review |
Canceled | Bookings have been canceled either manually or by the pre-trip approval process if pre-trip approval has been configured to auto-cancel Note: Remember to manually cancel any expired trips if pre-trip approval is not configured to auto-cancel. Although the air ticket is not issued, the trip is not auto canceled and could incur hotel penalties. |
Pending Approval | These trips have been canceled either manually or by the pre-trip approval process if pre-trip approval has been configured to auto-cancel Note: Remember to manually cancel any expired trips if pre-trip approval is not configured to auto-cancel. Although the air ticket is not issued, the trip is not auto canceled and could incur hotel penalties |
Confirmed | Bookings which have been approved by primary or secondary approver and sent to ticketing |
Add Comment