Designating a Primary Territory

To help resolve integration conflicts that may occur when a user is assigned to multiple territories, admins can designate a territory as being a roster member’s primary territory. Primary territories are prioritized when assigning functional profiles to users if the user is assigned to multiple territories with different functional profiles.

For example, Sarah Jones is assigned to the North Jersey Cardio territory. One of her colleagues, assigned to South Jersey Cardio, is going on a leave of absence, so Sarah is assigned South Jersey Cardio as a non-primary territory. These two territories in Align are associated with different functional profiles. When the next push to CRM occurs, the functional profile associated with North Jersey Cardio is assigned to her, since that is Sarah’s primary territory.

Configuring

To configure this feature:

  1. Grant the Align Integation User the following permissions:

    Object

    Object Permissions

    Fields

    Field Permissions

    align_settings__aln

    Create, Delete

    primary_assignment_handling__aln

    Edit

    roster_member_territory__aln

    Create, Delete

    primary__aln

    Edit

    roster_member_territory_model__aln

    Create, Delete

    primary__aln

    Edit

    roster_member_territory__aln

    Create, Delete

    override_primary_validation__aln

    Edit

    roster_member_territory_model__aln

    Create, Delete

    override_primary_validation__aln

    Edit

  2. Grant Align end users the following permissions:

    Object

    Object Permission

    Fields

    Field Permissions

    align_settings__aln

    Read

    primary_assignment_handling__aln

    Edit

    roster_member_territory__aln

    Edit

    primary__aln

    Edit

    roster_member_territory_model__aln

    Edit

    primary__aln

    Edit

  3. Add the primary__aln field to the following object page layouts:

    • roster_member__territory__aln
    • model_roster_member_territory__aln

  4. Add the primary__aln field to the Roster Member Territory related list on the following object page layouts:

    • roster_member__aln
    • territory__aln
    • model_territory__aln
  5. Add the primary_assignment_handling__aln field to the align_setting__aln object page layout.

  6. Select one or both of the following values for the primary_assignment_handling__aln Align Global Setting:

    • validate_roster_members__aln – Prevents users from assigning more than one primary territory to a roster member
    • validate_territories__aln – Prevents users from assigning roster members to the same primary territory

    This setting can only be used in the Global Settings record. It cannot be used in field-force specific settings, since end users can be assigned to mutliple territories in different Field Forces.

Designating a Primary Territory for a Roster Member

To designate a territory as being the primary territory of a roster member, select Yes for the primary__aln field for the appropriate roster_member_territory__aln or model_roster_member_territory__aln records.

When the user attempts to create or save a roster_member__territory__aln or model_roster_member_territory__aln record designated as a primary territory, the following validation occurs based on the selected values for the primary_assignment_handling__aln Align Global Setting:

  • If validate_roster_members__aln is selected, all other roster_member_territory__aln or model_roster_member_territory__aln records associated with the roster member are checked. If any other record is already designated as being a primary territory within the same date range, the user is prevented from saving the record.

  • If validate_territories__aln is selected, all other roster_member_territory__aln or model_roster_member_territory__aln records associated with the territory are checked. If any other record is already designated as another roster member’s primary territory, the user is prevented from saving the record.

  • If both validate_roster_members__aln and validate_territories__aln are selected, both steps of validation occur

Validation in model records does not apply across models, only within the same model. For example, a roster member can be primarily assigned two different territories for the same date range in different projects.

Admins can override the validation specified in the primary_assignment_handling__aln Align Global Setting by selecting Yes for the override_primary_validation__aln field on the appropriate roster_member_territory__aln or model_roster_member_territory__aln records. This field can only be populated via data loading and automatically resets to No as part of the dataload process to prevent future changes that override validation from occuring in the user interface.

Role and Profile Conflict Resolution

If a user is assigned to multiple territories, with one territory designated as a primary territory, and an integration conflict occurs regarding the users role or profile, a message displays in the header of the corresponding roster_member__aln or roster_member_model__aln record informing the admin that the user’s primary assignment is being used to resolve the conflict.

Admins can override the profile and role provided from the primary territory for an individual roster member.