Up-issuing a Definition should automatically up-issue any Rule and/or Policy which calls it

ITNCM Compliance manager has a feature whereby once you "activate" a Policy, Rule, or Definition - the version number of that Policy, Rule or Definition is automatically incremented whenever it is edited. It is normal to have each Policy call one or more of Rules, which in turn may call one or more Definitions. The way ITNCM works at present, if a Definition is edited (and hence it's version gets automatically incremented) this has no effect on the version number of the Rule which calls it and the Policy which calls the Rule. It is not obvious by just looking at the Policy that anything has changed. If (as we are) you are developing Policies etc. in a lab environment, for export to a number of production instances of ITNCM, this makes it extremely difficult to maintain version control. The policyExport utility permits a particular version of a Policy (and all Rules and Definitions it calls) to be exported - but at present, if (say) a Definition is updated, there is no indication that the Policy has changed in any way. If we want to convey this by changing the Rule and Policy version we have to do it manually- which is time consuming and prone to error.
This enhancement request is for the incrementing of the version number of any Definition or Rule to also automatically increment the version number of any Rule or Policy which calls it. (This should also be extended to extractions etc.)