Did the data model fundamentally change in 9.2.2?
By abhijit.kakhandiki on Oct 08, 2008
This was a question asked by a customer who is the process of upgrading to 18.104.22.168 from 9.2.1. Most of the customers are aware that there were a lot of functionality and usability improvements in 9.2.2 especially in the Product Portfolio Management (PPM) module. e.g. user feedback regarding consolidating all project related information on a single screen led to a single Content tab for the Programs base class that combines the Relationships, References, Attachments and Links functionality in earlier releases. But did this lead to a fundamental data model change that repurposed the use of fields such as name and number? What are implications for upgrade?
The short answer is no. Let me offer some details here, specifically regarding the changes seen in the Relationships, Content tabs.
The Name column in the Content tab for Program base class and its subclasses (and Relationship tab for other base classes) was added for usability reasons. The Content and Relationship tabs are unique because they may need to display a wide range of sub-classes depending on a variety of customer use-cases. Depending on the object type, the Name column displays the name, number or other details of the object. e.g. for documents and parts, it displays the number, for activities and gates, it displays the name, for File folders it displays the names of the files etc. This was done so the users could identify the content on a program more easily. e.g. in most cases a user wants to get to the file in a file folder, and the file folder number conveys little useful information, hence we display the filename in the 'Name' column. Similarly for activities, the name is the more useful than the activity number, hence the choice of displaying name there.
The number column in the Content and Relationship tabs is the same as the original, but is disabled out of the box. Customers can enable the Number column, but think of the new Name column as a best of both from an information conveyance perspective.
Note that this does not change the original intent behind name and number in the data model for the objects in question. The data model for parts, documents, activities, sourcing projects etc. remains the same. Think of the Name field in the Content and Relationship tabs as a field optimized for displaying information in a convenient and useful manner to the users. It serves as a multi-purpose field to represent the diverse range of objects found in Agile PLM. Hope that clears things up a bit. Let me know what you think.