You will find the answers to some of the frequently asked questions about different features and functionalities of Skelta Workflow.NET here. You can refer to this section to see if you can find answers to your queries. The questions are organized into groups based on the feature or functionality that they address.

Process Designer Questions

1. How can Business Users model Business Processes using graphical Designer for developer implementation?
2. How can the controls retrieve and submit data from a running process?
3. Can we store workflow designs as templates to be used to create other workflows?

Engine Questions

1. Is there functionality to add escalation and alerts
2. Do we have programmatic control over what will happen in the event of an escalation - i.e., can we execute our own assembly/code at this point?
3. I am not receiving notification emails
4. Can we define our own authentication class (preferably an interface or abstract class)?
5. How can you check if any errors occurred during the Workflow execution? How are errors handled?
6. What steps need to be followed in order to build a workflow capability into an existing business process using Skelta Workflow.NET?

Database Questions

1. Does Skelta Workflow.NET have the ability to integrate with our own existing user database (LDAP SUN) for interaction with workflow tasks? This would preferably be in the form of an interface/abstract class which we would extend/provide our own implementation for.
2. Does Skelta Workflow.NET rely on any external components for back end data sources?
3. Does Skelta Workflow.NET 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?
4. Is there a fail-safe mechanism for back up and recovery of process state data (SQL SERVER backups)?
5. Is there a backend data layer based on SQL Server that can be backed up regularly?
6. Can Skelta Workflow.NET 2004 function without a database?

Admin Questions

1. How can administrators handle the monitoring and administration of workflows in Skelta?
2. What options are available to handle workflow tasks that are overdue from the currently assigned task owner? Is there a provision to reassign the task to a new user or apply alerts/escalation methods?
3. Can I access administration functionality through framework (API)?
4. Is it possible to query running/completed process data through API or directly through Database Queries?
5. How is process data stored in the Database? Is it in a form that allows querying?

Appearance (Web UI related) Questions

1. Are the Skelta Web User Interfaces reusable, i.e., can forms be built once and re-used in either editable or read-only views to capture and/or display information?
2. Does Skelta Workflow.NET provide total control over the presentation layer, i.e., does it have a set of controls that allow us to easily build UI's that allow user's to add/view/modify workflow data items?
3. Can we implement our UI as ASP.NET pages? Can we add our own control logic for the UI?
4. Will we be able to hide all branding of the underlying workflow engine, especially in the workflow designer which will be presented to the end user as an application front end?

API Questions

1. Does Skelta Workflow.NET have a robust framework (API) for interacting with a Business Access to Process Data - user input process?
2. Can any other functionality be accessed through the API, i.e., re-assigning workflow items (tasks) to different users, redirecting workflow down a different path etc?
3. Is there a robust and complete API that allows programmatic access to all of the workflow administration functions in Skelta Workflow.NET?
4. Can we submit approval, rejection or acceptance to the workflow engine through an API?

Miscellaneous Questions

1. Do I need to retain the set of tables that the Skelta Workflow.NET Engine uses?
2. 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?
   
3. Using Skelta with WinForms
   
4. How can total control of the presentation layer, from an application development point of view, be achieved?
5. Can documents be attached to a process?
6. Is it possible to authenticate or 'digitally sign' data and/or integrate with NT 2000 domain authentication / Active directory? Also is it possible to have Web UI's incorporating SSL?
7. Is it possible to access Current Task Data, i.e., Task responses?
8. Is it possible to call custom assemblies to implement server-side processes?
9. Is it possible to call our own custom .NET assemblies to implement server side code
10. What is the User Id? Can it be associated with our own LDAP directory?
11. Does Skelta Workflow.NET have the ability to query the system (through a UI) and programmatically find a running process based on information contained in that process, i.e., where Data Item ("Name") = "Fred smith"?
12. What error handling options are available in Skelta Workflow.NET 2004?
13. What do you mean by the term 'concurrent workflows'? Can you illustrate it with an appropriate example?