Comments Hierarchy
- Last UpdatedJul 29, 2024
- 3 minute read
Comment world elements are the owners of common threads, which in turn own comment posts. Comment worlds and associated elements are stored in the Cross Product database.
Before comments and/or suggestions can be added, the correct hierarchy must be in place and as with all elements in the software, all the Lexicon module elements are owned by other elements, therefore elements must be created in a strict order.
Create and Configure Comment World
The CommentConfigurationForm window is populated with the all the comments world elements in the cross product databases. Use the functionality to add a new comments world or open and/or modify an existing one.
Right click to New to display the CommentWorldConfig window and create a new Comment World element in the Dictionary Explorer.
The Comments World element has four major parts:
-
Name
-
Database
-
Selection Rule
-
Comment World Slaves.
|
Name |
Enter a name for the comment world element. |
|
Database |
Select the appropriate database from the list of available ones (the list is populated with cross product databases depending on the MDB setup, team membership, global projects and location). |
|
Selection Rule |
Use the Selection Rule functionality (a PML 1 expression for the world) to define which comment world a comment thread will be created in. The default the expression is set to true which means any comment thread created can be stored in the current comment world. The element that the expression is evaluated against is the element that the comment thread is attached to. Note: Defining what comment world will store the comment thread without having to manage it with a MDB setup. Can be particularly useful when not every comment thread is to be visible to everyone (for example: working with subcontractors). When searching for a suitable comment world to create a thread in, all comment worlds with a selection rule that is not set to true will be considered first, then comments world with a selection rule that equals true. The order of the search is governed by the order that the databases are defined in the MDB, so the first comment world with a selection rule that evaluates to true will be used. Note: It is recommended to have one comment world with a selection rule set to true, so that there is always a suitable world to store the comment thread in. For example: all threads attached to Equipment (EQUIP) elements are stored in the comment world named EQUIPCOMMENTS, while all others goes into the PIPECOMMENTS comment world. |
|
Comment World Slaves |
Use the Comment World Slaves functionality to set up a Master-Slave relationship between comments worlds to overcome the problem when the database that the comment world and hence the comment thread is not writable. This means, setting up a comment world as a secondary to another means the selection rule used will be the one defined in the primary comment world. When creating a post in a comment thread in a comment world that is not writable, a shadow thread is created in the slave comment world, if writable the post will be stored in the shadow thread. When presenting the thread, the system will automatically merge the content of the thread and its slave thread(s) into one. For example: The comment world named CIVILCOMMENTS is defined as a slave to the comment world EQUIPCOMMENTS.
This functionality is particularly useful in a global scenario, as there is no need for setting up extracts to make it possible to update from different locations. Note: |
