Multiple Promotion states

[BenLoosli]

We have added a new lifecycle state which is optional for a promotion request. I have run the lifecycle upgrade utility and the parts are all showing they have the new state available. I have modified the ACLs to allow the members access to the new state. I did this first on my Windchill 12.0.2.10 test system then made the same changes to the production 11.1 M020 CPS20 system. The WIndchill 12 system is an upgrade from the Windchill 11.1 system, so it has the same base data, just a few weeks out-of-date. 

With the 12.0 system, when I do a New Promotion Request, I get a window at the top of the screen asking me to set the promotion request state.

On the Windchill 11.1 system, I only get the old Released state, no option.

I have compared the Lifecycle states and the ACLs and they are identical on both systems.

Is there something that needs done so the Windchill 11.1 system will act the same as the Windchill 12 system?

[avillanueva]

You said you checked lifecycles but did you define the exact settings for the promote line?

[BenLoosli]

Yes, parts that can be promoted are in either the Design or the Pre-Release state.

I have also restarted Windchill.

[avillanueva]

How about the preferences at the site level for Promotion Process? Are they the same?

[BenLoosli]

Both are the same setting. The Windchill 12 system is an upgrade from the data of the Windchill 11.1 system and I have not touched any settings at the site level.

[jbailey]

Any context level ACL's not being taken into account?

[BenLoosli]

I don't think so. As I said the Windchill 12 system is an upgrade from the Windchill 11.1 system, so all context level ACL's would have been transferred over. I do not use context ACl's anyway, I try to leave all of that at the Org level.

[jbailey]

What state are you promoting from? is it the same in both systems? 

Share the screenshot of the lifecycle on both WC 11 and WC 12 with the promoted from state selected in the lifecycle editor

[HelesicPetr]

Hi @BenLoosli 

I would check if an object use the latest lifecycle iteration. The object what you are trying to promote.

Usually it is thing that is very often forgotten to do.

Then check if the object use really your lifecycle template. Sometimes it is rewritten by lower level lifecycle template. For example from Product level.

PetrH 

[HelesicPetr]

@BenLoosli 

Also I would advice to double check the lifecycle template configuration for all states .

Usually it is misconfiguration.

PetrH

[BenLoosli]

All of the Parts and EPMdocuments had their lifecycles updated to have the added state. The part in question shows that the new state is listed in the list of states. I only use 1 Lifecycle for all of the parts, set at the org level.

There should not be any Lifecycles or ACL's at the Product level, I do all of that work at the Org level to keep it simple.

[HelesicPetr]

@BenLoosli 

Do you use multiple MethodServers? Sometimes the change is done on the one methodserver and it takes a while then the change is refreshed on the second method server. 

I could see the differences on many parts of windchill especially with ACL rules but I could see it with TypeAndAttribute management and layouts changes. Lifecycle changes and so on. 

Admin does a change on configuration but the configuration change was not seen on the second instance of the methodserver .

And sometimes it was randomly worked/not worked. 

Could it be your case?

PetrH 

[BenLoosli]

Shutdown and restarted Windchill yesterday. That should resolve any secondary MS issues. I have 3 MS and 1 BMS running.

Could it be Windchill cache files? I have not cleared them in a while.

[HelesicPetr]

Hi @BenLoosli 

Wch cache shouldn't case that issue with LC but who knows :D.

PetrH

[Dobi]

And you reassigned lifecycles for the parts you're trying to promote?

[BenLoosli]

I created the new lifecycle state and then ran the reassign Lifecycle utility. The Info page for the part I am trying to promote shows the new state in the list of states. It also shows the Lifecycle name that we use.

[HelesicPetr]

Hi @BenLoosli 

Really check the configuration and correct level of the lc template. 

PetrH

[HelesicPetr]

PS: Test in on just one part and reassign theLC from detail page to the latest lc iteration

I tested it on the WCH 11.1 M020 CPS14 without any issues.

PetrH

[BenLoosli]

I posted my screen shot of the Lifecycles earlier in this thread. Both Design and Pre-Release state show Verification Required as an state for Promote.

I also showed the Promotion Request screen for 11.1, showing on Target state option, and 12.o showing the Target State option drop-down.

I have tested it on the same part in both systems. The 12 system will take multiple promotion states as an option.

[jbailey]

I just wasn't sure which one was wc 11 and which one was wc 12.

[BenLoosli]

The lifecycle screen shots are Windchill 11.1, but the Windchill 12 look identical.

I captured in a Word document all of the Windchill 12 lifecycle state views and compared them to the WIndchill 11.1 views and all states are identical as to what is allowed.

I did the same with the ACL's for every state, also identical between the 11.1 and 12.0 systems.

[HelesicPetr]

Hi @BenLoosli 

If you try to create promotion request as a administrator, does it work? I mean you can see multiple state selection

PetrH

[BenLoosli]

The promotion request selection does not work for a normal user or the wcadmin account. I am using the wcadmin account for my testing.

[HelesicPetr · Accepted solution]

Ok, go to the detail page, 

add a lifecycle history tab and check if the object has really the latest LC iteration.

Check if the LC does not has higher iteration.

PS> it is definitely small miss configuration that you can not see. 

PetrH

[BenLoosli]

That was it, somehow, I missed setting the promotion options when I did the mass update. I will rerun the lifecycle update utility.

I did update the lifecycle to the latest on my test part and it is now working.

Thanks to everyone for helping.

It is the little things that get lost and take multiple ideas to find.

[BenLoosli]

I thought saving a file would pick up the latest lifecycle iteration, but that doesn't seem to be the case. I have files saved this morning that do not have the multiple promotion states.

[Marco_Tosin]

The "updated" lifecycle is only applied when a code is revised or you have to use the reassign lifecycle action to do it manually.

I have some reports that I use just to check what lifecycle an object is using, and I use it, usually, when a user tells me they can't find a lifecycle state.

When you change them multiple times, and years apart, it becomes difficult to remember.