Improve cascading attribute functionality as described in CS308511 (Windchill 12.0)

[SvenVD]

Cascaded attribute value change on Edit page still shows the derived attribute with initially pre-selected value although the driver attribute is changed.  

Whenever you change the driver attribute value, the list of the driven attribute should be updated according to the configured cascading attribute rules.  This means the initially set value should be removed from the list for the driven attribute. 

It doesn't make sense a user needs to manually set a driven attribute on the edit page while this driven attribute is set automatically on the creation page.

[olivierlp]

Hello SV_10072643 and welcome to the PTC Community.

Thank you for publishing your idea. However, we need more information as specified in the form you saw in the submission process. (Questions below). The more details and context you give, the better. 

Please let us know within the next two weeks.

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.

2. What product & version are you currently running?

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.

4. What is the use case for your organization?

5. What business value would your suggestion represent for your organization?

[SvenVD]

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.

Windchill Functional Consultant for PTC Partner, stakeholders are our customers

2. What product & version are you currently running?

Windchill 12.0

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.

Improve cascading attribute functionality as described in CS308511

4. What is the use case for your organization?

Demo for potential new customer and improvement for existing customers

5. What business value would your suggestion represent for your organization?

Customer satisfaction

[olivierlp]

Hello, 

Thank you for your idea and the information you provided.

[LawrenceS]

@olivierlp, I just came across this article as my company is running across this problem as well and would like to add more info

1. We are the end-users
2. WC 12.0
3. We want to use cascading attributes functionality to use the 1st company attribute to drive the 2nd company attribute on a Change Notice (CN).  Both sets of attributes are defined using Global Enumerations  On the Create page this works fine (as long as we remove the possibility of having a blank entry...otherwise it fails here too), however, it doesn't work if we edit the ECN later.  The first attribute can no longer drive the 2nd attribute as there are 2 items in the 2nd attribute drop-down list when the cascading attribute says there should only be one.  If you would like screenshots, please reach out to me.
4. Described in 3. above...but this is essentially being used to convert a verbose attribute into a 1 word attribute that is more user-friendly for searching.
5. Avoid confusion, miscommunication, and false change severity priority assignment.  In addition, this has the potential to help significantly when we start using WTParts for semi-automation of certain processes.  As it works now Cascading Attributes is broken with no use and no future use-cases.

[olivierlp]

@SvenVD and @LawrenceS    Thank you both for this info!