Reusing Cascading rules between Types

[SM_10804525]

Version: Windchill 12.0

Use Case: We have two enumerated attributes we use together. On a Type we have spent a lot of time entering a list of rules on the cascading attributes tab. We would like to reuse this logic on another Type. There seems to be no way to Export /Import this rule set. Does anyone know a way to do this?

Description:

We have two enumerated attributes we use together. On a Type we have spent a lot of time entering a list of rules on the cascading attributes tab. We would like to reuse this logic on another Type. There seems to be no way to Export /Import this rule set. Does anyone know a way to do this?

[avillanueva]

Possible that you can post some screenshots?

[jack456jokky]

Hello,

Thanks for submitting the issue.

You put a lot of effort into setting up your cascading attributes and now need a way to reuse this configuration. While there isn’t a direct export/import feature for rule sets in many systems, here are a few potential approaches you could consider:

Manual Replication: Although time-consuming, manually replicating the rules on the new Type ensures accuracy. You can open the cascading attributes tab side-by-side and copy the rules over.
Scripting or Automation: If your system supports scripting or has an API, you might be able to write a script to export the rules from one Type and import them into another. This would require some programming knowledge but could save time in the long run.
Configuration Management Tools: Some advanced configuration management tools or plugins might offer the ability to export and import configurations, including rule sets. Check if your system has any such tools available.
Consult Documentation or Support: Sometimes, the functionality might be hidden or not well-documented. Reviewing the official documentation or reaching out to the support team of your software could provide insights or alternative methods.
Community Forums: Engaging with community forums or user groups for your specific software can be very helpful. Other users might have faced similar challenges and could offer solutions or workarounds.

Hope that helps.

[joe_morton]

You might be able to export the entire Type, manually manipulate the exported file(s) to change the Type specified, then Import it.

This would definitely fall under the category at "proceed at your own risk"

Typical Export/Import ref:

https://www.ptc.com/en/support/article/CS30168?source=search

[mmeadows-3]

When you say another Type, do you mean another subtype of the same modeled type (i.e. two different WTPart subtypes)?  Or do you want to transfer them from one modeled type to another (i.e. WTPart to WTDocument)?

@joe_morton's response may be viable if it is two subtypes of the same modeled type.  Doubt that would work trying to transfer from WTPart to WTDocument due to variations in parameter definitions.

Definitely a non-production system exercise.  The load files for Types can get quite large, especially as the number of subtypes, parameters, conditions, enumerated lists, cascading rules, etc. grow.