When a process is generated, several elements are implanted in the VDoc database. From these definition elements we will keep the following:
Diagram of definition elements classes
This classes diagram represents the main relations that exist between every classes of the process system.
Table of definition elements correspondence
Functional term | Technical term | SDK term | EJB term (prefix:ejb/com/axemble/vdp/) | Description |
Application | Catalog | ICatalog | Catalog | An application is a group of processes and associated documents. |
Resource template | Resource template | IResourceDefinition | Resource template | |
Field,property | Property | IProperty | Property | Element constituting the description of a value supported by the document. |
Process | Process version group | IWorkflowContainer | VersionGroup | Group of process versions which share properties,views and roles. |
Process version,workflow | Process version | IWorkflow | TreatmentClass | A process is the modelling of the document path through multiple stages. It can also call sub-processes. |
Task, stage | Step | ITask | Stage | A task is the modeled object identifying a process stage. |
Workflow action,user action,routing action | Routing actions | IAction | TransitionInlet | User action to leave a step. |
Role | Role | IRole | Role | This is a group of users and groups. It can be associated to a set of common permissions or rights for an application, process,version,view. |
When a document is creating, several elements are registered in the database. Among these elements we will keep the following:
Diagram of dynamic elements classes
Table of dynamic elements correspondence
Functional term | Technical term | SDK term | EJB term (prefix:ejb/com/axemble/vdp/) | Description |
Resource | Resource | IResource | Resource | The term "Resource" represents the data container. It lets you store all the user data. |
Request,Document | Treatment | IWorkflowInstance | Treatment | The notion of document has changed a lot in VDoc. It defines a resource and the set of associated treatments and sub-treatments. |
Table line | Internal resource | ILinkedResource | Resource | This resource represents a resource type dynamic table line. |
Task to process | Activity, manual activity | ITaskInstance | Activity, manual activity | An activity represents an operation to be performed by a person or a program.A manual activity can be of two kind: Action or Decision. |
History | History | IResourceHistory | Document history. | |
History row | User event | IEvent | Document history row corresponding to a user action. | |
Attachment,file | File wrapper | IAttachment | Structure FileInfo or TempUploadFile | Attached file description in the document via a attachment field. |
Task to process | User activity | IOperator | UsersActivity | This is an association between a person and a manual activity. There should be as many users created as potential contributors determined for a task. |
Linked requests,linked documents,sub-processes | Linked treatment | IWorkflowInstance | Treatment | This treatment represents a treatment type dynamic table line. |