Tags: not added yet

Template Trackers in Project Deployment

You can update multiple projects by updating the template trackers during project deployment. After you update the configuration settings of the template tracker in the source instance, and deploy the project, the updated settings are inherited by the derived trackers in the target instance.

Updating the Application Configuration is not required when using template trackers for deployment. For more information on template tracker and how it can be made available as a template, see Template Tracker.

The derived trackers inherit the following configuration settings from the template tracker:

• Custom reference filter

• Field name

• Shared field enum

• Field Permissions

• Field Checkbox

• Field Enum

• Field Reference (Filter view too)

• Field Mandatory in status

• Field Formula

• Field Rules

• Field Content

• Field Layout

• State Transition Content

• State Transition Checkboxes

• State Transition Rule (Guard and Condition view too)

• State Transition Change Handler (Change filter view too)

• State Transition Entry (Condition view too)

•  State Transition Exit (Condition view too)

• Tracker Permissions

• Tracker Escalations (Escalation filter view too)

Note: The limitations for project deployment are also applicable to the template trackers in project deployment.

The following table shows the behavior of both the template and derived trackers while modifying their configuration settings in various scenarios:

Scenario	Details
Updating configuration settings in the template tracker.	After updating any of the above-mentioned configuration settings in the template tracker, the derived tracker inherits the updated settings. These settings are inherited after you deploy the project from the source to the target instance.
Updating configuration settings in the derived tracker.	If you update the configuration settings in the derived tracker and deploy the project, the derived tracker no longer inherits the changes from the template tracker. This results in the breakage of inheritance between the derived and the template tracker.
Modifying configuration settings based on permissions.	A user with write-only permissions for the template tracker can modify its configuration settings. The modified settings are then successfully inherited by the derived tracker upon using the deployment feature.
Deleting tracker configuration settings.	If you delete or modify any of the above-mentioned settings in the template tracker, the settings are inherited by the derived tracker after you deploy the project. If you delete or modify the configuration settings in the derived tracker, it does not inherit the changes from the template tracker. Note: Due to project template limitations, the tracker inheritance may not function properly if you modify the configuration settings of the derived trackers.