Features/Status level dependencies - Revision history

Nun: /* What it is */

2023-08-28T11:31:02Z

What it is

← Older revision		Revision as of 13:31, 28 August 2023
Line 2:		Line 2:

	Example:		Example:
	A hr-management system ~~contains some~~ 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.		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 ==		== Guide ==

Nun: /* What it is */

2023-08-28T11:30:03Z

What it is

← Older revision		Revision as of 13:30, 28 August 2023
Line 2:		Line 2:

	Example:		Example:
	~~Say we have a~~ hr-management system ~~containing~~ some 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.		A hr-management system contains some 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 ==		== Guide ==

Nun: /* What it is */

2023-08-28T11:29:17Z

What it is

← Older revision		Revision as of 13:29, 28 August 2023
Line 2:		Line 2:

	Example:		Example:
	Say ~~you had~~ a management system containing employees. These employees ~~have the following information: They have~~ a ~~CV, current working details, and last workday~~. ~~If a given employees can~~ be in a ~~few different statuses then each~~ of the ~~fields might not make sense. If an~~ employee is in ~~the process~~ of being hired, ~~then~~ they ~~would not have any current work details or~~ a ~~specific last~~ work ~~day~~. If ~~the employee~~ were in the ~~process~~ of ~~being fired, then~~ their ~~CV would not matter~~. ~~This example illustrates how you might want to hide away certain record fields depending on which~~ status ~~the record currently is~~ in. Status level dependencies are used to ~~solve~~ this ~~problem~~.		Say we have a hr-management system containing some 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 ==		== Guide ==

Nun: /* How to do */

2023-08-28T07:37:21Z

How to do

← Older revision		Revision as of 09:37, 28 August 2023
Line 4:		Line 4:
	Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.		Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.

	== ~~How to do~~ ==		== Guide ==
	[[File:Levels.png\|thumb\|397x397px\|Picture 1]]		[[File:Levels.png\|thumb\|397x397px\|Picture 1]]
	Status levels are numerical categories that one or more statuses can belong to.		Status levels are numerical categories that one or more statuses can belong to.

Nun: /* How to do */

2023-08-11T09:08:04Z

How to do

← Older revision		Revision as of 11:08, 11 August 2023
Line 6:		Line 6:
	== How to do ==		== How to do ==
	[[File:Levels.png\|thumb\|397x397px\|Picture 1]]		[[File:Levels.png\|thumb\|397x397px\|Picture 1]]
	Status levels are numerical categories that statuses can belong to.		Status levels are numerical categories that one or more statuses can belong to.
	Fields in ~~entities~~ can be configured to depend on these levels such that they can be made inactive if the ~~entity~~ record is not in a status with the correct level.		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 ~~the field is~~ only ~~shown~~ for those levels.		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 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 ~~entity~~ on as shown in picture 3 and go to the bottom as shown in picture 4.		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.

Nun: /* How to do */

2023-08-11T08:03:15Z

How to do

← Older revision		Revision as of 10:03, 11 August 2023
Line 5:		Line 5:

	== How to do ==		== How to do ==
			[[File:Levels.png\|thumb\|397x397px\|Picture 1]]
	Status levels are numerical categories that statuses can belong to.		Status levels are numerical categories that statuses can belong to.
	~~[[File:Levels.png\|thumb\|397x397px\|Picture 1]]~~
	Fields in entities can be configured to depend on these levels such that they can be made inactive if the entity record is not in a status with the correct level.		Fields in entities can be configured to depend on these levels such that they can be made inactive 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 the field is only shown for those levels.		For example can the dependency be set for all status levels above a certain value such that the field is only shown 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 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.

Nun at 08:02, 11 August 2023

2023-08-11T08:02:55Z

← Older revision		Revision as of 10:02, 11 August 2023
Line 5:		Line 5:

	== How to do ==		== How to do ==
	Status levels are numerical categories that statuses can belong to.		Status levels are numerical categories that statuses can belong to.
			[[File:Levels.png\|thumb\|397x397px\|Picture 1]]
	Fields in entities can be configured to depend on these levels such that they can be made inactive if the entity record is not in a status with the correct level.		Fields in entities can be configured to depend on these levels such that they can be made inactive 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 the field is only shown for those levels.		For example can the dependency be set for all status levels above a certain value such that the field is only shown for those levels.
	~~[[File:Levels.png\|thumb\|397x397px\|Picture 1]]~~
	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 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]]

Nun: added introduction

2023-08-11T08:02:20Z

added introduction

← Older revision		Revision as of 10:02, 11 August 2023
Line 2:		Line 2:

	Example:		Example:
	Say you had a management system containing employees. These employees have the following information: They have a CV, current work		Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.

	== How to do ==		== How to do ==
	Status levels are numerical categories that statuses can belong to.		Status levels are numerical categories that statuses can belong to.

	Fields in entities can be configured to depend on these levels such that they can be made inactive if the entity is not in the correct ~~status~~ level.		Fields in entities can be configured to depend on these levels such that they can be made inactive 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 the field is only shown for those levels.		For example can the dependency be set for all status levels above a certain value such that the field is only shown for those levels.

Nun: /* What it is */

2023-08-10T14:51:32Z

What it is

← Older revision		Revision as of 16:51, 10 August 2023
Line 2:		Line 2:

	Example:		Example:
	~~Hello world !~~		Say you had a management system containing employees. These employees have the following information: They have a CV, current work

	== How to do ==		== How to do ==

Kpe at 14:33, 10 August 2023

2023-08-10T14:33:45Z

← Older revision		Revision as of 16:33, 10 August 2023
Line 1:		Line 1:
			== What it is ==

			Example:
			Hello world !

			== How to do ==
	Status levels are numerical categories that statuses can belong to.		Status levels are numerical categories that statuses can belong to.