Greetings All,
I've been trying to set up a promotion process to revise an object so that we'd have a formalized, documented reason for the revision. This has been working however I noticed that when the promotion objects are revised, the old versions no longer maintain they're original state (released - no modify rights) but take on the new state (rework required - can be modified) that the new version moves to. This has become an issue because users have been able to inadvertently check out a previous revision as it is left in the modifiable state after completion of the promotion request. This is not what I want. As a note, we do have the 'allow checkout of non-latest iterations' set to 'Do not allow...' Not sure why that is not stopping the checkout of previous iterations.
In contrast, if we simply do a right-click>revise from admin - the old state (released) is maintained on the old version and the new version is in the new state (rework required). This is what I want.
Any help would be greatly appreciated.
Marc
Here is the default code for revisioning in the OOTB 10.2:
wt.maturity.PromotionNotice pn = (wt.maturity.PromotionNotice)primaryBusinessObject;
try
{
java.util.Locale locale = wt.session.SessionHelper.getLocale();
com.ptc.core.ui.validation.UIValidationResultSet set= com.ptc.windchill.enterprise.maturity.PromotionNoticeWorkflowHelper.revisePromotables(pn, pn.getCreator(), locale);
reviseValidationMsg= com.ptc.windchill.enterprise.maturity.validators.PromotionTargetsReviseValidator.getReviseResultSetMessage(set, locale);
if (!reviseValidationMsg.isEmpty() )
result="Partial";
else
result="Full";
}
catch( Exception wte )
{
wte.printStackTrace();
}