Support Cascading Attributes for edit in the Structure tree

[estefanovska]

We tested with the colleagues in OOTB ( 11.1 M020) the behave of two cascading attributes in structure view .

The structure edit mode is not working. For example : 

 Both attributes we created are used in global enumeration value. If there is only one attribute than the drop down menu in the structure table view is editable. But when there are two cascading attributes connected with a rule the structure view can not be edited. The Idea here is: Possibility to support the cascading attributes for editing in the structure tree!

Please refer to the screen shots for more information. 

[BjoernRueegg]

It would also be cool, if we could drive attributes across types. E.g. If the WTPart is a component, then you can choose different attribute values on the usage link.

[zmayo]

Forgive me if I'm wrong, but I think my organization is experiencing a similar issue.  We have run into trouble editing attributes for documents and CAD files when they have cascading values.  Any attribute included in a cascading rule isn't editable.  Our employees want to use cascading values because it makes lists shorter but they also rely on the ability to edit attributes for multiple documents/CAD files.  If the attribute has cascading rules, they are unable to edit it in this manner.  The idea of cascading attributes is great but so far we have been unable to use it because it has limited other functionality that people rely on.

[JeffZemsky]

@zmayo Some notes

1) CAD Documents are not yet supported

2) Parts, Documents and Changes are supported.  Support for multiple create Wizards (Parts and Documents) was added Windchill 11.1 M010.  I'm attaching a video example with Parts.

[HelesicPetr]

Hello Jeff,

The video is nice, but this is still for new parts.

If someone wants to change the attribute the easy way is to use the structure.

So I vote for this idea.

[JeffZemsky]

@HelesicPetr  That is correct.  That is a roadmap item.  The video above was in response to @zmayo  question about multi-create/multi-edit for Part and Document UIs

[zmayo]

@JeffZemsky   Do you have any update on that roadmap item?

[JeffZemsky]

@zmayo Cascading are supported in WTDocument since 11.1 M000 with single/create edit and M010 with multi-create edit.  EPMDocuments are not supported for Cascading attributes.

[kranck]

@JeffZemsky Is there any progress in WC12 to help with cascading attributes? I work with @zmayo so we are trying to make things easier for our users (we have 130 locations worldwide so scrolling thru a long list can be time consuming when you do it over and over again.

[abhishekarya]

@JeffZemsky looks like cascading attributes are not supported for multi value attributes, any plans in future to include multi value?

[JeffZemsky]

@abhishekarya This is a roadmap item.  We also have some questions on expectations here - eg - if you select a Driver that is multi-value - should the driven give you just the Intersection or the Union of the potential Driven attributes?   Or would you have use cases for both depending upon the specific information

[LawrenceS]

I tested this for attributes on a Change Notice and it works beautifully when you first create the CN, but then falls on its face when you try and edit the ECN and update the value.  It doesn't automatically pick the item, It just adds it to the list but it doesn't remove the previous value.

Essentially when editing the CN it turns into a CHECK, and is no longer DRIVING.  Unfortunately, this make it annoying enough to not be useful.  Very disappointing

[JeffZemsky]

@LawrenceS  sounds like a a bug.  What version are you using?

[LawrenceS]

I agree. WC 12.0.2.3