This section dwells on the objects a process scheme comprises, as well as the major methods of working with the process. The key scheme objects are Activities which may set process states and the order of the executed user code determined by Actions. Transitions determine the order of process execution. Commands and Timers are key triggers that make a process change its state and do effective work. Integration with the security system and control of user access to commands is done with the help of the Rule-Actor-Restriction.
In general, you can edit a process scheme in Designer. Designer consists of a toolbar and an object graph. Designer enables you to select objects with a frame and move them with the pressed left mouse button. An object can be selected by clicking on it with the left mouse button. The properties of Activity or Transitions can be accessed by double clicking on the object.
Activity object represents a rectangle with the following control components:
Transition object represents a line with the following control components:
The rest of the components are contained in the toolbar (from left to right):
Workflow Engine comprises lots of objects, but to understand this documentation section, you just need to be aware of the following three:
WorkflowRuntime- we mentioned it earlier; it provides API for working with processes;
ProcessInstance- process instance; it provides access to the process scheme and parameters;
ProcessDefinition- object representation of a process scheme.
The following code demonstrates how the three objects interrelate:
var processInstance = WorkflowInit.Runtime.GetProcessInstanceAndFillProcessParameters(processId); var processDefinition = processInstance.ProcesScheme;