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 derived trackers in the target instance inherit the updated settings.
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 Tracker Inheritance.
The derived trackers inherit the following configuration settings from the template tracker:
• Customer reference filter
• Field name
• Shared field enum
• Field permission
• Field checkbox
• Field enum
• Field reference with filter view
• Field mandatory in status
• Field formula
• Field rules
• Field content
• Field layout
• State transition content
• State transition checkboxes
• State transition rule and guard and condition view
• State transition change handler and change filter view
• State transition entry condition view
• State transition exit and condition view
• Tracker permissions
 |
The limitations for project deployment are also applicable to the template trackers in project deployment.
|
The following table provides details about the behavior of 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 preceding 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 when using the deployment feature.
|
||
|
Deleting tracker configuration settings
|
• If you delete or modify any of the preceding configuration 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.
|