Difference between revisions of "Features/Status level dependencies"
Jump to navigation
Jump to search
| (8 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
Example: | Example: | ||
A hr-management system is used to show information on employees who are assigned to projects. These employees are either currently working on a project or between projects. Or they might be in the process of being hired and would therefore not be a full employee yet. Depending on which of these states the employee is currently in, different information about them would be made available. If they were under consideration of being hired, we should see their application. If they were working on a project, we should see their work schedule. If they were between projects, we should see the end date of their last project. Each piece of information should only be made visible for the status in question, since they make no sense or are unimportant otherwise. Status level dependencies are used to manage this visibility. | |||
== | == Guide == | ||
[[File:Levels.png|thumb|397x397px|Picture 1]] | [[File:Levels.png|thumb|397x397px|Picture 1]] | ||
To see the status levels of an | Status levels are numerical categories that one or more statuses can belong to. | ||
Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level. | |||
For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels. | |||
To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1. | |||
[[File:Picture 2.png|thumb|Picture 2]] | [[File:Picture 2.png|thumb|Picture 2]] | ||
To change a status's level, go to that status and edit it as shown in picture 2. | To change a status's level, go to that status and edit it as shown in picture 2. | ||
[[File:Advanced toggle.png|thumb|Picture 3]] | [[File:Advanced toggle.png|thumb|Picture 3]] | ||
[[File:Level dependency.png|thumb|Picture 4]] | [[File:Level dependency.png|thumb|Picture 4]] | ||
To set the dependency, toggle the advanced view of the | To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4. | ||
Latest revision as of 12:31, 28 August 2023
What it is
Example:
A hr-management system is used to show information on employees who are assigned to projects. These employees are either currently working on a project or between projects. Or they might be in the process of being hired and would therefore not be a full employee yet. Depending on which of these states the employee is currently in, different information about them would be made available. If they were under consideration of being hired, we should see their application. If they were working on a project, we should see their work schedule. If they were between projects, we should see the end date of their last project. Each piece of information should only be made visible for the status in question, since they make no sense or are unimportant otherwise. Status level dependencies are used to manage this visibility.
Guide
Status levels are numerical categories that one or more statuses can belong to. Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level. For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels. To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1.
To change a status's level, go to that status and edit it as shown in picture 2.
To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4.