Versioning a Custom Action Template
If you want to modify a custom action template, you can create a new version of the existing template and modify the new version as required. When you create a new version of a custom action template, CentraSite creates an identical copy of the existing template; you can then modify the copy as required. (The new version of the custom action template gets its own copy of the Java Zip file.)
Note that CentraSite does not automatically apply the new custom action template to policies that use existing versions of the custom action. Policies that use existing versions of the action continue to use the versions that they have. If you want to apply the new version of the action to these policies, you must edit the policies (or create new versions of them) and replace the old version of the action with the newer one.
Similarly, modifying the parameter definitions in a new version of an action template does not affect the parameter definitions in any of the existing policies that use the action. Parameter definitions are specific to a version of the template.
When you create a new version of a custom action, be aware that:
You can only create a new version from the
latest version of an action. For example, if an action already has versions 1.0, 2.0, and 3.0,
CentraSite only allows you to create a new version of the action from version 3.0.
The new version of the action is identical to the version from which you created it (except for the system-assigned version identifier, which is always incremented by one).
CentraSite automatically establishes a relationship between the new version of the policy action and the previous version.
CentraSite uses this relationship to identify versioned actions.
You can only create new versions of
custom actions that exist on your instance of
CentraSite (that is, actions that you have added to
CentraSite). You cannot create new versions of the predefined actions that are installed with
CentraSite.
Tip:
To make the new version of the custom action distinguishable from earlier versions, consider appending the version number to the name of the custom action.