Abstract: Embodiments provide a checklist function integrated with a process flow model. The process checklist utilizes a semi-automated visual approach to cover processes specific to a user and/or enterprise. A model of the process is generated and stored, for example utilizing an input template in XML format and according to the Business Process Model and Notation (BPMN) standard. Next, instances corresponding to runs of the mapped processes are created. Various internal documents can be linked together within a process instance, thereby allowing enterprises to define different relationships between documents independent of product-wide implementation and database complexity. In some embodiments the process models may be accessed interactively in a What-You-See-Is-What-You-Get manner, without being machine executed. This allows for relatively loose process definition/modelling, fostering interpretation reliant upon user intuition.

Abstract: Embodiments provide a checklist function integrated with a process flow model. The process checklist utilizes a semi-automated visual approach to cover processes specific to a user and/or enterprise. A model of the process is generated and stored, for example utilizing an input template in XML format and according to the Business Process Model and Notation (BPMN) standard. Next, instances corresponding to runs of the mapped processes are created. Various internal documents can be linked together within a process instance, thereby allowing enterprises to define different relationships between documents independent of product-wide implementation and database complexity. In some embodiments the process models may be accessed interactively in a What-You-See-Is-What-You-Get manner, without being machine executed. This allows for relatively loose process definition/modelling, fostering interpretation reliant upon user intuition.