Promotion Request Layout

[PetrP]

Привет!

nowadays in WCH 10.2 when a new promotion request is created at step 2 "Select Promotion Objects" have to:

• Click into field "Target Promotion State"
• Select desired "Target Promotion State"
• Select object for promotion
• Click "Set Object for Promotion"

Setting object is redundant. Also unable to select different targets for each object (all objects must have the same target = useless).

I suggest to unify layout with change notice (add also icon for multi select target and allow to manage it faster). Then just need to:

• Click into field "Target Promotion State"
• Select desired "Target Promotion State"

[JeffZemsky]

We have discussed about updating the layout in the future.  A few notes though -

1. Not every object on a Promotion Request needs to have a state change
2. Since only one target state is supported we don't auto set for Promote in the case were multiple object types might be on a promotion request with different target states.
3. If the objects do have the same target state you can have it automatically select the Initially selected or Initially Selected and Collected for Promote without additional actions using the following property:  wt.maturity.autoPromoteType
   1. Additional information can be found here: https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS80255&art_lang=en&posno=7&q=promotion%20r...
4. A simpler process flow with supporting multiple target states can be accomplished using Change Notice (without Change Request) and selectable Target states

[jfrankovich]

Jeff,

Can you clarify point #4? How does one have selectable and multiple target states in a single Change Notice?

Thanks

[JeffZemsky]

John Frankovich‌ - this support was added in Windchill 10.1 M010.  It enables one to select the target per Resulting Object (or multiselect).  This makes it easier to do things like Release some items and Obsolete some items on the Change Task.

You can find help here:

https://support.ptc.com/cs/help/windchill_hc/wc110_hc/index.jspx?id=WCCG_BusLogicCust_ChangeMgmt_Tra...

[jfrankovich]

Thanks Jeff.

Looks like it could be pretty powerful functionality for defining multiple transition possibilities for each starting lifecycle state. Would have been nice if simple direct state targeting (like "set state" as opposed to selecting a transition type) was just OOTB functionality, but clearly we can make this method work.