Workflow Framework: Task Execution

Whenever a task is started the system executes it in the following sequence:

The system first loads the task from the generic_task table and then executes the task using multiple sub-steps:

1. When configured, the system calls the load logicnet to load data into the data context. If load is not configured the framework will load the dataobject_data BLOB from the generic_task_storage table.
2. When configured, the system triggers the pre-process logicnet. It then triggers the task logicnet.
3. When configured, the system will trigger the post-process logicnet to process data submitted in the task logicnet.
4. If the task is a UI task and the selected output option validation is set to "yes", the system will trigger the validation step to look for input errors and will display validation warnings if necessary. It will also return to the task logicnet. Depending on the selected output, the workflow will remain in the current task or continue to the next task.
5. Finally, when configured, the system calls the save logicnet. If the save logicnet is not configured the system will save dataobject_data to the generic_task_storage table. You can override this behavior with a custom save logicnet.

The system will check to determine if the workflow has reached its end. If so, the system will determine if the workflow is a child to another workflow and will trigger the parent workflow.