Configuring Align

The process for setting up and configuring the Veeva Align application is divided into two main areas: Vault platform setup and Align application setup. These can be set up independently of other activities, but Veeva recommends setting up Vault and then the Align application in the following order.

Vault Platform Setup

  1. Set up the Users & Groups tab.
  2. Configure the Settings tab, which contains Vault settings.

Browser Specific Setup

Align requires certain browser-dependent settings in order to function. Ensure your browser has the appropriate settings:

  • Google Chrome – Navigate to Chrome Settings -> Privacy and security > Third-party cookies and ensure Allow third-party cookies is selected
  • Safari – Navigate to Settings -> Privacy and ensure the Prevent cross-site tracking check box is not selected

Application Setup

  1. Configure and prepare Align.
    • Activate the country__aln records related to the data in Align—Territories, Accounts, addresses, etc.
  2. Configure the Vault CRM integration.
  • Configure the Integration Users in Align and Vault CRM
  • Create a Vault CRM instance (vault_crm_instance__aln) record to construct an integration connection to a Vault CRM instance.
  • Complete field mapping for each Vault CRM instance.
  • Activate Vault CRM instance countries. This step is optional.
  • Configure the Vault CRM instance import using the Vault Scheduler.
  1. Add the following Align metadata, either manually or using the Align Data Loader, in the order listed:
  • Add Field Forces (field_force__aln).
  • Add Field Force Products (field_force_products__aln). This step is optional.
  • Add Footprints (footprint__aln). This step is optional.
  • Add Footprint Geographies (footprint_geography__aln). This step is optional.
  • Add Territories (territory__aln)
  • Add Territory Products (territory_products__aln)
  • Add Geographies (geography__aln)
  • Add Account Assignment rules (account_rule__aln and account_rule_criteria__aln)
  1. Import the following data from Vault CRM.
  • user__sys

    • account__v

    address__v

    child_account__v

  • product__v

    • product_metrics__v (optional)

  1. Assign accounts and users to territories.
  • Data load any explicit account assignments. This step is optional.
  • Execute and test Account Assignment Rules. Commit the rules to Align when you are satisfied with the Rules Preview.
  • Push the changes to Vault CRM