Concur implementation is different such that the setup is done for each Entity and not for the whole Concur Site (or Faces Agency) Wolfgang Schuller please review. This means that for each entity whose travellers have to be synchronized via Umbrella Faces, a request token has to be requested from Concur.
Token Credentials sample:
Entity/Outtask ID: 110034
Client_UUID: 79840cd9-5989-4675c-a254-3cdkkkdddeeebb178
Request_Token: at-2t4r87t4rirtkugjsgf728
Procedure
- Prior to the opening a case for the Token Credentials, the token requests should be approved by Denby Bruzas from Concur
- In the application for the request token, the token cases should include the phrase “API token request” in the subject line. This will allow Concur's automated report to pull these cases from the queue for priority sorting. Otherwise the cases are frequently mis-assigned and delayed
- After receiving the request token you send it to Umbrella Support asap (the tokens are only valid for 12 hours). We appreciate receipt of the tokens between 06.00 AM - 14.30/15.00 PM CET latest. With these, we generate "refresh tokens" which are then given in in Faces.
Please open a case to Concur requesting the access control travel profile API credentials to use the Umbrella Faces App. Please also include a list of your Concur site id to this request along with the Managing TMC site ID (Vendor Site ID) that controls your list of clients. If you have multiple Vendor Site ID's (i.e. EMEA vs USA) then provide all.
Note:
- At the very first stage of implementing Concur we also activate the Interface on the agency and activate Concur polling so that profile updates from Concur are also sent into Faces.
...
- Umbrella Faces to Concur = real time Synchronization
- Concur to Faces = Concur polling (pulling the updated profiles from Concur) occurs every
...
- 15 minutes, at
...
- 5 mins, 20 mins, 35min past and
...
- 50 minutes
...
- past every full hour.