Note: Training Change Request is available in Veeva Training Vaults only. The Training Change Request object is highly configurable to meet your organization’s requirements. This article outlines Veeva’s best-practice recommendations for managing TCRs.
## About the Training Change Request Lifecycle & Workflow {#tcr-lifecycle-workflow}
The *Training Change Request* object lifecycle is delivered to all Training Vaults with standard lifecycle states, and the Veeva-recommended workflow configuration is a basic use case for moving TCRs and their related change items to completion.
Your organization may require that this process is simpler or more complex than what is described here. As such, when updating the *Training Change Request* object lifecycle and any related workflows, Vault Admins should minimally ensure that:
* *Training Change Request* records enter the *Pending System Implementation* state. The *VT: Process Training Change Requests* job searches for relevant TCR records in this state to locate proposed matrix updates, then it updates the matrix and transitions the TCR to *Complete* upon the TCR's indicated *Training Change Implementation Date*.
* When a TCR is in the *Pending System Implementation* state, its related *Matrix Change Items* have an *Implementation Status* of "Ready to Implement".
Training Change Request additionally includes a standard _VT: Manager Homepage Initiate TCR_ [workflow][9] for routing requests originating from the My Team page.
### Sample Configuration {#sample-config}
The Veeva-recommended lifecycle and workflow configuration follows a basic Training Change Request use case in which:
* In the TCR's *Initiated* state, requestors initiate a workflow via the "Send to Training Admin" user action. This sends the TCR to a Training Admin for review. Once initiated, the TCR transitions to the *In Training Admin Review* state.
* While *In Training Admin Review*, Training Admins review the request. In the event updates are required, they can remove or update *Matrix Change Items* directly.
* Once all change items are ready, Training Admins render a single "Ready for Implementation" verdict, and the record transitions to the *Pending System Implementation* state. Vault references this state to apply the proposed matrix changes and transition the TCR to the *Complete* state.
The workflow and lifecycle is additionally configured such that:
* The custom workflow is labeled "TCR: Send to Training Administrator".
* The **Start** step includes a participant control to use the Training Administrator role as a participant. To support this:
* The *Training Change Request* lifecycle includes the Training Administrator role.
* The *Training Change Request* object is configured with a custom sharing rule, where the Training Administrator role is mapped to a Training Administrators group.
* The **Task** step's settings assign the task to the Training Administrator role. The task is available to all users in this participant group.
### TCR Workflow for the My Team Page {#tcr-my-team-wf}
Training Change Request functionality within the My Team page is delivered with a standard *VT: Manager Homepage Initiate TCR* placeholder workflow that your organization can update with custom configurations.
When this workflow does not include any custom configurations:
* Vault creates a *Training Change Request* in the *Initiated* state, and related *Matrix Change Items* with a "Ready to Implement" *Implementation Status*.
* The change request record remains in the *Initiated* state until the Manager or other user starts a workflow. When your organization follows the recommended configuration, this is the "TCR: Send to Training Administrator" workflow used for the TCR feature generally.
## Limitations {#limitations}
Training Change Request is an evolving feature which supports many, but not all, requests to update your organization's Training Matrix.
See additional details on the types of matrix changes users can currently request with this feature, including via the My Team page.
Additionally, this feature can function differently for users requesting new matrix records. See [additional details][8] on how your Vault's security configuration can impact user experience.
## Related Permissions {#related-permissions}
To work with Training Change Requests generally, users must be assigned a permission set with the below permissions to submit a change request of any kind.
These basic permissions can be expanded such that:
* Users are granted [additional capability][8] when requesting to create a new matrix record.
* Users can create _Matrix Change Items_ directly [from a TRIA record][7].
| Permission Label | Permission |
|---|---|
| Objects: Training Change Request | Read, Create, Edit |
| Objects: Training Change Request: