This section provides a quick reference to the database tables used in Skelta Workflow.NET. This section also describes the procedure for using the database scripts to create the database tables.
To view the Skelta datbase structure, click here.
The different tables are described below:
|
Table |
Description |
|
This table stores information about the workflow, whenever a new workflow is created. |
|
|
This table stores information about the workflow design in the form of XML data, whenever a new workflow is created. |
|
|
This table stores information about the application name, workflow name, deployed version and workflow design after the workflow is deployed. |
|
|
This table stores information about the workflows that are executed. From this table, the total number of workflows that are instantiated can be determined. It also gives the execution status of the workflow like Finished (FN), Sleep Mode (SL), Execution Finished with Error (FE) etc. |
|
|
This table stores information about the actions, their links, status etc. that are involved in a particular execution. It may have resource dependant actions like Approval, Information, Checklist etc. or resource independent actions like Email, Script etc. This table has a collection of instances of actions that are triggered. |
|
|
This table stores information about the multiple timeout warnings sent to a resource, if the resource does not act upon the activity in his/her activity list within the specified time. |
|
|
This table stores the collection of actions that involves a resource to act on, that are triggered in a particular execution. |
|
|
This table stores information about the history of the resource actions and the status. For example, if 10 resources are involved in one workflow instance, then the statuses of all the resources’ actions will be stored in this table. |
|
|
This table stores information whenever an activity is forwarded from one resource (1) to another resource(2). After forwarding, the activity will be deleted from the activity list of resource (1). |
|
|
This table stores information like minimum and maximum number of persons required to acknowledge an action, approve an action and also time limit for acknowledging and time limit for warning to acknowledge. |
|
|
This table stores variables that are initialized in the workflow. |
|
|
This table stores the organization’s holiday details. The dates are selected by a resource in the Organization web control. These holidays are shown to the resources in their resource calendar. |
|
|
This table stores the organization’s shift details and the working hours of an organization. |
|
|
This table stores the organization’s week holiday details. The dates are selected by a resource in the Organization web control. |
|
|
This table stores a list of all resources in an application. |
|
|
This table stores the week holiday details of the resources. This is selected by the resource in his/her resource calendar web control in the activity list. |
|
|
This table stores the custom holiday details of the resources. This is selected by the resource in his/her resource calendar web control. These details are useful for redirecting the activity to the alternate resource. |
|
|
This table stores the shift details of the resource, which is taken from the organization shift details. |
|
|
This table stores the alternate resource details. Whenever the resource is on leave, the activities coming to this resource’s activity list will be redirected to the alternate resource activity list. As a result no activity gets delayed because of the resource’s absence. |
|
|
This is a filter option where the resource can customize the view of the activities in the activity list. The criteria can be saved as a query and it retrieves data from SWActivityList table based on the search criteria. |
|
|
This table stores information about the task status types. |
|
|
This table stores information about the task assignment status type. |
|
|
This table stores information about the task status. |
|
|
This table stores information about the task list. |
|
|
This table stores the report details whenever a report set is saved by a name. This can be used for future cases where the same expression is required. |
|
|
This table stores the event messages logged for an action. |
|
|
This table stores the event messages logged for a workflow. |