Workflow (Window ID-113)
Window: Workflow
Description: Maintain Workflow
Help: The Workflow Window defines Workflows in the system, the access level for the Workflow and the Nodes or Steps within the Workflow.
Tab: Workflow
Description: Define Workflow
Help: The Workflow Tab defines Workflows in the system.
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_Workflow.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_Workflow.AD_Org_ID numeric(10) Table Direct |
| Search Key | Search key for the record in the format required - must be unique | A search key allows you a fast method of finding a particular record.
If you leave the search key empty, the system automatically creates a numeric number. The document sequence used for this fallback number is defined in the "Maintain Sequence" window with the name "DocumentNo_<TableName>", where TableName is the actual name of the table (e.g. C_Order). |
AD_Workflow.Value character varying(40) String |
| Name | Alphanumeric identifier of the entity | The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. | AD_Workflow.Name character varying(60) String |
| Description | Optional short description of the record | A description is limited to 255 characters. | AD_Workflow.Description character varying(255) String |
| Comment/Help | Comment or Hint | The Help field contains a hint, comment or help about the use of this item. | AD_Workflow.Help text Text |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_Workflow.IsActive character(1) Yes-No |
| Beta Functionality | This functionality is considered Beta | Beta functionality is not fully tested or completed. | AD_Workflow.IsBetaFunctionality character(1) Yes-No |
| Workflow Type | Type of Workflow | The type of workflow determines how the workflow is started. | AD_Workflow.WorkflowType character(1) List |
| Table | Database Table information | The Database Table provides the information of the table definition | AD_Workflow.AD_Table_ID numeric(10) Search |
| Document Value Logic | Logic to determine Workflow Start - If true, a workflow process is started for the document | You can enter simple logic using variables like @Created@=@Updated@, which fires, when a record is created. If you need to evaluate also values of other records, you need to use SQL logic and need to prefix this logic with "SQL=". Example: start a Order verify workflow, when a business partner ordered something and is over the credit limit "SQL=EXISTS (SELECT * FROM C_BPartner bp WHERE C_Order. C_BPartner_ID=bp. C_BPartner_ID AND SO_CreditUsed > SO_CreditLimit)".
Note that the SQL based logic checks for duplicate workflows (i.e. a workflow is started only once per record). |
AD_Workflow.DocValueLogic character varying(2000) String |
| Data Access Level | Access Level required | Indicates the access level required for this record or process. | AD_Workflow.AccessLevel character(1) List |
| Entity Type | Dictionary Entity Type; Determines ownership and synchronization | The Entity Types "Dictionary", "iDempiere" and "Application" might be automatically synchronized and customizations deleted or overwritten.
For customizations, copy the entity and select "User"! |
AD_Workflow.EntityType character varying(40) Table |
| Workflow Responsible | Responsible for Workflow Execution | The ultimate responsibility for a workflow is with an actual user. The Workflow Responsible allows to define ways to find that actual User. | AD_Workflow.AD_WF_Responsible_ID numeric(10) Table Direct |
| Priority | Indicates if this request is of a high, medium or low priority. | The Priority indicates the importance of this request. | AD_Workflow.Priority numeric(10) Integer |
| Valid from | Valid from including this date (first day) | The Valid From date indicates the first day of a date range | AD_Workflow.ValidFrom timestamp without time zone Date |
| Valid to | Valid to including this date (last day) | The Valid To date indicates the last day of a date range | AD_Workflow.ValidTo timestamp without time zone Date |
| Publication Status | Status of Publication | Used for internal documentation | AD_Workflow.PublishStatus character(1) List |
| Version | Version of the table definition | The Version indicates the version of this table definition. | AD_Workflow.Version numeric(10) Integer |
| Author | Author/Creator of the Entity | AD_Workflow.Author character varying(20) String | |
| Default | Default value | The Default Checkbox indicates if this record will be used as a default value. | AD_Workflow.IsDefault character(1) Yes-No |
| Start Node | Workflow Node, step or process | The Workflow Node indicates a unique step or process in a Workflow. | AD_Workflow.AD_WF_Node_ID numeric(10) Table Direct |
| Workflow Processor | Workflow Processor Server | Workflow Processor Server | AD_Workflow.AD_WorkflowProcessor_ID numeric(10) Table Direct |
| Duration Unit | Unit of Duration | Unit to define the length of time for the execution | AD_Workflow.DurationUnit character(1) List |
| Duration Limit | Maximum Duration in Duration Unit | Maximum (critical) Duration for time management purposes (e.g. starting an escalation procedure, etc.) in Duration Units. | AD_Workflow.Limit numeric(10) Integer |
| Duration | Normal Duration in Duration Unit | Expected (normal) Length of time for the execution | AD_Workflow.Duration numeric(10) Integer |
| Cost | Cost information | AD_Workflow.Cost numeric Costs+Prices | |
| Working Time | Workflow Simulation Execution Time | Amount of time the performer of the activity needs to perform the task in Duration Unit | AD_Workflow.WorkingTime numeric(10) Integer |
| Waiting Time | Workflow Simulation Waiting time | Amount of time needed to prepare the performance of the task on Duration Units | AD_Workflow.WaitingTime numeric(10) Integer |
| Context Help | AD_Workflow.AD_CtxHelp_ID numeric(10) Search | ||
| Validate Workflow | Validate that the workflow is correct | (limited checking) | AD_Workflow.ValidateWorkflow character(1) Button |
| Valid | Element is valid | The element passed the validation check | AD_Workflow.IsValid character(1) Yes-No |
Tab: Node
Description: Define workflow nodes
Help: The Node Tab defines each Node, Activity or step in this Workflow.
The action (activity) type determines the execution: "Route" may be used in routing control conditions. "None" identifies manual execution.
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_WF_Node.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_WF_Node.AD_Org_ID numeric(10) Table Direct |
| Workflow | Workflow or combination of tasks | The Workflow field identifies a unique Workflow in the system. | AD_WF_Node.AD_Workflow_ID numeric(10) Table Direct |
| Search Key | Search key for the record in the format required - must be unique | A search key allows you a fast method of finding a particular record.
If you leave the search key empty, the system automatically creates a numeric number. The document sequence used for this fallback number is defined in the "Maintain Sequence" window with the name "DocumentNo_<TableName>", where TableName is the actual name of the table (e.g. C_Order). |
AD_WF_Node.Value character varying(40) String |
| Name | Alphanumeric identifier of the entity | The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. | AD_WF_Node.Name character varying(60) String |
| Description | Optional short description of the record | A description is limited to 255 characters. | AD_WF_Node.Description character varying(255) String |
| Comment/Help | Comment or Hint | The Help field contains a hint, comment or help about the use of this item. | AD_WF_Node.Help text Text |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_WF_Node.IsActive character(1) Yes-No |
| Centrally maintained | Information maintained in System Element table | The Centrally Maintained checkbox indicates if the Name, Description and Help maintained in 'System Element' table or 'Window' table. | AD_WF_Node.IsCentrallyMaintained character(1) Yes-No |
| Entity Type | Dictionary Entity Type; Determines ownership and synchronization | The Entity Types "Dictionary", "iDempiere" and "Application" might be automatically synchronized and customizations deleted or overwritten.
For customizations, copy the entity and select "User"! |
AD_WF_Node.EntityType character varying(40) Table |
| Workflow Responsible | Responsible for Workflow Execution | The ultimate responsibility for a workflow is with an actual user. The Workflow Responsible allows to define ways to find that actual User. | AD_WF_Node.AD_WF_Responsible_ID numeric(10) Table Direct |
| Priority | Indicates if this request is of a high, medium or low priority. | The Priority indicates the importance of this request. | AD_WF_Node.Priority numeric(10) Integer |
| Start Mode | Workflow Activity Start Mode | How is the execution of an activity triggered. Automatic are triggered implicitly by the system, Manual explicitly by the User. | AD_WF_Node.StartMode character(1) List |
| Finish Mode | Workflow Activity Finish Mode | How the system operated at the end of an activity. Automatic implies return when the invoked applications finished control - Manual the user has to explicitly terminate the activity. | AD_WF_Node.FinishMode character(1) List |
| Join Element | Semantics for multiple incoming Transitions | Semantics for multiple incoming Transitions for a Node/Activity. AND joins all concurrent threads - XOR requires one thread (no synchronization). | AD_WF_Node.JoinElement character(1) List |
| Split Element | Semantics for multiple outgoing Transitions | Semantics for multiple outgoing Transitions for a Node/Activity. AND represents multiple concurrent threads - XOR represents the first transition with a true Transition condition. | AD_WF_Node.SplitElement character(1) List |
| Action | Indicates the Action to be performed | The Action field is a drop down list box which indicates the Action to be performed for this Item. | AD_WF_Node.Action character(1) List |
| Image | Image or Icon | Images and Icon can be used to display supported graphic formats (gif, jpg, png).
You can either load the image (in the database) or point to a graphic via a URI (i.e. it can point to a resource, http address) |
AD_WF_Node.AD_Image_ID numeric(10) Table Direct |
| Info Window | Info and search/select Window | The Info window is used to search and select records as well as display information relevant to the selection. | AD_WF_Node.AD_InfoWindow_ID numeric(10) Table Direct |
| Window | Data entry or display window | The Window field identifies a unique Window in the system. | AD_WF_Node.AD_Window_ID numeric(10) Table Direct |
| Special Form | Special Form | The Special Form field identifies a unique Special Form in the system. | AD_WF_Node.AD_Form_ID numeric(10) Table Direct |
| Column | Column in the table | Link to the database column of the table | AD_WF_Node.AD_Column_ID numeric(10) Table Direct |
| Attribute Name | Name of the Attribute | Identifier of the attribute | AD_WF_Node.AttributeName character varying(60) String |
| Attribute Value | Value of the Attribute | iDempiere converts the (string) field values to the attribute data type. Booleans (Yes-No) may have the values "true" and "false", the date format is YYYY-MM-DD | AD_WF_Node.AttributeValue character varying(60) String |
| EMail Recipient | Recipient of the EMail | AD_WF_Node.EMailRecipient character(1) List | |
| EMail Address | Electronic Mail Address | The Email Address is the Electronic Mail ID for this User and should be fully qualified (e.g. joe.smith@company.com). The Email Address is used to access the self service application functionality from the web. | AD_WF_Node.EMail character varying(60) String |
| Attached Document | Attached document to Email | AD_WF_Node.IsAttachedDocumentToEmail character(1) Yes-No | |
| Mail Template | Text templates for mailings | The Mail Template indicates the mail template for return messages. Mail text can include variables. The priority of parsing is User/Contact, Business Partner and then the underlying business object (like Request, Dunning, Workflow object). So, @Name@ would resolve into the User name (if user is defined defined), then Business Partner name (if business partner is defined) and then the Name of the business object if it has a Name. |
AD_WF_Node.R_MailText_ID numeric(10) Table Direct |
| Duration Limit | Maximum Duration in Duration Unit | Maximum (critical) Duration for time management purposes (e.g. starting an escalation procedure, etc.) in Duration Units. | AD_WF_Node.Limit numeric(10) Integer |
| OS Task | Operation System Task | The Task field identifies a Operation System Task in the system. | AD_WF_Node.AD_Task_ID numeric(10) Table Direct |
| Workflow | Workflow or tasks | The Workflow field identifies a unique workflow. A workflow is a grouping of related tasks, in a specified sequence and optionally including approvals | AD_WF_Node.Workflow_ID numeric(10) Table |
| Subflow Execution | Mode how the sub-workflow is executed | AD_WF_Node.SubflowExecution character(1) List | |
| Process | Process or Report | The Process field identifies a unique Process or Report in the system. | AD_WF_Node.AD_Process_ID numeric(10) Table Direct |
| Document Action | The targeted status of the document | You find the current status in the Document Status field. The options are listed in a popup | AD_WF_Node.DocAction character(2) List |
| Wait Time | Time in minutes to wait (sleep) | Time in minutes to be suspended (sleep). A value of -1 means to wait and execute after the commit of the workflow transaction. | AD_WF_Node.WaitTime numeric(10) Integer |
| Dynamic Priority Unit | Change of priority when Activity is suspended waiting for user | Starting with the Process / Node priority level, the priority of the suspended activity can be changed dynamically. Example +5 every 10 minutes | AD_WF_Node.DynPriorityUnit character(1) List |
| Dynamic Priority Change | Change of priority when Activity is suspended waiting for user | Starting with the Process / Node priority level, the priority of the suspended activity can be changed dynamically. Example +5 every 10 minutes | AD_WF_Node.DynPriorityChange numeric Number |
| Duration | Normal Duration in Duration Unit | Expected (normal) Length of time for the execution | AD_WF_Node.Duration numeric(10) Integer |
| Cost | Cost information | AD_WF_Node.Cost numeric Costs+Prices | |
| Working Time | Workflow Simulation Execution Time | Amount of time the performer of the activity needs to perform the task in Duration Unit | AD_WF_Node.WorkingTime numeric(10) Integer |
| Waiting Time | Workflow Simulation Waiting time | Amount of time needed to prepare the performance of the task on Duration Units | AD_WF_Node.WaitingTime numeric(10) Integer |
| Context Help | AD_WF_Node.AD_CtxHelp_ID numeric(10) Search |
Tab: Parameter
Description: Workflow Node Parameter
Help: Parameter for the execution of the Workflow Node
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_WF_Node_Para.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_WF_Node_Para.AD_Org_ID numeric(10) Table Direct |
| Node | Workflow Node (activity), step or process | The Workflow Node indicates a unique step or process in a Workflow. | AD_WF_Node_Para.AD_WF_Node_ID numeric(10) Table Direct |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_WF_Node_Para.IsActive character(1) Yes-No |
| Process Parameter | AD_WF_Node_Para.AD_Process_Para_ID numeric(10) Table Direct | ||
| Attribute Name | Name of the Attribute | Identifier of the attribute | AD_WF_Node_Para.AttributeName character varying(60) String |
| Attribute Value | Value of the Attribute | iDempiere converts the (string) field values to the attribute data type. Booleans (Yes-No) may have the values "true" and "false", the date format is YYYY-MM-DD | AD_WF_Node_Para.AttributeValue character varying(60) String |
| Description | Optional short description of the record | A description is limited to 255 characters. | AD_WF_Node_Para.Description character varying(255) String |
| Entity Type | Dictionary Entity Type; Determines ownership and synchronization | The Entity Types "Dictionary", "iDempiere" and "Application" might be automatically synchronized and customizations deleted or overwritten.
For customizations, copy the entity and select "User"! |
AD_WF_Node_Para.EntityType character varying(40) Table |
Tab: Node Translation
Description: Node Translation
Help:
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_WF_Node_Trl.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_WF_Node_Trl.AD_Org_ID numeric(10) Table Direct |
| Node | Workflow Node (activity), step or process | The Workflow Node indicates a unique step or process in a Workflow. | AD_WF_Node_Trl.AD_WF_Node_ID numeric(10) Table Direct |
| Language | Language for this entity | The Language identifies the language to use for display and formatting | AD_WF_Node_Trl.AD_Language character varying(6) Table |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_WF_Node_Trl.IsActive character(1) Yes-No |
| Translated | This column is translated | The Translated checkbox indicates if this column is translated. | AD_WF_Node_Trl.IsTranslated character(1) Yes-No |
| Name | Alphanumeric identifier of the entity | The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. | AD_WF_Node_Trl.Name character varying(60) String |
| Description | Optional short description of the record | A description is limited to 255 characters. | AD_WF_Node_Trl.Description character varying(255) String |
| Comment/Help | Comment or Hint | The Help field contains a hint, comment or help about the use of this item. | AD_WF_Node_Trl.Help text Text |
Tab: Transition
Description: Workflow Node Transition
Help: The Next Nodes Tab defines the order or Nodes or Steps in a Workflow.
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_WF_NodeNext.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_WF_NodeNext.AD_Org_ID numeric(10) Table Direct |
| Node | Workflow Node (activity), step or process | The Workflow Node indicates a unique step or process in a Workflow. | AD_WF_NodeNext.AD_WF_Node_ID numeric(10) Table Direct |
| Next Node | Next Node in workflow | The Next Node indicates the next step or task in this Workflow. | AD_WF_NodeNext.AD_WF_Next_ID numeric(10) Table |
| Sequence | Method of ordering records; lowest number comes first | The Sequence indicates the order of records | AD_WF_NodeNext.SeqNo numeric(10) Integer |
| Description | Optional short description of the record | A description is limited to 255 characters. | AD_WF_NodeNext.Description character varying(255) String |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_WF_NodeNext.IsActive character(1) Yes-No |
| Std User Workflow | Standard Manual User Approval Workflow | If selected, only documents with an open status (drafted, in progress, approved, rejected, invalid) and standard user actions (prepare, complete, approve, reject) are allowed to continue. Use this to prevent having to define details on how automatic processes (unlock, invalidate, post, re-activate) and when the document is closed for normal user action (completed, waiting, closed, voided, reversed). | AD_WF_NodeNext.IsStdUserWorkflow character(1) Yes-No |
| Entity Type | Dictionary Entity Type; Determines ownership and synchronization | The Entity Types "Dictionary", "iDempiere" and "Application" might be automatically synchronized and customizations deleted or overwritten.
For customizations, copy the entity and select "User"! |
AD_WF_NodeNext.EntityType character varying(40) Table |
Tab: Condition
Description: Workflow Node Transition Condition
Help: Optional restriction of transition of one node to the next. The (string) value is converted to the datatype. Booleans (Yes-No) are represented by "true" and "false", the date format is YYYY-mm-DD
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_WF_NextCondition.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_WF_NextCondition.AD_Org_ID numeric(10) Table Direct |
| Node Transition | Workflow Node Transition | The Next Nodes Tab defines the order or Nodes or Steps in a Workflow. | AD_WF_NextCondition.AD_WF_NodeNext_ID numeric(10) Table Direct |
| Sequence | Method of ordering records; lowest number comes first | The Sequence indicates the order of records | AD_WF_NextCondition.SeqNo numeric(10) Integer |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_WF_NextCondition.IsActive character(1) Yes-No |
| And/Or | Logical operation: AND or OR | AD_WF_NextCondition.AndOr character(1) List | |
| Operation | Compare Operation | AD_WF_NextCondition.Operation character(2) List | |
| Column | Column in the table | Link to the database column of the table | AD_WF_NextCondition.AD_Column_ID numeric(10) Table Direct |
| SQL Expression/Statement | AD_WF_NextCondition.SQLStatement character varying(4000) String | ||
| Value | Condition Value | AD_WF_NextCondition.Value character varying(40) String | |
| Value To | Value To | AD_WF_NextCondition.Value2 character varying(40) String | |
| Entity Type | Dictionary Entity Type; Determines ownership and synchronization | The Entity Types "Dictionary", "iDempiere" and "Application" might be automatically synchronized and customizations deleted or overwritten.
For customizations, copy the entity and select "User"! |
AD_WF_NextCondition.EntityType character varying(40) Table |
Tab: Workflow Translation
Description:
Help:
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_Workflow_Trl.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_Workflow_Trl.AD_Org_ID numeric(10) Table Direct |
| Workflow | Workflow or combination of tasks | The Workflow field identifies a unique Workflow in the system. | AD_Workflow_Trl.AD_Workflow_ID numeric(10) Table Direct |
| Language | Language for this entity | The Language identifies the language to use for display and formatting | AD_Workflow_Trl.AD_Language character varying(6) Table |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_Workflow_Trl.IsActive character(1) Yes-No |
| Translated | This column is translated | The Translated checkbox indicates if this column is translated. | AD_Workflow_Trl.IsTranslated character(1) Yes-No |
| Name | Alphanumeric identifier of the entity | The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. | AD_Workflow_Trl.Name character varying(60) String |
| Description | Optional short description of the record | A description is limited to 255 characters. | AD_Workflow_Trl.Description character varying(255) String |
| Comment/Help | Comment or Hint | The Help field contains a hint, comment or help about the use of this item. | AD_Workflow_Trl.Help text Text |
Tab: Access
Description: Workflow Access
Help: The Workflow Access Tab defines the Roles who have access to this Workflow.
.png)
| Name | Description | Help | Technical Data |
|---|---|---|---|
| Tenant | Tenant for this installation. | A Tenant is a company or a legal entity. You cannot share data between Tenants. | AD_Workflow_Access.AD_Client_ID numeric(10) Table Direct |
| Organization | Organizational entity within tenant | An organization is a unit of your tenant or legal entity - examples are store, department. You can share data between organizations. | AD_Workflow_Access.AD_Org_ID numeric(10) Table Direct |
| Workflow | Workflow or combination of tasks | The Workflow field identifies a unique Workflow in the system. | AD_Workflow_Access.AD_Workflow_ID numeric(10) Table Direct |
| Role | Responsibility Role | The Role determines security and access a user who has this Role will have in the System. | AD_Workflow_Access.AD_Role_ID numeric(10) Table Direct |
| Active | The record is active in the system | There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.
There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries. |
AD_Workflow_Access.IsActive character(1) Yes-No |
| Read Write | Field is read / write | The Read Write indicates that this field may be read and updated. | AD_Workflow_Access.IsReadWrite character(1) Yes-No |
Contributions / Posts
Workflows in *piere
"*piere" means all systems derive from compiere. This is a copy of 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 or General Workflows,
- Document Process Workflows and
- 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 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
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 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.
