You can use Dynamic Hierarchy policies to automatically generate external Business Roles and Locations based on the value of a specified person attribute, such as the name of their department. After the policy is created, the Dynamic Hierarchy engine will add any account with the matching attribute values to the AccountExternalOrgRoleOrgZone table for use by the role and location compiler job. As seen below in the policy settings section of a dynamic hierarchy policy, you can select up to 3 attributes to build your external role tree and your external location tree. Each level represents a Parent/Child level in the tree as described below:
External Role Level 1 – Specify the attribute that is to be used to generate the parent external role.
External Location Level 1 – Specify the attribute that is to be used to generate the parent external location.
External Role Level 2 – If nesting roles, specify the attribute that is to be used to generate the first child external role.
External Location Level 2 – If nesting locations, specify the attribute that is to be used to generate the first location external role.
External Role Level 3 – If nesting roles, specify the attribute that is to be used to generate the second child external role.
External Location Level 3 – If nesting locations, specify the attribute that is to be used to generate the second location external role.
The other sections of the dynamic hierarchy policy configuration follow the same format as dynamic hierarchy policies for management roles or groups. The EmpowerID system uses the Dynamic Hierarchy Generation job to create the external roles and locations, and then uses the Dynamic Hierarchy Membership job to populate the AccountExternalOrgroleOrgzone table.
Use Dynamic Hierarchy Policies to Create External Roles and Locations