Following Resources
Go Up to Working with Resources
Team Server keeps track of people activity surrounding resources (glossaries, terms, ER objects, and data sources). It records when someone edits a resource, posts a comment to a resource, and so on.
You can follow a resource so that you can keep track of all the activity that surrounds that resource. You can see the activity of every resource that you are following in your Home page.
Contents
Understanding Cascading Follow Hierarchy
Team Server 16.5 and later allow you to follow some ER Objects such as glossaries and terms using Cascading Follow Hierarchy (CFH). CFH means that when a user chooses to follow an object in a parent/child hierarchy, any changes made to lower-level "child" objects also flag the upper-level "parent" as changed.
For example, if a change is made to any aspect of Column F, then that column is changed. Because Column F is part of Table 2, that table also is changed. Because Table 2 is part of Submodel A, that submodel also is changed. Finally, because Submodel A is part of Model A, that model also is changed. The following structure illustrates this example object hierarchy where the child objects are indented under their immediate parent:
Model 1
Submodel A
Table 1
Column A
Column B
Column C
Table 2
Column D
Column E
Column F
The main purpose of a Cascading Follow Hierarchy is to notify users when a change occurs to a child of a parent object the user is following. For example, Users need to know when a table in a model they are following is added, deleted, or modified in any way. Likewise, users need to know when a column in a table of a model they are following is modified, added, or deleted. For this reason, notifications are generated and appear in the user's Activity Stream page and email.
Parent objects are objects that contain a set of child objects. A parent object may contain multiple types of child objects and, in turn, a child object may be a parent to its own set of objects. If you choose to follow a parent object, you are implicitly following all child objects and all lower levels for that object. Team Server includes three sets of objects:
- Team Server objects, i.e. glossaries and terms
- ER/Studio Data Architect objects
- ER/Studio Business Architect objects
Team Server Objects
| Parent | Child |
|---|---|
| Glossary | Child Glossaries, Terms |
| Child Glossary | Child Glossaries, Terms |
| Terms | No children to follow |
| Datasource | No children to follow |
| People | No children to follow |
ER/Studio Data Architect Objects
| Parent | Child |
|---|---|
| Diagram | Logical and Physical Data Models |
| Logical Model | Submodels, Entities, Views, Relationships |
| Physical Model | Submodels, Tables, Views, Relationships |
| Logical Submodel | Submodels, Entities, Views, Relationships |
| Physical Submodel | Submodels, Tables, Views, Relationships |
| Entity | Attributes, Indexes |
| Table | Columns, Indexes |
| View | View Columns |
| Attribute | No children to follow |
| Column | No children to follow |
| View column | No children to follow |
| Relationship | No children to follow |
| Index | No children to follow |
| Attachment | No children to follow |
| Attachment Binding | No children to follow |
| Attachment Type | Attachments |
| Data Lineage Data Flow | Data Lineage Transformations, Tables |
| Data Lineage Column | No children to follow |
| Data Lineage Source | No children to follow |
| Data Lineage Table | No children to follow |
| Data Lineage Transformations | No children to follow |
| Transformation Column/Attribute | No children to follow |
| Data Movement Rule | No children to follow |
| Dictionary | No children to follow |
| Dictionary Default | No children to follow |
| Domain | No children to follow |
| Index | No children to follow |
| Index Column | No children to follow |
| Key | No children to follow |
| Key Attribute | No children to follow |
| Reference Value | No children to follow |
| Security | No children to follow |
| Security Tape | No children to follow |
| User Data Type | No children to follow |
ER/Studio Business Architect Objects
| Parent | Child |
|---|---|
| Workspace | Business Projects, Business Models |
| Business Project | Business Models |
| Business Model | Process Diagrams, Processes, Sub Processes, Conceptual Diagrams, Subject Areas, Business Entities, Business Relationships, Interactions |
| Process Diagram | Processes and Tasks |
| Process | Sub Processes, Tasks, Events, Gateways, Data Objects |
| Conceptual Diagram | Subject Areas, Business Entities |
| Business Entity | Business Attributes |
| Business Attributes | No children to follow |
| Association | No children to follow |
| Business Element | No children to follow |
| Interactions | No children to follow |
| Business Relationship | No children to follow |
| Business Unit | No children to follow |
| Data Object | No children to follow |
| Data Store | No children to follow |
| Event | No children to follow |
| Gateway | No children to follow |
| Lane | No children to follow |
| Link | No children to follow |
| Message Flow | No children to follow |
| Pool | Lanes |
| Reference Column | No children to follow |
| Reference Entity | No children to follow |
| Rule | No children to follow |
| Sequence Flow | No children to follow |
| Steward | No children to follow |
| Subject Area | No children to follow |
| Task | No children to follow |
| Usage | No children to follow |