Workflow (Window ID-113) - Revision history

Eugenh: Workflow Components

2020-04-23T14:48:04Z

Workflow Components

Eugenh: /* Workflows in piere /

2020-04-23T14:43:50Z

Workflows in *piere

Eugenh: /* Contributions / Posts / Workflows in piere

2020-04-23T14:19:12Z

Contributions / Posts: Workflows in *piere

CarlosRuiz: template generated from idempiere51

2017-11-17T13:32:17Z

template generated from idempiere51

CarlosRuiz: move language from template to manpage

2017-11-15T16:36:40Z

move language from template to manpage

Wikirobot: Created page with " Category: Reference Manual {{Workflow (Window ID-113 V1.0.0)}} ==..."

2013-05-01T16:52:57Z

Created page with "  Category: Reference Manual {{Workflow (Window ID-113 V1.0.0)}}  ==..."

New page

[[Category: Reference Manual]]

{{Workflow (Window ID-113 V1.0.0)}}


==Contributions / Posts==

← Older revision		Revision as of 14:48, 23 April 2020
Line 62:		Line 62:
	====Record Value Workflow====		====Record Value Workflow====
	Record or Document Value Workflows are invoked when a specific condition is met. This can be for a document or maintenance window. These are entirely user defined. An example of a Record Value Workflow can be found in GardenWorld. The Business Partner Approval Workflow is based on the Business Partner table. It is invoked whenever a new Business Partner is added. The condition is Created Date and UpdatedDate are equal as this condition would only resolve to true when a record is first added. A notice is sent to a supervisor. You could then extend this workflow to include tasks like validate email addresses, perform a credit check, assign a sales representative etc.		Record or Document Value Workflows are invoked when a specific condition is met. This can be for a document or maintenance window. These are entirely user defined. An example of a Record Value Workflow can be found in GardenWorld. The Business Partner Approval Workflow is based on the Business Partner table. It is invoked whenever a new Business Partner is added. The condition is Created Date and UpdatedDate are equal as this condition would only resolve to true when a record is first added. A notice is sent to a supervisor. You could then extend this workflow to include tasks like validate email addresses, perform a credit check, assign a sales representative etc.
		+
		+	===Workflow Components===
		+
		+	====Nodes and Transitions====
		+
		+	A Compiere Workflow is composed of one or more Nodes (Steps). Each Node can have the following Actions:
		+
		+	* Automatic Process – Any Process, Report, Task, Workflow, Document Action,
		+	* User Action – Any Window, Form - User needs to confirm Completion
		+	* Set Variable – Any Column to Constant or Variable
		+	* User Choice – Any Choice (e.g. approval), List selection
		+	* Wait (Sleep) – can also be used for Start/End/etc.
		+
		+	Transition between nodes can optionally have conditions. In addition, you can specify multiple transitions, each of which can be processed sequentially or in parallel.
		+
		+	====Approvals====
		+
		+	Compiere lets you specify a workflow-specific approval hierarchy or it can utilize the organization hierarchy defined in the system.
		+
		+	The entity responsible for a workflow can be an individual, a group, or an organization. Different individuals can be responsible for different nodes/steps in a workflow.
		+
		+	====Priority, Escalation and Alerts====
		+
		+	Compiere provides dynamic priority management, allowing you to use the workflow engine for call center routing and priority based customer support.
		+
		+	You can define escalation rules (based on inactivity, for example) and send alerts to the workflow responsible and/or the supervisor.
		+
		+	The Compiere Workflow Engine is also Compiere's core transaction management system. That means that all processes in Compiere are automatically workflow enabled and thus are easy to extend and modify.

@@ Line 48: / Line 48: @@
 There are three types of workflows in Compiere:
-* Steps/Guidance Workflows,
+* Steps/Guidance or General Workflows,
 * Document Process Workflows and
-* Record Value Workflows.
+* Record/Document Value Workflows.
 Each serves a different need and each can be easily extended (or you can create your own).
 ====Steps/Guidance Workflow====
-Steps/Guidance Workflows are the most basic and general. They are invoked by the user by selecting one of the Workflows in the Menu. They are indicated in the Menu by the footprints. It allows you to define a list or process of steps that should be completed to accomplish a specific task. In Compiere these Workflows have been defined for Defining a new Language, Setting up a Business Partner, among others. You can easily add any specific steps you require to these existing Workflows, or you can create your own to document your month or year end closing process (for example). These Workflows impose no restrictions or limitations. The user is not forced to complete each step or to complete each step in a particular order. Its purpose is to guide or assist a user in a new or infrequently performed task. These Workflows can also include steps outside of Compiere.
+Steps/Guidance or '''General Workflows''' are the most basic. They are invoked by the user by selecting one of the Workflows in the Menu. They are indicated in the Menu by the footprints. It allows you to define a list or process of steps that should be completed to accomplish a specific task. In Compiere these Workflows have been defined for Defining a new Language, Setting up a Business Partner, among others. You can easily add any specific steps you require to these existing Workflows, or you can create your own to document your month or year end closing process (for example). These Workflows impose no restrictions or limitations. The user is not forced to complete each step or to complete each step in a particular order. Its purpose is to guide or assist a user in a new or infrequently performed task. These Workflows can also include steps outside of Compiere.
 ====Document Process Workflow====
@@ Line 61: / Line 61: @@
 ====Record Value Workflow====
-Record Value Workflows are invoked when a specific condition is met. This can be for a document or maintenance window. These are entirely user defined. An example of a Record Value Workflow can be found in GardenWorld. The Business Partner Approval Workflow is based on the Business Partner table. It is invoked whenever a new Business Partner is added. The condition is Created Date and UpdatedDate are equal as this condition would only resolve to true when a record is first added. A notice is sent to a supervisor. You could then extend this workflow to include tasks like validate email addresses, perform a credit check, assign a sales representative etc.
+Record or Document Value Workflows are invoked when a specific condition is met. This can be for a document or maintenance window. These are entirely user defined. An example of a Record Value Workflow can be found in GardenWorld. The Business Partner Approval Workflow is based on the Business Partner table. It is invoked whenever a new Business Partner is added. The condition is Created Date and UpdatedDate are equal as this condition would only resolve to true when a record is first added. A notice is sent to a supervisor. You could then extend this workflow to include tasks like validate email addresses, perform a credit check, assign a sales representative etc.

← Older revision		Revision as of 14:19, 23 April 2020
Line 39:		Line 39:

	==Contributions / Posts==		==Contributions / Posts==
		+	===Workflows in *piere===
		+	"*piere" means all [https://klst.gitbook.io/adempiere/ systems derive from compiere]. This is a copy of [https://www.compieresource.com/2008/03/workflows-in-compiere.html Post by Jorg Janke on 03/16/2008]
		+
		+	One of the ways in which Compiere is different from other applications is how it implemented and uses workflows. In many applications, any workflow engine is an afterthought. Therefore it can be used mainly for guiding users but not for any control purposes. In Compiere, the workflow engine is an integrated part of the application. This approach makes it relatively easy to create, modify and extend processes to address your specific needs and requirements.
		+
		+	Workflows can include tasks and operations within Compiere and external tasks as well. A Workflow can be used to send emails and notifications to internal and external parties and can be used to generate reports and do report bursting (sending reports to a list of recipients).
		+
		+	There are three types of workflows in Compiere:
		+
		+	* Steps/Guidance Workflows,
		+	* Document Process Workflows and
		+	* Record Value Workflows.
		+
		+	Each serves a different need and each can be easily extended (or you can create your own).
		+
		+	====Steps/Guidance Workflow====
		+	Steps/Guidance Workflows are the most basic and general. They are invoked by the user by selecting one of the Workflows in the Menu. They are indicated in the Menu by the footprints. It allows you to define a list or process of steps that should be completed to accomplish a specific task. In Compiere these Workflows have been defined for Defining a new Language, Setting up a Business Partner, among others. You can easily add any specific steps you require to these existing Workflows, or you can create your own to document your month or year end closing process (for example). These Workflows impose no restrictions or limitations. The user is not forced to complete each step or to complete each step in a particular order. Its purpose is to guide or assist a user in a new or infrequently performed task. These Workflows can also include steps outside of Compiere.
		+
		+	====Document Process Workflow====
		+	Document Process Workflows are invoked when a user selects the Document Action button (e.g. Complete, Prepare, Close) on any document. There are four standard nodes which should not be edited, but you can introduce additional nodes to alter the processing. The typical example is to add an approval step to the Purchase Order Workflow to require a supervisor approval for Purchase Orders over $500.00. With the Compiere Workflow design, this is done by adding data (no code) and the modifications would be preserved when upgrading to a new release.
		+
		+	====Record Value Workflow====
		+	Record Value Workflows are invoked when a specific condition is met. This can be for a document or maintenance window. These are entirely user defined. An example of a Record Value Workflow can be found in GardenWorld. The Business Partner Approval Workflow is based on the Business Partner table. It is invoked whenever a new Business Partner is added. The condition is Created Date and UpdatedDate are equal as this condition would only resolve to true when a record is first added. A notice is sent to a supervisor. You could then extend this workflow to include tasks like validate email addresses, perform a credit check, assign a sales representative etc.

← Older revision		Revision as of 13:32, 17 November 2017
Line 1:		Line 1:
		+	<!-- breadcrumb -->
		+	<font size=-2>
		+	⇐
		+	[[Manual\|Table of Contents]]
		+	</font>
		+
		+	[[Category:Manual\|W]]
		+
	[[en:Workflow (Window ID-113)]]		[[en:Workflow (Window ID-113)]]
	[[ar:Workflow (نافذة ID-113)]]		[[ar:Workflow (نافذة ID-113)]]

← Older revision		Revision as of 16:36, 15 November 2017
Line 1:		Line 1:
		+	[[en:Workflow (Window ID-113)]]
		+	[[ar:Workflow (نافذة ID-113)]]
		+	[[bg:Работен процес (прозорец ID-113)]]
		+	[[da:Workflow (Vindue ID-113)]]
		+	[[de:Workflow (Fenster ID-113)]]
		+	[[el:Ροή Εργασιών (παράθυρο ID-113)]]
		+	[[es:Flujo de Trabajo (Ventana ID-113)]]
		+	[[fr:Workflow (Fenêtre ID-113)]]
		+	[[hu:Munkafolyamat (Aablak ID-113)]]
		+	[[id:Alur Kerja (jendela ID-113)]]
		+	[[it:Workflow (finestra ID-113)]]
		+	[[ja:作業フロー (ウィンドウ ID-113)]]
		+	[[ms:Aliran Kerja (tetingkap ID-113)]]
		+	[[nl:Workflow (Venster ID-113)]]
		+	[[pl:Workflow (Okno ID-113)]]
		+	[[pt:Workflow (Janela ID-113)]]
		+	[[ro:Flux (fereastră ID-113)]]
		+	[[ru:Workflow (окно ID-113)]]
		+	[[sr:Радни ток (прозор ID-113)]]
		+	[[sv:Arbetsflöde (Fönster ID-113)]]
		+	[[th:เวิร์คโฟล (หน้าต่าง ID-113)]]
		+	[[tr:Workflow (pencere ID-113)]]
		+	[[zh:工作流 (窗口 ID-113)]]

	<!-- Note to editors: DON'T MODIFY THIS CODE -->		<!-- Note to editors: DON'T MODIFY THIS CODE -->