Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Align/TerrFeedback/Config/Constraints.htm

## Territory Feedback Constraints

Align operational users can enable specific feedback constraints for Model Field Forces, which are both viewable and enforceable when end users use Territory Feedback. This helps end users comply with guidelines before they submit their feedback, and avoids dependency on managers to identify violations.

The following constraints can be enabled:

* The minimum total number of channel interactions the plan must contain
* The maximum percentage of the original HCP targets the end user can remove as targets
* The maximum number of HCO targets the plan can contain
* The exact number of HCP targets the plan must contain

**Who can use this feature?**

* Align Operational Users - Browser
* [Creating Constraints for Model Field Forces](#Creating)
* End Users - iPad
* [Using Territory Feedback Constraints](#Using)
* Users require an Align License

### Configuring Territory Feedback Constraints for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)
Align Operations Users](#)

To configure this feature:

1. Ensure the following features are configured:

   * [Configuring Align](../../Configuration/ConfiguringAlign.htm)
   * [Configuring Territory Feedback](Configuration.htm)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | aln\_feedback\_constraint\_model\_\_v | CRED | targeting\_\_v | * field\_force\_model\_\_v * minimum\_channel\_interactions\_\_v * max\_percent\_hcp\_target\_removals\_\_v * max\_number\_hco\_targets\_\_v * required\_number\_of\_hcp\_targets\_\_v * production\_record\_\_v | Edit |
   | aln\_feedback\_constraint\_\_v | CRED | targeting\_\_v | * field\_force\_model\_\_v * minimum\_channel\_interactions\_\_v * max\_percent\_hcp\_target\_removals\_\_v * max\_number\_hco\_targets\_\_v * required\_number\_of\_hcp\_targets\_\_v | Edit |
   | aln\_territory\_model\_\_v | CRE | All | capacity\_adjustment\_percentage\_\_v | Edit |
   | aln\_territory\_\_v | CRE | All | capacity\_adjustment\_percentage\_\_v | Edit |
6. Navigate to **Admin > Configuration > Objects > aln\_field\_force\_model\_\_v > Layouts**.
7. Add the **Model Feedback Constraints** Related Object section to the appropriate layouts.
8. Navigate to **Admin > Configuration > Objects > aln\_field\_force\_\_v > Layouts**.
9. Add the **Feedback Constraints** Related Object section to the appropriate layouts.
10. Navigate to **Admin > Configuration > Objects > aln\_territory\_model\_\_v > Layouts**.
11. Add the **capacity\_adjustment\_percentage\_\_v** field to the appropriate layouts.
12. Navigate to **Admin > Configuration > Objects > aln\_territory\_\_v > Layouts**.
13. Add the **capacity\_adjustment\_percentage\_\_v** field to the appropriate layouts.

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Managers](#)

This feature can be optionally configured to enable managers to bypass Constraints on behalf of their reps. To do so, ensure the Model Territory Lifecycle grants managers the ability to move a Model Territory from the Feedback lifecycle state to the Manager Review lifecycle state.

### Creating Constraints for a Model Field Force as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

Align operational users define which constraints apply to each field force, as well as define the parameters that end users' feedback must meet. Constraints are maintained in the model, and persist into future models through Publish and Import.

To define constraints for a Model Field Force:

1. Navigate to the appropriate **Model Field Force**.
2. Select **Create** in the Model Feedback Constraints related list.
3. Populate the appropriate fields:

   * minimum\_channel\_interactions\_\_v – The minimum total number of channel interactions the plan must contain
   * max\_percent\_hcp\_target\_removals\_\_v – The maximum percentage of the original HCP targets the end user can remove as targets
   * max\_number\_hco\_targets\_\_v – The maximum number of HCO targets the plan can contain
   * required\_number\_of\_hcp\_targets\_\_v – The exact number of HCP targets the plan must contain

   Only populated fields are evaluated as constraints. A constraint field left blank does not apply.
4. Select **Save**.

Only one Model Feedback Constraint record is supported for each Model Field Force. If multiple records exist, only the first record returned applies.

Align operational users can adjust constraints for a specific territory by editing the Model Territory’s capacity\_adjustment\_percentage\_\_v field with a value from 0% to 1000%. This field scales the constraints defined at the Model field Force level for that specific territory.

For example, if the Minimum Channel Interactions constraint is 1,000 and the Capacity Adjustment % for a territory is 50%, the plan for that territory must contain at least 500 interactions. When the field is blank, the Capacity Adjustment % is treated as 100%. The Capacity Adjustment % does not apply to the % of HCP target removals allowed constraint.

Constraints publish from Model Field Forces to production Field Forces, as well as import from production Field Forces to Model Field Forces, meaning Align operational users can define the constraints once and have those constraints carry over across cycles.

### Using Territory Feedback Constraints as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

End users can check their feedback against the constraints that apply to their territory before they submit their feedback to managers:

1. Navigate to the **Edit Alignments** screen.
2. Select the **All Actions** menu.

   ![](../../../../Resources/Images/Align/Configuration/Constraints.png)
3. Select **Validate Alignment**.

Constraint violations display as a red Error pill. Select this pill to view details about the violations.

![](../../../../Resources/Images/Align/Configuration/Constraints1.png)

This validation also occurs when end users submit their feedback, and if violations are found, end users are prompted to address them before resubmitting.

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Managers](#)

Constraints are not evaluated for any lifecycle state changes managers perform from Manager Feedback. This means that managers can submit an end user’s feedback on their behalf to make an exception to the constraints.

To submit feedback on behalf of an end user:

1. Navigate to [Manager Feedback](../ManagerTerrFeedback.htm).
2. Select the appropriate territory.
3. Move the Model Territory from the Feedback lifecycle state to the Manager Review lifecycle state. The feedback moves to Manager Review without constraints being evaluated.

### Related Topics

[Configuring Territory Feedback](Config/Configuration.htm)

[Using Territory Feedback in Vault CRM](TerrFeedback.htm)