All configurations whether Expense Feed, HR Feed...etc. should follow these following scenarios

• Set the "Static Approver" on the Airportal people Approvers tab

• Create the rule class with NO approvals to bypass approvals (Insert what Becky does to make this happen other than scripts hard coded rule class values to bypass approval?

• Build U37 and U38 in Airportal as described in Approval by Travel Manager – Christopherson Business Travel (cbtravel.com)

  • Take values from existing "Managers" in travelers' profiles, or take values from HR feeds/expense feeds...etc.

• Create the rule class with NO approvals to bypass approvals 

  • In Travel Policy-Travel Policy Builder setup a rule under Misc-Trip does not have a remark-Contains ex: U56-EXECUTIVE TRAVEL CLASS

• Airportal currently cannot support this, and we should be not taking clients live until we have finished the dev ticket that has been created for Airportal to be able to support this.

• Temporary solution:
  

  • BUILD U37 & U38 as described in- https://support.cbtravel.com/hc/en-us/articles/30912108904851-Approval-by-Travel-Manager. This will be used for ALL travelers, even those with the "Static approver"

    • Static Approver Rule class- Make sure this approver is listed as an option in U37. then go into all existing Travelers for that Rule class and set the static approver in each of those profiles as the "Manager"/approver.  Then we'll need to manually keep track of enrollments as travelers are built to check and validate, they are selecting the correct approver based on their rule class

• Airportal currently cannot support this, and we should be not taking clients live until we have finished the dev ticket that has been created for Airportal to be able to support this.

• Temporary solution:
  

  • BUILD U37 & U38 as described in- https://support.cbtravel.com/hc/en-us/articles/30912108904851-Approval-by-Travel-Manager. This will be used for ALL travelers, even those with the "Static approver"

    • Static Approver Rule class- Make sure these approvers are listed as an option in U37. then go into all existing Travelers for each Rule class and set the appropriate static approver in each of those profiles as the "Manager"/approver.  Then we'll need to manually keep track of enrollments as travelers are built to check and validate, they are selecting the correct approver based on their rule class

    • **RH has an HR Feed that CSM's monitor for NEW enrollments to go in and manually add the correct manager based on the rule class that is chosen.

    • ****Stephen testing a new solution within Faces 

**For clients with Expense feeds/HR feeds and they are LIVE on Faces it's a scenario where they set approver based on rule class but we need to manage it through U37, we need to work with CSM's so they are aware of the client and the situation so they can go in and manually add the correct approver based on the rule class that was chosen.