The main feature of any workflow engine is tracking the histories of transactions for its process flows, normally all workflow engines will support for this feature but when you want track the custom history for a process flow like Approval history (approver, result, date, role, department and comments) then you need to dig your own logic based on your workflow engine. Normally history is collection log user or actor action of activities of a process...

Skelta provides the feature to initiate a workflow from a Skelta form by associating it. In Skelta Enterprise Console they given the provision to fill the form and submit it but this form fill page has own fence i.e Top level form only display here if you created workflow initiator form under a folder it will not display here and mainly they are not documented how to render the form fill page and initiate the workflow or provided as component, so we need to create our own Form fill page for workflow...

In Skelta BPM.Net 2009 they introduced dynamic form, we can design our required dynamic forms and attach with workflow in form of Invoke Form activity, it is very nice feature from Skelta but it has own fence. Here we have two types of forms one is workflow initiator form and another one is normal action forms, even we have two types based on whether the form created on Skelta List(Form mapper to table) or not.This section explains about how to render an action form (custom ASPX web form for Invoke...