Do I need to retain the set of tables that the Skelta Workflow.NET Engine u ses?
Details like the Workflow designed, actions to be executed, the different properties set for each action etc., are stored in Workflow.NET engine related tables. So these tables have to be retained. • I see that when I submit the request for leave, then the Engine will automatically update certain tables. How will I handle this for my process? Skelta Workflow.NET Supports Custom Actions to be built and integarted to the workflow being built; these Custom actions can have application specific updation. • Using Skelta with WinForms Skelta Workflow.NET controls are web server controls which can be dragged and dropped on to ASPX pages. These controls can be used in WinForms by loading the web pages in WinForms. • How can total control of the presentation layer, from an application development point of view, be achieved? The Workflow.NET uses HTML templates for the presentation. These HTML templates use place holders for displaying the data. The developer can completely customize the HTML te
Related Questions
- Does Skelta Workflow.NET 2004 have the ability to integrate with / pull data from (SUN) LDAP directory for user data - i.e., allow for custom implementation of a user data source?
- Does Skelta Workflow.NET 2004 rely on any external components for backend data sources?
- Do I need to retain the set of tables that Skelta BPM.NET Engine uses?
