Workflow Responsible (Venster ID-299)
Venster: Workflow Responsible
Beschrijving: Responsible for Workflow Execution
Help: The ultimate responsibility for a workflow is with an actual user. The Workflow Responsible allows to define ways to find that actual User.
TAB: Responsible
Beschrijving: Responsible for Workflow Execution
Help The ultimate responsibility for a workflow is with an actual user. The Workflow Responsible allows to define ways to find that actual User.
Bestand:Workflow Responsible - Responsible - Venster (iDempiere 1.0.0).png
Naam | Naam | Beschrijving | Help | Specificaties |
---|---|---|---|---|
Workflow Responsible | 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_Responsible_ID numeric(10) NOT NULL ID |
Client | Client | Client/Tenant for this installation. | A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. | AD_Client_ID numeric(10) NOT NULL Table Direct |
Organization | Organization | Organizational entity within client | An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. | AD_Org_ID numeric(10) NOT NULL Table Direct |
Name | 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. | Name character varying(60) NOT NULL String |
Description | Beschrijving | Optional short description of the record | A description is limited to 255 characters. | Description character varying(255) String |
Active | Actief | 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. |
IsActive character(1) NOT NULL Yes-No |
Entity Type | Entity Type | Dictionary Entity Type; Determines ownership and synchronization | The Entity Types "Dictionary", "Adempiere" and "Application" might be automatically synchronized and customizations deleted or overwritten.
For customizations, copy the entity and select "User"! |
EntityType character varying(40) NOT NULL Table |
Responsible Type | Responsible Type | Type of the Responsibility for a workflow | Type how the responsible user for the execution of a workflow is determined | ResponsibleType character(1) NOT NULL List |
Role | Role | Responsibility Role | The Role determines security and access a user who has this Role will have in the System. | AD_Role_ID numeric(10) Table Direct |
User/Contact | User/Contact | User within the system - Internal or Business Partner Contact | The User identifies a unique user in the system. This could be an internal user or a business partner contact | AD_User_ID numeric(10) Search |