Skip to main content
hamburger menu Created with Sketch.
PHP2Shell - PHP Vulnerability Announcement

Search the Knowledge Base

Special Veeva Align Hierarchical Assignment Rule Scenarios Involving Intermediaries and Child HCO Accounts

  • Updated

Audience:

Admin

Application:

Application (Product) Application Area Release Number Release Number
Align

Assignments and Rules

  17R1 - Current (24R3.2) Current (24R3.2)

 

Question:

This article demonstrates and clarifies two Hierarchical Assignment Rule Scenarios which are not trivial.

  1. Why may not an intermediary child and intermediary parent accounts be assigned to a particular territory?
  2. Why may Is Person = No Accounts be assigned to the territory in the event Is Person = Yes is in the Account Criteria of the Hierarchical rule?

Answer:

The example data set has the following Account Hierarchy:

HCP - HCO1 - HCO2 - HCO3, HCO3 is the top HCO, while HCO1 and HCO2 are referred to as intermediaries.

mceclip0.png

Each of the following scenarios describes one particular hierarchical assignment rule setup without any additional criteria:

Scenario #1

Assign Parent with Is Person = No Account Criteria and Intermediaries = Assign

mceclip4.png

Right-click and open the image in a new tab to view it.

In this case, the Assignment Preview (Rules Engine) will take all parent HCOs into considerating existing in the hierarchy and assign all of them to the territory. The reason for that is because Is Person = No behaves as a filter or Destination. This means the Assignment Preview will stop at the matching HCO account, however, it also includes all child HCOs along the way, which are in the hierarchy. It traverses through the hierarchy.

Scenario #2:

Assign Parent with Is Person = Yes Account Criteria

In this case, the Assignment Preview (Rules Engine) only assigns the first parent HCO in the territory and terminates, it does not check any parent accounts further in the hierarchy, as it has found a first match. Unlike Assign Child rules, Assign Parent does not traverse the hierarchy once a match is found.

Scenario #3:

Assign Child with Is Person = No Account Criteria 

In this case, the Assignment Preview (Rules Engine) only assigns the first child HCO in the territory and terminates, it does not check further in the hierarchy, as it has found a first match.

Scenario #4:

Assign Child with Is Person = Yes Account Criteria and Intermediaries = Assign

mceclip3.png

Right-click and open the image in a new tab to view it.

In this case, the Assignment Preview (Rules Engine) will take all child HCOs and HCPs into consideration existing in the hierarchy and assign all of them to the territory. The reason for that is because Is Person = Yes behaves as a filter or Destination. This means the Assignment Preview will stop at the matching HCP account, however, it also assigns all child HCOs along the way in the hierarchy - this occurs because Intermediaries is set to Assign.

Scenario #5:

Assign Child with Is Person = Yes Account Criteria and Intermediaries = Do not Assign

In this case, the Assignment Preview (Rules Engine) will take all child HCOs and HCPs into consideration existing in the hierarchy and assign all of them to the territory. The reason for that is because Is Person = Yes behaves as a filter or Destination. This means the Assignment Preview will stop at the matching HCP account, however, it will not include all child HCOs along the way in the hierarchy - this occurs because Intermediaries is set to Do not Assign.

Additional Resources:

Align Help Documentation:

Powered by Zendesk