cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

CEM tables should be implemented as configurable table views

CEM tables should be implemented as configurable table views

The Windchill Customer Experience Management (CEM) module has a number of tables within the module that are restrictive as far as the columns that can be added or removed. This is because they are not implemented as configurable tables. I would like the capability to configure the columns/attributes presented in the UI by creating custom table views via the table view manager for such tables. Examples are Related Persons and Related Products tables in the Complaint Intake wizard, tables in the Complaint Management tab etc.

This issue extends farther than the UI's mentioned as examples above. Across the board in CEM, the standard Windchill design of using configurable table views should be implemented to allow for easily configurable UI's.

2 Comments

This specific functionality would be of significant additional value in the Related People and Places table, since it would enable the addition of address details to the native UI.

In the event that 2 places are added which are both a part of the same business (and therefore have the same name), the address is a useful way of identifying which site serves which function.

For example, a company might be the medical facility (ie classified as Hospital) in which a patient was treated but may also be supplying spares from a separate facility and so may be added to assist with tracking.

Regular Member

Tables should always be configurable and consistent across the board.

PTC should have start procedure that if the developer (at PTC) needs a table in his module, the table MUST have such functionalities

So look and feel are the same every where within all PTC products.

PTC recommends its customer for product reuse,  the same should apply in PTC product.  reuse your code