Skip to main content
U
uvex_windchill8-Gravel
8-Gravel
October 21, 2022
Solved

OIR are not chooseable in LifeCycleStatus

  • October 21, 2022
  • 4 replies
  • 1471 views

I dont know if i am right, but i wanted to get new chooseable Lifecycle Statuses. So i created new OIR, but it doesnt work. 

Best answer by HelesicPetr

Hi @uvex_windchill 

You need to use enumcustomize aplication from windchill shell

 

Article cs42231 describes how to do so.

 

PetrH

4 replies

HelesicPetr
HelesicPetr22-Sapphire II
22-Sapphire II
October 21, 2022

Hi @uvex_windchill 

 

What do you need?

Add own Lifecycle state names because what you want is not in the list of states?

or New lifecycle template with different first Lifecycle state for a new object?

 

PetrH

 

    U
    uvex_windchill8-GravelAuthor
    8-Gravel
    October 21, 2022

    thank you for your fast answer. 

     

    yes, i want to add own lifecycle state names, because we want to make more customization.

    where can i do that?

    HelesicPetr
    HelesicPetr22-Sapphire IIAnswer
    22-Sapphire II
    October 21, 2022

    Hi @uvex_windchill 

    You need to use enumcustomize aplication from windchill shell

     

    Article cs42231 describes how to do so.

     

    PetrH

      M
      MikeLockwood22-Sapphire I
      22-Sapphire I
      October 21, 2022

      Terminology super important on these things. This might clarify a bit.

      - You are interested in assigning a specific lifecycle template to a certain object type (e.g. WTPart - possibly a sub type of WTPart).

      - You have the lifecycle template already created and checked in and enabled.

      - The OIR has to list the object type near the top like this:

                       <AttributeValues objType="wt.change2.WTPart">

      - The OIR then has to specify the lifecycle template, some this like this:

                        <!-- set the lifecycle -->

                        ....

                        <Arg>WTPart Life Cycle</Arg>

       

      Important Note: As supplied all these are at Site Level (OIRs, Lifecycle templates, etc.).  May admin's leave all at Site alone and make all new / changes at Org level.  This is generally best practice.  If this is done, one should create both the lifecycle template and OIR at Org level (possibly via Save As).  Also, the lifecycle template and OIR should have different names from those at Site level to avoid confusion.

      Terms & ConditionsAccessibility statement