Basic Integrated Territory Feedback Configuration

Configuring Integrated Territory Feedback requires processes in both Vault CRM and Align:

Who can use this feature?

  • Browser Users
  • Users require an Align License
  • Business Admin Users

Configure Integrated Territory Feedback in Align

To configure Integrated Territory Feedback in Align:

  1. Navigate to Align Settings.

  2. Populate the following Align Settings with a comma-separated list of Align API field names from the appropriate objects:

    • feedback_account_assignment_columns__v – List of fields on the following objects that display on the Account Profile of Integrated Territory Feedback:

    • account__v
    • address__v

    • product_metric__v – Product metrics for any products assigned to the model territory display as long as the Product Assignment is active during the model's planned publish date

      For example: account__v.last_name_cda__v, account__v.specialty_1__v, account__v.country__v

    • account_card_fields__v – List of fields that display on the Account Profile of Integrated Territory Feedback

      The following objects are supported:

      • account__v
      • address__v
      • product_metric__v

      For example, account__v.name__v, product_metric__v.trx__v, account__v.specialty_1__v,address__v.name__v

  3. Navigate to the appropriate aln_project__v record.

  4. Populate the feedback_instructions__v field with instructions for users. This field displays in the Instructions section in the Territory Feedback tab in Vault CRM.

    This field supports Markdown formatting. When entering a value in this field, a preview of the formatted text displays below the field entry area.

  5. Navigate to the Configuration tab of the Vault Administration page.

  6. Edit the challenge_reason__v picklist on the following objects:

    • mc_cycle_plan_target__v – Defines the list of reasons for challenging a target
    • aln_account_territory_model__v – Defines the list of reasons for challenging an account assignment
  7. Select Save.
  8. Configure the Approval Process.

Integrated Territory Feedback uses lifecycle states on the aln_territory_model__v object to control what actions are available to various user roles. See Managing Object Lifecycles for more information on managing lifecycle states.

Configuring Integrated Territory Feedback in Vault CRM

To configure Integrated Territory Feedback in Vault CRM:

  1. Navigate to Business Admin > Objects > Territory Settings.

  2. Set the align_territory_feedback_mode__v Territory Setting to 2.

    Admins can control the position of the tab in CRM using the Tab Visibility feature by adding TerritoryFeedback to the list of tabs in the TAB_NAV_DISPLAY Veeva Message.

  3. Navigate to Business Admin > Objects > VMobile Object Configurations.
  4. Enable the appropriate VMOCs for the territory_settings__v object. Veeva recommends cloning the existing VMOC for the veeva_settings__v object and changing the object to territory_settings__v.
  5. Grant the appropriate users access to the Territory Feedback tab.
  6. Ensure the formatted_name__v field is populated for all account__v records in Align. Admins can perform this task by mapping this field to the formatted_name__v field on the account__v object in CRM and running a full import.

Configuring Viewing Target Changes

To configure viewing target changes via the Assignment Changes widget, ensure users are part of an active MC Cycle with a populated clone_source__aln field. This field populates automatically via MC Cycle Cloning, or can be populated manually.

Defining the Default Feedback State

Admins can define a feedback state that all territory models in a project. Whenever the project is placed in the Feedback Review state, all territory models in the project are automatically placed in the defined default state. This saves the user from having to manually set the correct lifecycle state for each territory hierarchy.

To configure the default lifecycle state, populate the default_feedback_state__v field on the project. To use the out-of-the-box pre-configured approval workflow, select Feedback as the default feedback state.

Customers still must create the approval mapping for each field force model and specify lifefcycle states there, since this assigns lifecycle states to different users, who may require the assignment to participate in the feedback process.

If a Model Territory’s lifecycle state is manually changed, it does not automatically move into the default feedback state when the project is moved into the Feedback Review State.

Addresses in Integrated Territory Feedback

Align administrators can configure Integrated Territory Feedback to display the addresses of the accounts on the Account Card. This enables end-users to verify that the address information of the account is correct during the feedback process.

Configuring Addresses in Integrated Territory Feedback

To enable this feature:

  1. Navigate to the Align Settings.

  2. Add the appropriate fields on the address_aln object to the account_card_fields__v setting.

    For example: address__v.name__v,address__v.street_address_2_cda__v,address__v.city_cda__v

Use

A table with all associated addresses displays on the Account Card after the Product Metrics table. Each row of this table represents a different address__v record associated with the account and each column represents a field defined in the account_card_fields__v Align Setting.

Automated Feedback Handling

Administrators can configure Align to automatically handle approved challenges. This streamlines the Integrated Territory Feedback process by automatically applying approved challenges to the modeling project.

To enable Automated Feedback Handling:

  1. Navigate to Align Settings.
  2. Enable the automated_feedback_handling__v setting.

When a modeling project is moved to a state of Territory Feedback Complete, approved challenges automatically apply to the modeling project with the following behaviors:

  • Remove Account – All associated aln_account_territory_model__v records between the account and territory are end-dated to the planned publish date. An aln_account_exclusion_model__v record is created with the following values:

    Field Value
    account__v Account__v field on the aln_account_territory_model__v record
    aln_territory_model__v aln_territory_model__v field on the aln_account_territory_model__v record
    aln_project__v aln_project__v field on the aln_account_territory_model__v record
    start_date__v Planned_publish_date__v on the aln_project__v record
    end_date__v End_date__v field on the aln_territory_model__v record
    assignment_type__v account__v
    exclusion_reason__v feedback__v
    send_to_crm__v YES
  • Add Account – The account is added to the territory
  • Keep Account – The account remains in the terriory

  • Remove Target – the associated mc_cycle_plan_target__v record and all child records are deleted. An aln_account_exclusion_model__v record is created with the following values:

    Field Value
    account__v Account__v field on the mc_cycle_plan_target__v record
    aln_territory_model__v aln_territory_model__v field on the mc_cycle_plan_target__v record
    aln_project__v The current project
    start_date__v Planned_publish_date__v on the aln_project__v record
    end_date__v End_date__v field on the mc_cycle_plan__v record
    assignment_type__v target__v
    exclusion_reason__v feedback__v
    send_to_crm__v YES
  • Add Target – The target remains in the project
  • Edit Goals – If one of the target's cycle plan channel or cycle plan product records has a populated feedback_activity_goal__v field, the value stamps on the record's activity_goal_edit__v field or product_activity_goal_edit__v field, respectively.

Once Integrated Territory Feedback is complete, Pending challenges are ignored.

Editing the Challenge Reasons Picklist

Administrators can add, edit, and disable values of the Challenge Reasons picklist that displays to users when they submit a challenge using Integrated Territory Feedback. This enables more flexibility when configuring Integrated Territory Feedback, since the administrator can tailor this picklist based on the needs of the users submitting the feedback.

Administrators can also use this feature to disable the other__c free-text value in the picklist, ensuring compliance for field forces that do not support free-text notes.

For example, the Align administrator edits the challenge_reason__v picklist based on the needs of her users. She has received feedback that many users challenge target removals to their territories due to having a good rapport with the account, so she adds a new challenge reason, rapport__c, to the picklist. Her company also requires that users are not able to enter free-text, so she sets the status of the other__c value to Inactive.

To edit the values of the challenge_reason__v picklist:

  1. Navigate to the Configuration tab of the Vault Administration page.
  2. Navigate to the aln_account_territory_model__v object.
  3. Edit the challenge_reason__v picklist.
  4. Select Fields Using this Picklist.
  5. Select Edit.

From this page, administrators can perform the following tasks:

  • Add new picklist values by entering them in the text field after all existing values
  • Edit the status of individual picklist values