workflow Table (526)
SuperOffice specific info about a workflowFields
| Name | Description | Type | Nullable |
|---|---|---|---|
| workflow_id | Primary key | PK | No |
| name | Name of the workflow | String(255) | Yes |
| description | Description of the workflow | String(4000) | Yes |
| status | Status of the workflow definition | Enum WorkflowDefinitionStatus | Yes |
| associate_id | Associate who owns this workflow | FK associate | Yes |
| group_id | Group id of original owning associate, so that changes to owner’s primary group do not influence group membership of this workflow. | FK UserGroup | Yes |
| start_only_once | A contact can start this flow only once | Bool | Yes |
| jump_to_finish | When a goal is reached, contact jumps directly to finished | Bool | Yes |
| visible_for_all | True if visible for all | Bool | Yes |
| visible_for_associates | Array of references to the visible for associates | FKArray | Yes |
| visible_for_groups | Array of references to the visible for groups | FKArray | Yes |
| registered | Registered when | UtcDateTime | No |
| registered_associate_id | Registered by whom | FK associate | No |
| updated | Last updated when | UtcDateTime | No |
| updated_associate_id | Last updated by whom | FK associate | No |
| updatedCount | Number of updates made to this record | UShort | No |
| use_workflow_start | Start the flow running with enrolled participants at the given time | Bool | Yes |
| workflow_start | When to start running the workflow. Until start, any enrolled members are not running through the flow, just waiting. Datetime is interpreted in stored timezone or as UTC | UtcDateTime | Yes |
| use_enrollment_end | End enrollment into the workflow at the given time | Bool | Yes |
| enrollment_end | Do not enroll more participant after given time, interpreted in stored timezone or as UTC | UtcDateTime | Yes |
| tzLocationId | Timezone used for this workflows datetimes. If not set, behavior is best guess - databasetime, system time… | FK TZLocation | Yes |
| remove_from_flows | Workflows to remove the participants from when they are enrolled in this workflow | FKArray | Yes |
| block_lists | Persons in the given selections are not allowed to enter this workflow | FKArray | Yes |
| exit_flow_id | On exit with no success criteria met, we attempt to add the participant to the given flow | FK workflow | Yes |
| exit_success_flow_id | On exit with success criteria met, we attempt to add the participant to the given flow | FK workflow | Yes |
Indexes
| Fields | Types | Description |
|---|---|---|
| associate_id | FK | Index |
| visible_for_associates, visible_for_groups, remove_from_flows, block_lists | FKArray, FKArray, FKArray, FKArray | Full text |
Relationships
| Table | Description |
|---|---|
| appointment | Tasks, appointments, followups, phone calls; and documents (document_id != 0). An appointment always has a corresponding record in VisibleFor specifying who may see this. |
| associate | Employees, resources and other users - except for External persons |
| email_flow | A set of properties related to the email workflow. |
| person | Persons |
| sale | Sales For every Sale record edited through the SuperOffice GUI, a copy of the current version of the record will be saved in the SaleHist table. This also applies to editing done through the SaleModel COM interface, but not to editing done through the OLE DB Provider or other channels. |
| selection | Selections |
| ticket | This table contains the tickets (requests) of the system. Its purpose should be evident. |
| TZLocation | Time zone location |
| UserGroup | Secondary user groups |
| workflow | SuperOffice specific info about a workflow |
| workflow_goal | A set of goals related to a workflow. Some goals will have search criterias associated with it to determine if the goal has been reached. |
| workflow_instance | A set of properties related to the workflow instance of one participant going through the flow |
| workflow_root_step_link | Link root steps to the workflow |
| workflow_trigger | A set of triggers related to a workflow. |
Replication Flags
- None
Security Flags
- Sentry controls access to items in this table using user’s Role and data rights matrix.