Skip to main content
R
RB_103565536-Contributor
6-Contributor
May 3, 2023
Solved

State based versioning scheme doesn't apply when manual set state done from approved to released

  • May 3, 2023
  • 2 replies
  • 3558 views

I have created a custom Versioning Scheme which should work with State Change from Approved -> Released ( i.e A.1 (Approved) will change to 1.1 (Released) State change either manually or when triggered in custom Workflow)

 

Has anyone encountered such issues, as this custom versioning is working for Object Revise action but not for Set State action / in Workflow State Change

 

Your support is appreciated. Thank you.

 

Lifecycle Transition:

RB_10356553_0-1683107730520.png 

RB_10356553_1-1683107815176.png

 

where highlighted series is my Custom versioning Series name

RB_10356553_2-1683107878280.png

 

RB_10356553_3-1683107910559.png

 

 

 

 

 

 

 

Best answer by joe_morton

You can create a workflow to trigger when the object reaches the Released state. Put the necessary additional steps in that workflow. That way, whether the objects is promoted or you use a set state, the secondary workflow will be triggered and the same steps will be performed for either case.

2 replies

StephenW
StephenW23-Emerald III
23-Emerald III
May 3, 2023

Which software are you using?

    R
    RB_103565536-ContributorAuthor
    6-Contributor
    May 3, 2023

    Windchill 12.0

    HelesicPetr
    HelesicPetr22-Sapphire II
    22-Sapphire II
    May 3, 2023

    Hello @RB_10356553 

     

    The versioning schema is change only during Revise action.

    Set state do not change it also Promotion do not change it.

    You can set autorevision during Promotions request that the object is autorevised and then the versioning schema is changed.

     

    PetrH

      R
      RB_103565536-ContributorAuthor
      6-Contributor
      May 4, 2023

      Thanks HelesicPetr.

      Terms & ConditionsAccessibility statement