An Execution step allows you to execute a specific function. Execution steps can include system functions, deployed MapForce mappings, StyleVision transformations, and other jobs. For example, you can add the system/send-mime function to send an email (possibly with an attachment) to the specified recipients.
FlowForce Server processes execution steps sequentially, starting with the first (topmost) step down to the last step. This rule also applies to any sub-steps that a step may have. The code listing below illustrates this scenario:
By default, if FlowForce encounters an error, processing stops, and subsequent steps are not executed. However, in most system functions, you can set the Abort on error parameter to false, which will prevent job execution from stopping even after an error has occurred.