Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

My Agency & Company Setup - Custom field Mapping design

A new design to add field mapping configuration will be available in all agency & company configurations. The new mapping configuration provides more structured space to store the preferred command to a custom field.

Old design:

New design:

The click to the displays the details and allows to create, update, delete the mapping to the different interfaces.

Notes:

  • All field mapping will be migrate to the new design on agency and company level
  • Label in custom fields & actions are used form interface credentials label
  • Old XML mappings configuration can be use for import
  • Field Mappings which are configured and stored at company level with a disable Target GDS (System) are not displayed but once Target GDS is enabled mapping is shown
  • Company Setup will only show enabled Target GDS in the custom fields mapping
  • In case multiple Cytric and Generic HTTP (Atriis, Atlatos etc.) are activated in the agency, the new mapping will shown multiple Cytric and Generic HTTP. This will provide the possibly to store different mapping to e.g. Cytric. Mapping migration will automatically store existing mapping to all Cytric and Generic HTTP

Multiple Concur Credentials

We improved the usage of multiple Concur Credentials in a single agency. It is possible to store multiple Concur credentials (TMC-Tree, Non-Tree etc.) by providing a unique label. 

Note: Interfaces can only be added as a Umbrella Supporter or Circle Administrator. 


Approver/Arranger - visibility all fields

All Faces fields (same as traveler) are available for profiles which are only nominated as a Approver and/or Arranger. For this type of profiles all Faces fields can be used for update as they are available for travelers.

 

 

  • No labels