Assignment Database Tables
  • 07 Jul 2023
  • 5 Minutes to read
  • Dark
    Light

Assignment Database Tables

  • Dark
    Light

Article Summary

Overview 

Due to the complex nature of Assignments, Decisions stores and maintains all of a user's Assignment Data within a series of four database tables:

  • entity_assignment
  • flow_state_storage
  • assignment_handler_data
  • flow_data_delta_storage

Each table works in conjunction with one another to provide Decisions the necessary data to properly execute and track Assignments. The following document provides insight to how these tables interact with one another, as well as charts providing information on the columns within each database table. 


Database Diagram Relationship 

The following diagram provides a relational data model that demonstrates how each of the four tables connect and interact with one another. 


entity_assignment

The entity_assignment table holds most of the user configured data, such as the Assignment Name or Escalation configurations. When a user makes a change in the Assignment Setup Properties in the Flow Designer, it gets recorded in this table. 

When a Flow needs to start after an Assignment has been completed, the information in this table is used to continue the Flow from the point where it left off.

Database Table Details

entity_assignment
assignment_idThis is the primary key field of the database table
warn_dateA user configured date that will run the user configured warn date flow send a notification to the Assignee when this date is reached
late_dateA user configured date that will run the user configured late date Flow
escalate_dateA user configured date that will send the Assignment to a different assignee when this date is reached
start_dateA user configured date when the Assignment set to the current State
priorityA user configured String field that is configured through the Assignment Setup Properties in the Flow Designer
handler_dataSerialized Data about the Handler such as the Form Assignment Handler or Custom Handler
escalation_handler_wrap_dataSerialized data about how Escalations should be handled
notesNotes
valid_only_in_folder_stateFor conditional actions where they can be assigned when the Folder is in the correct State
completedA Boolean value that is set to true once the Assignee works the Task
is_assignedA Boolean value that is set to true if the Assignment has an Assignee
is_currentA Boolean value set to true if the Assignment is active but not completed
hiddenThe Property that controls whether the Assignment can be visible or invisible
administrator_view_onlyA Boolean value set to true if the Assignment is Admin view only
entity_folder_idThe Id of the Folder where the Assignment is stored
entity_nameIs the name of the Assignment that will be displayed in a user's Inbox
entity_descriptionA String field for writing a description about the Assignment
created_on_dateThe date the Assignment was created
modified_dateThe date that the Assignment was modified
stateThis field indicates the condition the Assignment is in
archivedA Boolean used to indicate if the Assignment has been Archived
archived_dateThe date the Assignment will be Archived and permanently deleted
all_assignmentsStores details of all the Users/Groups that have been assigned this Assignment
deletedA Boolean value set to true if the Assignment is deleted
assignment_handler_idId of the Assignment Handler
assignment_handler_id_typeStores an Id of the Handler type
state_changed_dateThe date the Assignment State was changed
next_check_timeThe time when the Scheduled Job will check the assignment for any changes
next_check_typeWhat type of check is done i.e. Current, Warn, Late, Expired, or Escalated
next_check_idId of the Check
show_at_loginA Boolean value that if true will show the Assignment at the user's login
assignment_typeStores the Form Assignment Type value
has_state_changedA Boolean value that indicates if an Assignment State has changed
assignment_start_flow_idThe id of the Assignment Start Flow that a user can configure in the Assignment Setup Properties in the Flow Designer
assignment_warn_flow_idThe id of the Assignment Warn Flow that a user can configure in the Assignment Setup Properties in the Flow Designer
assignment_late_flow_idThe id of the Assignment Late Flow that a user can configure in the Assignment Setup Properties in the Flow Designer
assignment_escalte_flow_idThe id of the Escalate Late Flow that a user can configure in the Assignment Setup Properties in the Flow Designer
flow_tracking_idForeign Key from the flow_state_storage_data
step_tracking_idId of the step that created the Assignment
primary_flow_idThe Id of the Primary Flow
primary_flow_nameName of the default base Flow
flow_idThe Id of the current Flow
flow_nameName of the parent Flow 
step_idForeign Key from the flow_data_delta_storage
step_nameName of the step that created the Assignment
assignment_interaction_startedTime stamp of the interaction time
assignment_startedA Boolean value indicating if the Assignment is current
completed_date_timeThe date the Assignment was completed
completed_resultIs the Assignment Forms outcome path
completed_byRecords the user who completed the Assignment
completed_notesA String field used for storing notes about a completed Assignment
url_tokensURL token for the Assignment URL
notification_subjectThe Assignment Notification String subject that will display when the Assignment gets created
notification_messageThe Assignment Notification String message that will display when the Assignment gets created
do_not_send_default_notificationBoolean value that if set to true would cause default Notification to not trigger
assignment_time_in_secondsThe amount of time the Assignment has been active
assignment_interaction_time_in_secondsThe user interaction time with the Assignment
reference_idThe user provided Id that stored when an Assignment is configured
history_folder_idA common field created for Decisions Entities that stores Version History
all_tags_dataStores all tags that have been attached to the Assignment
deleted_byRecords the user who deleted the Assignment
deleted_onRecords the date the Assignment was deleted
extension_idThe Id of the extension object that is tied to the Assignment
extension_id_typeStores the Extension Type
folder_stateThe State the Folder is currently in



flow_state_storage_data

This database table is responsible for storing the Flow's Header Data. When a Flow comes to a Task step, Decisions takes a snapshot of that Flow and stores a record in the flow_state_storage_data table. 

This table allows Decisions to pause the Flow until an action has occurred. Once the expected action is received, the Flow continues to the next step in the process. 

Database Table Details

flow_state_storage_data
flow_tracking_id The Primary Key field of the table
archivedA Boolean indicating if the Flow has been set to an Archived status
archived_byThe user who set the Archived status
deletedA Boolean indicating if the Flow has been set to a Deleted status
deleted_byThe user who set the Deleted status
ended_in_exceptionA Boolean indicating if the Flow encountered an Exception
exception_detailsThe Log Error Message details
primary_flow_nameStores the name of the Primary Flow
primary_flow_idThe Id of the Primary Flow
primary_flow_nameName of the default base Flow
current_flow_idId of the running Flow
current_step_nameName of the current step
current_step_idId of the current step
current_tracking_idStores the current Flow Tracking Id
current_step_tracking_idStores the current Step Tracking Id
percent_completedFlow completion percentage
start_dateThe date when the Flow was started
last_update_dateThe date when the Flow was last edited
last_update_byThe user who last edited the Flow
created_on_dateThe date when the Flow was created
created_byThe user who created the Flow
flow_date_storageForeign Key of the flow_data_delta_storage table
auto_restore_result_dataStores the Result Data that needs to be sent for the Auto Restart of the step
auto_restartA Boolean value that indicates if a Flow is set to Auto Restart
auto_restart_date_timeDate when the Flow was Auto Restarted
auto_restart_failedA Boolean value that indicates if a Flow failed to Auto Restart
store_generationNumber used to determine if the stored Flow Data is up-to-date
completedA Boolean indicating if the Flow completed
completed_date_timeThe date when the Flow completed
completed_byThe user who completed the Flow
last_active_serverServer on which the Flow Data was used
last_active_date_timeThe last recorded data time the Flow Data was used
archived_dateThe date when the Flow will be set to an Archived status
deleted_onThe date when the Flow was deleted
entity_folder_idId of the Designer Folder that stores the Flow
stateThe current state of the Flow
auto_expire_onA Boolean value that indicates if the Flow is set to expire

assignment_handler_data

This table that stores data of the Assignments' Escalation, Form, and Handler data for custom Form Assignments.

Database Table Details

assignment_handler_data
IdThis is the primary key of the table
handler_dataSerialized Flow Handler data
escalation_handler_dataSerialized data about handling Escalations
form_view_dataStores the serialized data for the completed Form

flow_data_delta_storage

This table stores differential data instead of the complete Flow Data to minimize storage needs.

Database Table Details

flow_data_delta_storage
primary_flow_tracking_idThe Main Flow tracking Id
delta_dataSerialized Delta Data from the Flow
delta_time_stampDate Time of when the Delta Data was capture
current_flow_idCurrent Flow Id
current_step_idCurrent Step Id
current_flow_nameCurrent Flow Name
current_step_nameCurrent Step Name
current_step_tracking_idTracking Id of the current step
current_flow_tracking_idTracking Id of the current Flow
is_tracking_dataBoolean used to track if the data is complete or partial 

Was this article helpful?