Skip to main content
P
pwilliams-313-Aquamarine
13-Aquamarine
July 23, 2013
Question

Removal of Change Notice "Complexity"

  • July 23, 2013
  • 11 replies
  • 11632 views
Hi All,
I have soft typed the CN to an ECN. In the workflow I removed the Full Track branch and therefore do not need the "theComplexity" attribute on my ECN. However this attribute is required by Windchill to create my ECN. So I went down the road of setting the Visibility to "Hidden" or "Read Only" both of which didn't give me the desired results. I then went the OIR route and found that "theComplexity" is not defined in the LogicalAttributes.xml file for ChangeOrder2 which means I can't add it as a visible attribute to an OIR in the RuleConfigurableTypeAttribute.properties file.

So how do I hide/remove "theComplexity" attribute on a CN from the user's perspective but still have it populated for Windchill?

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image001.jpg@01CE87A4.AFFCCE10]

11 replies

M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
July 23, 2013
We do this as well - don't use the concept at all but have to satisfy the code that looks for it.

You have to:

- Add Complexity to what the OIR can address in LogicalAttributes.xml

- Fill in a value via the OIR

- Hide it via Type Manager on create / edit / info

[cid:image002.png@01CE878E.43B0F760]

P
pwilliams-313-AquamarineAuthor
13-Aquamarine
July 23, 2013
Awesome Mike, this is exactly what I was looking for. What did you put into LogicalAttributes.xml and RuleConfigurableTypeAttribute.properties?

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image001.jpg@01CE87A7.EE661A00]
M
22-Sapphire I
MikeLockwood22-Sapphire I
22-Sapphire I
July 23, 2013
Attached

P
pwilliams-313-AquamarineAuthor
13-Aquamarine
July 23, 2013


Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image003.jpg@01CE87AD.6FFF7E30]
D
ddemay1-Visitor
1-Visitor
July 24, 2013


Here you go. The key here is knowing how the value is stored in the
database. Its type is string. Therefore:



Pick one value from the enum or update to something not meaningful as
provide as a arg:





<attrvalue id="theChangeNoticeComplexity"&lt;br"/>algorithm="wt.rule.algorithm.StringConstant">

<arg>SIMPLE</arg>

</attrvalue>







Tested on 10.1 M010. No other steps should be required. Alternatively one
could also write their own algorithm class here.



Side note: LogicalAttributes.xml now stored in database table of similar
name. XML file maintained for older code still in system. You can still
configure one or the other.





Cheers,

Dave








P
pwilliams-313-AquamarineAuthor
13-Aquamarine
July 24, 2013
Dave,
I'm on 10.1 M040 and I'm trying to do this on a soft type of CN. Did you try this on a soft type? I still can't seem to get it to work.

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image007.jpg@01CE87F1.396BD780]
D
ddemay1-Visitor
1-Visitor
July 24, 2013
Yes, on a soft typed CN to allow for conditional use.




P
pwilliams-313-AquamarineAuthor
13-Aquamarine
July 24, 2013
Here is my OIR for my CN soft type where I set "theChangeNoticeComplexity" to COMPLEX but when I start a new ECN it is populated with Fast Track instead of Full Track. What am I doing wrong?

<attributevalues objtype="net.steelcase.na.EngineeringChangeNotice">


<attrvalue id="folder.id" algorithm="com.ptc.core.foundation.folder.server.impl.FolderPathAttributeAlgorithm">
<arg>/Default/Change Objects</arg>
</attrvalue>


<attrvalue id="lifeCycle.id" algorithm="com.ptc.core.foundation.lifecycle.server.impl.LifeCycleTemplateAttributeAlgorithm">
<arg>Engineering Change Notice Life Cycle</arg>
</attrvalue>


<attrvalue id="teamTemplate.id" algorithm="com.ptc.core.foundation.team.server.impl.TeamTemplateAttributeAlgorithm">
<arg>Change Notice Team</arg>
</attrvalue>


<attrvalue id="theChangeNoticeComplexity" algorithm="wt.rule.algorithm.StringConstant">
<arg>COMPLEX</arg>
</attrvalue>
</attributevalues>

[cid:image005.jpg@01CE884C.4E86C430]

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image006.jpg@01CE884C.4E86C430]
S
sdrzewiczewski10-Marble
10-Marble
July 24, 2013
Your first line is wrong, you need to call out the parent object first

<attributevalues objtype="wt.change2.WTChangeOrder2|" net.steelcase.na.engineeringchangenotice=" &quot;=">
S
SteveVinyard1-Visitor
1-Visitor
July 24, 2013
Could this be used to set the value to blank? It's crazy that the value is prepopulated permanently (from TS). I get users accidentally selecting the wrong track all the time because they forgot. I've had to hide the OOTB complexity, adjust the OIR like here and simply create my own complexity attribute for use.

[cid:image006.gif@01CE8858.C11CC1F0]

Steve Vinyard
Senior Solution Architect
Show more replies
Terms & ConditionsAccessibility statement