5.2 Workflow Definition
Workflows, comprised of module instances, identify specific tasks and outline the order in which they are completed. Module instances are the activities or operations. Together, workflows and module instances provide an operational outline of which operations to complete.
All functionality used by CHPS in processing dynamic data and running external forecasting models is configured in module instances. These instances execute in a logical sequence, which is defined in a workflow.
Activities
Each task in a defined workflow file is called an activity. Single or multiple activities may be contained in the workflow.
Different types of activities include sequences of module instances, nested workflows, and/or ensemble runs.
Files
All workflows must be registered in the WorkflowDescriptors.xml file in the RegionConfigFiles directory in order to process the activities.
Entries in the file define the specific behavior of the workflow.
Each workflowDescriptor id defined in WorkflowDescriptors.xml has a corresponding XML configuration file in the WorkflowFiles directory.
Sequences
Workflows activities are processed in the order in which they are listed in the configuration.
Since the activities process in a logical sequence, workflows can assist with troubleshooting if the results are not as expected.
Workflows contain calls to module instances and other workflows. 
Water Cooler Break! Take a few minutes to explore a workflow configuration file. Learning to configure new or existing workflows requires practice and exploration of the files!
Reference: For more details on configuring workflows, please refer to the Deltares Delft-FEWS Configuration Guide.