Workflow Engine.NET v1.5 and v2.3
Add a new workflow functionality. More flexibility in settings. Get transparent and predictable development results! WorkflowEngine.NET is a component that adds workflow functionality to your application. It can be fully integrated with the application, or be implemented as a specific stand-alone service (such as a web service).
The benefits of using WorkflowEngine.NET:
Code-free process scheme design in a web-browser (HTML5)
Add a custom workflow to your project. As easy as a pie!
Autogenerate incoming list
Change the scheme process in real-time
Database providers: MS SQL Server, MongoDB, RavenDB, Oracle, MySQL, PostgreSQL.
8 steps to a process scheme creation
Create Actors, Command, and Timers.
Create the first Activity marked as “Initial”.
Create Activities, in which the document can move from the current Activity. Link the current and new Activities with the help of Transitions.
For each new Activity indicate:
4.1. In the State field - the name of a document’s status.
4.2. If the status can be forcefully moved into a particular state, then check the box “For set state.”
4.3. If a scheme may be updated in this Activity, then check the box “Auto scheme update.”
4.4. Fill in the Action calls in the boxes “Implementation” and “Pre-ExecutionImplementation.” Methods from the “Implementation” box will be called, when the document moves to a respective Activity (in “Pre-Execute” mode, methods from the “Pre-Execution Implementation” box will be called). If you use the constructor functionality to build a concordance history, then you need to add the appropriate methods in the data blocks (in our example, these are UpdateTransitionHistory and WriteTransitionHistory, respectively).
For each new Transition:
5.1. Indicate the value of the Classifier. Use “Direct” or “Reverse” for direct or reverse Transitions, respectively.
5.2. In the “Restrictions” block, indicate Actors with access rights for this Transition. When several Conditions are indicated, they are grouped by AND. This function is available for Trigger type equal Command.
5.3. In the “Triggers” block, indicate the type of operation (as per p. 3.5) that initiates a Transition.
5.4. In the “Condition” block, indicate the type of Condition (as per p. 3.5) that helps define the possibility of a Transition and choose an appropriate Transition Type.
If each new Activity contains possible Transitions, repeat pp. 3–6 for each Activity. If these Activities are final, mark them as “Final.”
Create Parameters and indicate them in the appropriate Commands.