Overview:
An End-user is unable to change the Lifecycle state to Manager Review or Territory Feedback Complete of a Model Territory of a Project in Veeva Align. The next Lifecycle state: Manager Review or Territory Feedback Complete are not available at all just the current Lifecycle State.
Root Cause:
The issue is caused by misconfiguration located in the following areas in Veeva Align:
- Missing Object / Field Level Permissions for the end-user
- Incorrect Model Territory Lifecycle State Configuration
- Inappropriate Sharing Rule Configuration
Solution:
The standard permission requirements are as follows:
The end-user needs Read access to most tabs in Align in the Admin section, and Edit access on the Object Lifecycles, Object Workflows, Objects, Object Messages, and Object Web Actions sections.
In the Objects tab, the end-user needs Create, Read, Update object permission on the Model Territory object.
The end-user needs access to most tabs in the Tabs section. Generally, all tabs are given access the user.
The Users in the Align instance need edit access to the relevant roles of the Model Territory Lifecycle State. This is a global permission section.
This page can be accessed by navigating to Business Admin --> Object Lifecycles --> Territory Model Lifecycle:
The Model Territory Lifecycle State and Model Territory Sharing Rule Configuration requirements are as follows:
The Approval Process configuration is for use with the Territory Feedback functionality.
Example:
When accessing the Future Territory Alignments page in Salesforce, Managers and Sales Reps typically do not have direct access to the Align instance and are not changing these values from within the Align Vault.
To have the change status actions visible in the Align Vault, the end-user needs proper access to the lifecycle actions. The configuration depends on the Sharing Model of the Align instance.
In the event, Sharing Rules are not in use on the Model Territory object:
Without Sharing Rules enabled on the Model Territory object, the lifecycle uses the default State Behavior atomic security for each state since the particular user is not assigned to any role on the object record. End-users are not assigned to any role if there are no sharing rules.
The role assignment is covered in the following Vault Help documentation in Detail: About Dynamic Access Control for Objects.
Example:
In the event, the Feedback state has the default state behavior set to Hide. The end-users are not able to change the lifecycle state of a model territory record from Feedback to Manager Review or from Manager Review to Territory Feedback complete.
In order to make the lifecycle change actions available on the territory model record, and if Sharing Rules are not intended to be used on the Model Territory object, then the State Behaviour needs to be changed from Hide to Execute for the appropriate Action Labels.
In the event, Sharing Rules are in use on the Model Territory object:
End-users are dynamically assigned to roles using object sharing rules if they are present. The roles are configured in each Sharing Rule. The end-user needs to be placed into the group the sharing rule is associated with and also the questionable model territory record has to be meet the sharing rule criteria, so that it can be visible for the end-user. There are several pieces of configuration possible.
The following example is presented with another out-of-the-box role:
An out-of-the-box role Editor is assigned to the end-user. By default there is no Editor Role located in the Atomic Security Actions page. By clicking on the Edit button, located at the far right of the Atomic Security Actions section, a new Role can be added using the Role Override button.
The actions have to be adjusted accordingly to the appropriate action labels, preferably selecting Execute in this case, in the Editor/Change State to Manager Review matrix. The View Action is also needed for the View Action Label.
Next, in the Configuration --> Objects --> Model Territory Object settings, the Sharing Rules are enabled.
The sharing rule is setup as shown:
With this configuration, the end-user located in this group, is able to change the lifecycle state of the Model Territory to Manager Review from Feedback.
Another common scenario is the ability to move the Model Territory Lifecycle state from Manager Review to Territory Feedback Complete. This scenario requires the following Lifecycle State configuration for the Manager Review State. The Group / Sharing Rule configuration / Role / Action requirements apply the same way.
- It is recommended to test the configuration in an Align Vault sandbox.
- There are several pieces of configuration possible.
- In the sharing rule example, It is not required to assign the Editor role in the Approval Process of the Modeling Field Force.
- Vault Owners can make any changes.
- End users responsible for lifecycle changes of projects are commonly referred as Market or Local Business Admins.
- The presented data is not customer-specific.
Related Documentation:
Align Help Documentation:
Vault Help Documentation: Vault Help
Send us your feedback: We are always looking for feedback to help improve our Knowledge Base! Please let us know if this article is helpful or provide feedback on how we can improve your experience by clicking here.