What steps need to be followed in order to build a workflow capability into an existing business process using Skelta Workflow.NET 2004?
Skelta Workflow.NET 2004 is a workflow management tool that can be integrated to your existing application, as you have seen in the sample leave application, the starting point for the workflow has to come from the application (when leave submission happens). Please follow the instructions given below to add the workflow capability: 1) Skelta Workflow.NET itself provides an option called ActivityList for the actions which need User Interaction (Example: Approval or Task) 2) But the Application View from where Skelta Workflow.NET 2004 starts has to be developed in the application (Leave Submission Form). 3) Once the form is submitted, the workflow is alerted about the start. From that point onwards, the flow is taken care of by the workflow. The approval options assigned to the resource is displayed in the ActivityList for that resource. (ActivityList needs to be integrated to the existing application as in the sample) 4) Built-in Action Handlers act as the controller. The decision (App
Related Questions
- What steps need to be followed in order to build a workflow capability into an existing business process using Skelta Workflow.NET?
- If a developer wants to build a rental project using Low-Income Housing Tax Credits, what steps should be followed?
- How will document conversion affect the business and workflow process?
