Flows

Each flow represents specific business logic in an app. An app can have one or more flows. A flow contains one or more activities. It is activated by a trigger.

You can create the trigger at the time of flow creation or create a blank flow to begin with and add one or more triggers to it at a later time after the flow has been created. If you anticipate that you will need multiple triggers for a flow, be sure to create a blank flow and add the triggers as needed. If you create a flow with a trigger, you will not be able to modify it or add triggers to the flow once such a flow has been created.

  • Creating a Flow
    Every app has at least one flow. Use the Create a Flow button on the app page to create a flow in an app.
  • Using Subflows
    TIBCO Cloud Integration- Flogo (PAYG) provides the ability to call any flow from another flow in the same app. The flow being called becomes the subflow of the caller flow. This helps in separating the common app logic by extracting the reusable components in the app and creating standalone flows for them within the app. Any flow in the app can become a subflow for another flow within the same app. Also, there are no restrictions on how many subflows a flow can have or how many times the same subflow can be called or iterated in another flow. Hence, subflows are useful when you want to iterate a piece of application logic more than once or have the same piece of logic repeat in multiple locations within the app.
  • Creating Multiple Flows
    An app can have one or more flows.
  • Creating a Flow Execution Branch
    Activities in a flow can have one or more branches specifying conditions. These branches are created from within the activity in the flow. Branching is also supported for Error Handlers in a flow.
  • Editing a Flow
    You can edit the flow name or its description after creating the flow. You can also add more activities, rearrange existing activities by dragging and dropping them in the desired location, or delete activities from the flow.
  • Reverting Changes to a Flow
    If you have multiple flows in an app, you cannot revert changes made to a single flow. However, you can click the button on the app page, to revert all changes made to the app and revert the app to the state that it was in after the last . All changes made to the app will be lost. This can be done as long as you have not the app after making the changes.
  • Switching Between Flows in an App
    If an app has multiple flows, you can switch between the flows.
  • Deleting a Flow
    You can delete a flow from the app page.
  • Configuring the Error Handler
    Use the error handler to catch exceptions that occur when executing a flow. If there are multiple flows in an app, the error handler must be configured for each flow separately. Branching is supported for error handler flows similar to the other flows.
  • Adding an Activity
    After a flow is created, you must add activities to the flow.
  • Configuring an Activity
    After adding an activity, you must configure it with any input data that the activity might need and the output schema for activities that generate an output.
  • Using the Iterator in an Activity
    When creating a flow, you may want to iterate a certain piece of logic multiple times. For example, you may want to send an email to multiple people based on the output of a certain activity (let's call it activity1) in your flow. You can do this by adding a SendMail activity following activity1 in your flow and configure the SendMail activity to iterate multiple times when activity1 outputs the desired result. Each iteration of the SendMail activity is used to send an email to one recipient. This saves you the effort of creating multiple SendMail activities.
  • Deleting an Activity
    You can delete an activity in a flow from the page for a flow.