Inheritance and Hierarchy

Top  Previous  Next

Inheritance

In mSuite and mDesign Server, a group can be placed inside of another group to created a sub-group.  Sub-groups display the following properties:

 

Sub-groups will inherit the properties of the containing group.
Some inherited properties can be overridden at sub-group level
If the sub-group contains it's own sub-group/users, these will inherit any overwritten properties.

 

Example

 

You may have 3 groups - A, B, C.

 

A is the top level group.
B is a sub-group of A.
C is a sub-group of B.

 

Without any changes being made, C will have the properties of B and B will have the properties of A, making the properties of all three groups the same.

If a property in B is changed, C and B will have this change, A will not.

 

 

How mSuite / mDesign Server implements inheritance

In the MMC plugin, 'Users and Groups' is the default top level container.  This group has all of the CommonTime defaults set as its properties and you cannot edit the properties of this container.

 

If you want to redefine the defaults, create a group in this container and make the changes in the properties of this group. You should then ensure that all future groups inherit from this new top level group. An example is shown in the illustration below:

 

 

 

 

 

A new group called 'Top Level Group' has been added to apply new default settings. This would be the only group at this level, will all groups inheriting from this group.
All main groups (Group 1, Group 2 etc) inherit from the new top level group.
Group 1, Group 2 etc can have their own sub-groups (e.g. Group 1A, Group 1B etc)

 

Users inherit settings from their group, and any groups higher up the chain.
If settings have been overwritten, the settings of the group it resides in will take precedence,
For example, User 1 will take its properties first from Group 1A, then Group 1, then Top Level Group.

 

 

Multiple Inheritance

Please make sure that each group or user is only a member of one and only one direct parent group.  In this way you will avoid multi-inheritance scenarios, where a user or group inherits its properties from more than once place.  Multi-inheritance is hard to understand and support and the results often seem unpredictable.

 

Overriding Inheritance

If you change a property in a group or user, the change will override the inheritance. All other properties will continue to be inherited, but the overridden property will be set for the user or group and any lower level inheriting user or groups.  So, with reference to the illustration above, if a property is changed at Group 1, the change will affect Group 1A and Group 1B and everything inside those groups.

 

 

Setting Properties

The image below illustrates how to set properties for mNotes. Wherever Properties are inherited in an mSuite system, controls similar to the following are displayed.

 

 

 

When you run the configuration wizard and make changes to the settings, you will change the properties for this group or user.  If the object is a group, any item contained by the group will inherit the changed properties.

 

If you discard property changes made at this object, you will restore the inheritance, i.e. the current property set will be inherited from the parent group.

 

Show the property inheritance table displays a table that will let you determine where a setting value originated.  This display will also highlight any property conflicts.  These will be displayed in red.  You can also use this facility to display only conflicts.  If you have conflicts, please resolve them as they may well cause unpredictable behavior.

 

 

 


Page url: http://msuitehelp.commontime.com/index.html?ct_qs_hierarchy.htm