To configure this feature:

1. Ensure Configuring Territory Management is complete.

2. Grant the following permissions:

   Object	Object Permissions	Object Types	Fields	Field Permissions
   assignment_rule__v	CRED	n/a	All fields	Edit
   assignment_rule_criterion__v	CRED	n/a	All fields	Edit

3. Add the Assignment Rules related list to the appropriate territory__v object page layouts.
4. Add the Criteria related list to the appropriate assignment_rule__v object page layouts.
5. Ensure the criteria_logic__v field is not added to any assignment_rule__v object page layouts.

To create an assignment rule:

1. Navigate to the Assignment Rules related list of the appropriate territory__v record.
2. Select New.

3. Populate the following fields:

   • Name
   • Territory – Automatically populates with the originating territory__v record
   • Cascade Down Hierarchy – The following values are available:
   • Yes – Applies the assignment rule to the selected territory and it's descendents
   • No – Only applies the assignment rule to the selected territory
   • Status – Must be Active
4. Navigate to the Criteria section.

5. Create the appropriate criteria. Each criterion consists of the following fields:

   • Field – Select the appropriate field. The following selections are available:
   • Any account__v field of the following types:
   • Account Object Type
   • Currency- Entered values are matched against the Vault's corporate currency
   • Date
   • Datetime
   • Number
   • Lookup
   • Picklist
   • Text
   • Yes/No
   • Address: Brick – Base the rule on the brick of address__v records
   • Address: Zip – Base the rule on the postal code of address__v records
   • Operator – The following operators are available, depending on the selected field type:

   • Matches territory's geographies – Only available if either Address: Brick or Address: Zip is selected as the field.

     This evaluates address__v records either marked as an account's primary address or records with an include_in_territory_assignment__v field of Yes. Criteria using this operator only consider account addresses where the address's country and postal code or brick match the values on the related geography_territory__v record. This operator ignores any addresses associated with accounts with an exclude_from_zip_to_terr_processing__v field of Yes.

   • Equals
   • Does not equal
   • Starts with
   • In
   • Not in
   • Contains
   • Does not contain
   • Less than
   • Less than or equals
   • Greater than
   • Greater than or equals
   • Includes
   • Excludes
   • Is null
   • Is not null
   • More than x days
   • Less than x days
   • Is in the range – This operator is only available when the selected field is a Date or Datetime field and enables territory managers to define a range of dates for the criterion
   • Value – Input depends on the selected Field and Operator values
6. Populate the Criteria Logic field with the appropriate matching logic. Parentheses, AND, and OR operators are supported when defining the criteria logic. Consecutive AND and OR operators must be separated with parentheses.
7. Select Save.

A maximum of 99 criteria are allowed per Assignment Rule.

When using the Assignment Rules UI in Vault CRM to edit or create Assignment Rules, users are prevented from inputting invalid criteria and logic. If an alternative method is used to edit or create Assignment Rules, for example, via data loading, invalid criteria and logic cause the rule to fail. If this happens, the initiating user is notified via email.

Inactive rules and criteria are not supported.

Select the Run Assignment Rules action on the appropriate territory to evaluate accounts against that territory and its descendants.

Rules can be run against any territory affected by at least one rule. A territory is affected by a rule in the following scenarios:

• A rule is assigned to the territory
• A rule is assigned to an ancestor of the territory, and Cascade Down Hierarchy is selected
• A rule is assigned to a descendant territory

Accounts must match all of a territory's defined assignment rules in order to be assigned to the territory. If an account matches, an account_territory__v record is created with the following properties:

• Account – The matching account
• Territory – The matching territory
• Manual – No
• Rule-based – Yes
• Status – Active

• External ID – Populates using the following format:

  account_id__v;territory_id__v

If a rule matches an assignment that has already been manually created, the rule__v field on the existing account_territory__v record updates to Yes.

If an account matches to multiple territories that are related, for example, if an account matches to both a territory and its parent territory, the account is assigned to the lowest matching territory. The user is notified via email when the assignment is complete or if the assignment failed due to errors.

When updating account-to-territory assignments, end user visibility to accounts processes asynchronously. This means a delay can be expected when updating assignments for multiple accounts.