"Change Summary" table in Change Notice information page displays the same object multiple times

[HerwigSchwarz]

As described in CS48553.

Change Summary table in Change Notice information page displays the same object multiple times, if it is a part of multiple Change Task

I can see no purpose in having the same object in this table multiple times.

In fact I have the use case, where there are 10 or 20 or more Change Activities where the same Part is included as an affected or resulting object. Showing the same row 20 times makes the table quite confusing.

[JeffZemsky]

@HerwigSchwarz what is the use case that you are having the same item on so many different Affected/Resulting tables?  Is it used as supporting information for other tasks?  Is additional work done?  It would be interesting to understand your use case.  Thank you.

[HerwigSchwarz]

@JeffZemsky  The customer uses change notices and tasks for creating all kinds of processes.

Release process of course, but also failure analysis process, technical enhancement process, prototype, initial batch manufacturing and so on. They have special dynamically created templates for this. Most of the times only 1 WTPart is affected, but 20 tasks are needed in a step-by-step order (they use sequences as well) to finish the process. All tasks are affected by the same part. 

I can help the customer, by writing special MVC components consisting of DataUtility, TableBuilder and default table views. But I feel it's a customization that shouldn't be needed at all.

Let's turn the tables (pun intended):

Can you tell me a use case where it is important to have multiple lines for the same object in this table?

[JeffZemsky]

@HerwigSchwarz Not suggesting its desirable.  Just trying to understand that if we enhanced something -  what users are doing in these additional tasks such that we can provide the best options. 

In this case we might want to provide some other type of relationship for additional work that is not necessarily Resulting. 

For the examples above - can you describe for those additional steps - is the user doing work against the Part (eg iterating it before release) or are they using it for reference for work in other processes or tools?

[HerwigSchwarz]

@JeffZemsky  Both.

In some tasks the parts are only referenced. (e.g. "Check the delivery status in ERP system", "Perform incoming inspection", ...)

In others the parts are to be checked out, edited, checked in. (e.g. "Attach customer specification to WTPart" "Correct the classification attributes", ...)