cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Possibility to add several versions of same object in a Promotion Request

0 Kudos

Possibility to add several versions of same object in a Promotion Request

We want to have the possibility to add several versions of the same object in a Promotion Request. 

 

In our case we want to set several versions of the same object to Expired at the same time. So if version C gets Approved we want to be able to set both B & A to Expired in the same promotion request.

3 Comments
BenLoosli
Sapphire II

The promotion request itself would be for a single version? C in your example.

Why would version A not have been set to expired when version B was promoted?

What determines which prior versions get set to expired?

Do all prior versions get set to expired automatically? If so, is this request just a 'patch' to make up for prior releases that did not set the prior versions to expired?

Setting the 1 prior version to a different state should be doable within the workflow and lifecycles.

TomU
Emerald II

@pmöllberg wrote:

In our case we want to set several versions of the same object to Expired at the same time. So if version C gets Approved we want to be able to set both B & A to Expired in the same promotion request.


Promotion requests are designed to only work with one target state.  It's not currently possible to have the target state for some objects set to 'Released' while the target state for others set to 'Obsolete' (or 'Expired').  You may be able to develop custom code to do this behind the scenes, but the promotion request screens are only going to work with one target state.  You may be able to switch to using 'full blown' change management (problem reports, change requests, change notices, change tasks, etc.).  I believe that has a way to deal with the old versions of objects when the new ones are promoted.

bmr
Peridot
Peridot

This is kind of a duplicated idea:

Windchill Promotion Requests - Multiple Enhancements 

 

@JeffZemsky  wrote last year:


We don't have plans to support multiple states - a Change  Notice should be used for this case (and can be much simpler than a Promotion Request here)



You are able to add multiple version to a Change Notice and then you can define two different transition rules (target states)

Screenshot 2021-01-20 at 21.41.32.png

 

 

 

 

 

 

 

 

 

 

And if you have setup the Change Notice correctly, it is almost as easy as a promotion request. Just with more options. You can use different templates, Tasks for 2 / 4 eyes, with or without Change Audit, etc.