Approval mechanisms - Revision history

Stefanseiler: /* Approval processes */

2024-09-16T11:14:37Z

Approval processes

← Older revision		Revision as of 11:14, 16 September 2024
Line 16:		Line 16:
	* '''Customer order acceptance''' - Before a customer order is confirmed to the customer a financial approval and material approval must be granted		* '''Customer order acceptance''' - Before a customer order is confirmed to the customer a financial approval and material approval must be granted
	* '''Delivery confirmation''' - Before a bill is payed, the receipt of the shipment must be confirmed		* '''Delivery confirmation''' - Before a bill is payed, the receipt of the shipment must be confirmed
	* '''Digital creation''' - Before a new b-op digital is created, a responsible person must approve the confirmation ~~[[Business reuiqrements for digital creation]]~~		* '''Digital creation''' - Before a new b-op digital is created, a responsible person must approve the confirmation

	===== Default approval strategy =====		===== Default approval strategy =====

Stefanseiler: /* Related articles */

2023-11-02T23:50:25Z

← Older revision		Revision as of 23:50, 2 November 2023
Line 24:		Line 24:
	*		*
	*[[Entitites subject to approval & Task types]]		*[[Entitites subject to approval & Task types]]

			== Related development articles ==
	*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects		*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects
	*[[App:Task manager]] - This app allows responsible persons to grant or reject approvals		*[[App:Task manager]] - This app allows responsible persons to grant or reject approvals

Benjamingoerde at 15:54, 27 October 2023

2023-10-27T15:54:28Z

← Older revision		Revision as of 15:54, 27 October 2023
Line 16:		Line 16:
	* '''Customer order acceptance''' - Before a customer order is confirmed to the customer a financial approval and material approval must be granted		* '''Customer order acceptance''' - Before a customer order is confirmed to the customer a financial approval and material approval must be granted
	* '''Delivery confirmation''' - Before a bill is payed, the receipt of the shipment must be confirmed		* '''Delivery confirmation''' - Before a bill is payed, the receipt of the shipment must be confirmed
	* '''Digital creation''' - Before a new b-op digital is created, a responsible person must approve the confirmation		* '''Digital creation''' - Before a new b-op digital is created, a responsible person must approve the confirmation [[Business reuiqrements for digital creation]]

	===== Default approval strategy =====		===== Default approval strategy =====

Stefanseiler: /* Related articles */

2023-10-12T07:51:43Z

← Older revision		Revision as of 07:51, 12 October 2023
Line 32:		Line 32:
	[[Category:Order Types and related objects]]		[[Category:Order Types and related objects]]
	__NOTOC__		__NOTOC__
			[[Category:Business Epics]]

Stefanseiler: /* Approval processes */

2023-10-12T07:46:06Z

Approval processes

← Older revision		Revision as of 07:46, 12 October 2023
Line 8:		Line 8:

	== Approval processes ==		== Approval processes ==
	ZUGSEIL supports many approval for many entity types. The approval process is for all entity types subject to approval/confirmation processes governed by the [[Dev:Approval agent\|approval agent]] and entity specific approval strategies, which can be administered in our [[App:Approval strategies administration\|approval strategy adiministration app]].		ZUGSEIL supports many approval for many entity types. The approval process is for all entity types subject to approval/confirmation processes governed by the [[Dev:Approval agent\|approval agent]] and [[Entitites subject to approval & Task types\|entity specific approval strategies]], which can be administered in our [[App:Approval strategies administration\|approval strategy adiministration app]].

	~~== Specifics to~~ approval ~~strategy types ==~~		ZUGSEIL offers highly configurable approval strategies for these processes:

			* '''Internal order approval''' - Before an [[internal order]] is processed financial approval, material approval, team order approval, personal equipment approval must be granted
			* '''Purchase order approval''' - Before a [[purchase order]] is forwarded to the supplier a financial approval and material approval must be granted
			* '''Customer order acceptance''' - Before a customer order is confirmed to the customer a financial approval and material approval must be granted
			* '''Delivery confirmation''' - Before a bill is payed, the receipt of the shipment must be confirmed
			* '''Digital creation''' - Before a new b-op digital is created, a responsible person must approve the confirmation

	===== Default approval strategy =====		===== Default approval strategy =====
	''For each'' approval strategy type you may define <u>one</u> default strategy. When picking a strategy, e.g. for digital creation of within a shopping purpose you always have the option "Use default approval strategy" instead of selecting a specific approval strategy. This allows central manipulation of approval strategies without the need to locate each place where it was used.		''For each'' approval strategy type you may define <u>one</u> default strategy. When picking a strategy, e.g. for digital creation of within a shopping purpose you always have the option "Use default approval strategy" instead of selecting a specific approval strategy. This allows central manipulation of approval strategies without the need to locate each place where it was used.

	~~===== Financial approval priority =====~~
	''Financial approval strategies'' offer the option to define a priority. This is required as there are multiple sources of authority to define the appropriate financial approval strategy which might result in multiple applicable financial approval strategies. For this case exist priority. Always the one with the highest priority will be used (highest priority is 1).

	<u>Example</u>: Shopping purpose says that orders have to undergo a financial approval strategy A, which has priority 3. But on the same order there are products, which are registered with a classification element which forces a financial approval strategy B, which has priority 2. As a result, the order will have to undergo strategy B, as it has the higher priority.

	== Related articles ==		== Related articles ==

	*		*
			*[[Entitites subject to approval & Task types]]
	*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects		*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects
	*[[App:Task manager]] - This app allows responsible persons to grant or reject approvals		*[[App:Task manager]] - This app allows responsible persons to grant or reject approvals

Stefanseiler: /* Approval processes */

2023-10-12T07:38:35Z

Approval processes

← Older revision		Revision as of 07:38, 12 October 2023
Line 8:		Line 8:

	== Approval processes ==		== Approval processes ==
	ZUGSEIL supports many approval for many entity types. The approval process is for all entity types subject to approval/confirmation processes governed by the [[Dev:Approval agent\|approval agent]] and entity specific ~~[[Approval extensions for onboarding workflow\|~~approval strategies]], which can be administered in our [[App:Approval strategies administration\|approval strategy adiministration app]].		ZUGSEIL supports many approval for many entity types. The approval process is for all entity types subject to approval/confirmation processes governed by the [[Dev:Approval agent\|approval agent]] and entity specific approval strategies, which can be administered in our [[App:Approval strategies administration\|approval strategy adiministration app]].

	== Specifics to approval strategy types ==		== Specifics to approval strategy types ==

Stefanseiler at 07:37, 12 October 2023

2023-10-12T07:37:20Z

← Older revision		Revision as of 07:37, 12 October 2023
Line 6:		Line 6:
	#'''Alignment with Goals -''' Companies have specific objectives, mission statements, and strategic goals. Approval strategies help ensure that decisions made at various levels of the organization are aligned with these broader goals, contributing to the company's overall success.		#'''Alignment with Goals -''' Companies have specific objectives, mission statements, and strategic goals. Approval strategies help ensure that decisions made at various levels of the organization are aligned with these broader goals, contributing to the company's overall success.
	#'''Regulatory and Legal Compliance -''' Many industries are subject to strict regulations and legal requirements. An approval strategy helps ensure that decisions and actions taken by the company adhere to these regulations. This can help prevent legal issues, fines, or other negative consequences that may arise from non-compliance.		#'''Regulatory and Legal Compliance -''' Many industries are subject to strict regulations and legal requirements. An approval strategy helps ensure that decisions and actions taken by the company adhere to these regulations. This can help prevent legal issues, fines, or other negative consequences that may arise from non-compliance.

			== Approval processes ==
			ZUGSEIL supports many approval for many entity types. The approval process is for all entity types subject to approval/confirmation processes governed by the [[Dev:Approval agent\|approval agent]] and entity specific [[Approval extensions for onboarding workflow\|approval strategies]], which can be administered in our [[App:Approval strategies administration\|approval strategy adiministration app]].

	== Specifics to approval strategy types ==		== Specifics to approval strategy types ==


	===== Default approval strategy =====		===== Default approval strategy =====

Stefanseiler: /* Approval strategy types */

2023-10-12T07:34:42Z

Approval strategy types

@@ Line 6: / Line 6: @@
 #'''Alignment with Goals -'''  Companies have specific objectives, mission statements, and strategic goals. Approval strategies help ensure that decisions made at various levels of the organization are aligned with these broader goals, contributing to the company's overall success.
 #'''Regulatory and Legal Compliance -'''  Many industries are subject to strict regulations and legal requirements. An approval strategy helps ensure that decisions and actions taken by the company adhere to these regulations. This can help prevent legal issues, fines, or other negative consequences that may arise from non-compliance.
 == Specifics to approval strategy types ==
@@ Line 35: / Line 21: @@
+*
 *[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects
 *[[App:Task manager]] - This app allows responsible persons to grant or reject approvals
 *[[Dev:Approval agent]] - The central service, which governs the approval process depending on the settings made in the applicable approval strategy.

Stefanseiler at 05:15, 12 October 2023

2023-10-12T05:15:24Z

← Older revision		Revision as of 05:15, 12 October 2023
Line 36:		Line 36:
	*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects		*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects
	*[[Dev:Financial approval strategy settings]]		*[[Dev:Financial approval strategy settings]]
	*[[App:~~Pending tasks~~]] - This app allows responsible persons to grant or reject approvals		*[[App:Task manager]] - This app allows responsible persons to grant or reject approvals
	*[[Dev:Approval agent]] - The central service, which governs the approval process depending on the settings made in the applicable approval strategy.		*[[Dev:Approval agent]] - The central service, which governs the approval process depending on the settings made in the applicable approval strategy.
	*[[Dev:Digital deployment service]] - The central service for automatic deployment of digitals.		*[[Dev:Digital deployment service]] - The central service for automatic deployment of digitals.

Stefanseiler at 10:02, 2 September 2023

2023-09-02T10:02:50Z

← Older revision		Revision as of 10:02, 2 September 2023
Line 12:		Line 12:
	Before the processing of a [[Purchase order\|''purchase order'']] or ''[[internal order]]'' may start, each order needs to fulfll these four approval criteria:		Before the processing of a [[Purchase order\|''purchase order'']] or ''[[internal order]]'' may start, each order needs to fulfll these four approval criteria:

	* '''Financial approval''' - Depending on ~~predefined~~ [[Dev:Financial approval ~~strategies~~\|financial approval ~~strategies~~]], different parties need to approve the order. The financial approval type for an order is defined by the [[App:Shopping purpose administration\|shopping purpose]], but can be overridden by classification elements of the products on the order.		* '''Financial approval''' - Depending on defined [[Dev:Financial approval strategy settings\|financial approval settings]], different parties need to approve the order. The financial approval type for an order is defined by the [[App:Shopping purpose administration\|shopping purpose]], but can be overridden by classification elements of the products on the order.
	* '''Material approval''' - Special product groups require a product group manager to approve the order before it is granted (e.g. shotguns). The material approval type for an order is defined by classification elements of the products on the order. Please note that each product on an order may trigger its own material approval process, e.g. if different staff are responsible for different materials. (guns vs. ppe)		* '''Material approval''' - Special product groups require a product group manager to approve the order before it is granted (e.g. shotguns). The material approval type for an order is defined by classification elements of the products on the order. Please note that each product on an order may trigger its own material approval process, e.g. if different staff are responsible for different materials. (guns vs. ppe)
	*'''Team manager approval''' - when staff is ordering through the [[Dev:Team ordering assistant\|team ordering assistant]], you may define that team managers have to approve each or specific orders. The applicable team manager approval is defined within the [[App:Shopping purpose administration\|shopping purpose]].		*'''Team manager approval''' - when staff is ordering through the [[Dev:Team ordering assistant\|team ordering assistant]], you may define that team managers have to approve each or specific orders. The applicable team manager approval is defined within the [[App:Shopping purpose administration\|shopping purpose]].
Line 35:		Line 35:
	*		*
	*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects		*[[App:Approval strategies administration]] - This app allows approval strategies, which can be bound to many approval govering objects
			*[[Dev:Financial approval strategy settings]]
	*[[App:Pending tasks]] - This app allows responsible persons to grant or reject approvals		*[[App:Pending tasks]] - This app allows responsible persons to grant or reject approvals
	*[[Dev:Approval agent]] - The central service, which governs the approval process depending on the settings made in the applicable approval strategy.		*[[Dev:Approval agent]] - The central service, which governs the approval process depending on the settings made in the applicable approval strategy.