sysRole

sysRole is principal object for system rights assignement, grouping and linkage with user accounts

• Dependencies between roles
• Support for integration with business description
  • Usage notes
• Technical notes to the role object implementation
  • Insert

Role object is used to link people with system rights.

Dependencies between roles

Roles might have several ancestors and several subsidiary roles. However, create a cycle is forbidden.

Support for integration with business description

sysRole contains fields that supports simple description of the business structure. These fields are not internally used by the sys module:

• clienType – currently unused
• managerID – optional organisation manager. Fields is not used for person responsible for the system role management.
• userType – unused by sys and not available for the administration management. Optionally could be used by other modules.
  (Unused by other modules in the business bundle – crm, tsk, am, hr).
• link to the object – role can be assigned to a single object. Not used by sys but system administration can remove the linkage.
  (Currently used only for documentation purposes. It is 1-N relationship which is not as useful.)

Usage notes

Manager is used by the tsk module for right control. Team managers got some additional rights to the people in the team

Technical notes to the role object implementation

Insert

sysRole does no use default insert operations beacue it does not correctly works with objectName / objectID fields without default value settings.
If not attribute noPrincipalObject used, standard operation set up objectName field but does not fill objectID (not in the view).

Note: attributes objectName and objectID are very probably superfluous and could be altered with better use the parentObject values.
npm install check-dependencies --save-dev