Defining Illegal Child Tag Statuses

AVEVA Change Manager must guarantee Tag hierarchy consistency, which means, you cannot, for example, void the current Tag if its child Tag has not been voided yet.

To specify the list of statuses that a child Tag may have when the current Tag's status is being changed, you must access the \TIM.WebSite\Dictionary\TIM.Dictionary.Pages.xml path and refer to the following section:

...
<!--Specify a semicolon separated list of child Tag statuses that are allowed when the current Tag's status is changed-->
<!--If the child Tag's status is not in the list associated with the value the current Tag's status is being set to, the current Tag's status modification will be rejected with an appropriate error message raised-->
<!--<allowedChildTagStatusesForCurrentTagStatusToBeChangedTo>
<Void>Void;Removed;...</Void>
<Removed>Removed;Void;...</Removed>
...
</allowedChildTagStatusesForCurrentTagStatusToBeChangedTo>-->
<!--Be aware that the status value must be from the list of supported statuses-->
<!-- Active -->
<!-- On Hold --><!-- Be aware that the space in the middle must be omitted in the XML tag but not in its value, e.g. <OnHold>Active;On Hold</OnHold> -->
<!-- Removed -->
<!-- Void -->
<!-- Reserved -->
<!-- Future -->
<!-- Installed -->
<allowedChildTagStatusesForCurrentTagStatusToBeChangedTo>
<Void>Void</Void>
</allowedChildTagStatusesForCurrentTagStatusToBeChangedTo>
...

Notes:
- You must switch on the child Tag status validation feature, which is turned off by default.
- This feature is available only in AVEVA Change Manager (not in AVEVA NET Gatekeeper).
- If the section <allowedChildTagStatusesForCurrentTagStatusToBeChangedTo/> is not empty (which means, the child Tag status validation feature is turned on), the Parent Tag status validation feature is turned on automatically (which means, it is not possible to re-activate the current Tag if its parent Tag is not active).