Skip to main content
BF_1381190014-Alexandrite
14-Alexandrite
Sep 15, 2026 9:27 AM UTC
Solved

"template.templated" Attribute Value

I am using Windchill PDMLink Release 13.0 and Datecode with CPS 13.0.2.13 What dictates the value of template.templated which is often used to dictate the life cycle an object is set to in OOTB OIRs?
TDTAnswer
18-Opal
Sep 15, 2026 1:03 PM UTC

Hi ​@BF_13811900,

The template.templated attribute indicates whether the Change Notice object was created as a template or as an actual Change Notice.

When you create a Change Notice template, it is technically created as a Change Notice object, but the template.templated attribute is set to true. Therefore, Change Notice templates use the Basic lifecycle instead of the Change Notice lifecycle.

When you create an actual Change Notice using a Change Notice template, the template.templated` attribute is set to false.

The OOTB behavior is designed this way so that the Change Notice lifecycle is not applied to a Change Notice object when it is created as a template.

View in thread

4 replies

rhart16-Pearl
16-Pearl
Sep 15, 2026 10:48 AM UTC

If the object was created in the templates area then template.templated is 1 otherwise 0

Translate
    BF_1381190014-AlexandriteAuthor
    14-Alexandrite
    Sep 15, 2026 12:13 PM UTC

    Thanks but I’m still a bit unclear. The xml script seen below is used in the OIR for an OOTB change notice object. The way I interpret this is that the lifecycle given to a new change notice object is dependent upon the value template.templated is set to. Every change notice I create seems to get set to the ‘Change Notice Life Cycle’. I’m aware there is a “Templates” option available under certain container types in the GUI but I can’t see how it is possible to create the object in this area. How can a change notice object be created in such a way that it results in being set to the “Basic” life cycle?

     

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

    <!--  set the folder  -->

    <AttrValue id="folder.id" algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm">

    <Arg>/Default</Arg>

    </AttrValue>

    <!--  set the lifecycle  -->

    <AttrValue id="lifeCycle.id" algorithm="com.ptc.core.foundation.lifecycle.server.impl.LifeCycleTemplateAttributeAlgorithm">

    <!--  if (template.templated)  -->

    <Value algorithm="wt.rule.algorithm.BooleanBranch">

    <!--  test this value  -->

    <Attr id="template.templated"/>

    <!--  if true  -->

    <Arg>Basic</Arg>

    <!--  if false  -->

    <Arg>Change Notice Life Cycle</Arg>

    </Value>

    </AttrValue>

    Translate
    TDT18-OpalAnswer
    18-Opal
    Sep 15, 2026 1:03 PM UTC

    Hi ​@BF_13811900,

    The template.templated attribute indicates whether the Change Notice object was created as a template or as an actual Change Notice.

    When you create a Change Notice template, it is technically created as a Change Notice object, but the template.templated attribute is set to true. Therefore, Change Notice templates use the Basic lifecycle instead of the Change Notice lifecycle.

    When you create an actual Change Notice using a Change Notice template, the template.templated` attribute is set to false.

    The OOTB behavior is designed this way so that the Change Notice lifecycle is not applied to a Change Notice object when it is created as a template.

    Translate
    BF_1381190014-AlexandriteAuthor
    14-Alexandrite
    Sep 16, 2026 6:47 PM UTC

    Thank you very much! That clears things up.

    Translate
    Terms & ConditionsAccessibility statement