Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

In this tutorial, we will show how to check the status of a DataFlow from the FlowEngine.

We will be using the node “Check Dataflow Status“ on the “Onesait Platform Dataflows““ category

 

Let's see how we can use that node. To do this, we will follow the following steps:

  1. Select the "FlowEngine Management" option from the menu:

     

  2. Select the domain belonging to your user:

     

  3. Once you are in the domain, drag a node of type "Check Dataflow Status" to the flow and double click on it to see its properties.


    The following are the base properties:

    1. Name: The name that you want the node to have when viewing it within the flow.

    2. Dataflows available: List of dataflows availables by the user

    3. Dataflow: Dataflow selected in the previous box. This dataflow is the one that will be started. If msg.dataflowIdentification has content, this will be used insted of the base property.

    4. Wait until Status: It will allow us to configura a single execution from an incoming message (none option) or a scheduled periodic polling for a status value. The options are:

      1. none: Default node behaviour. It will check the status only if there is an incoming message

      2. interval: It will check the status every time you configure since the last deploy instant

      3. interval between times: It wil set a scheduled check in a crontab like manner.

      4. at specific time: It will schedule one status check at a given time.


        If any of the scheduled options is selected, two more properties will appear:

      5. Status: It will only generate an output if the DataFlow is in the specified status.

      6. Restart checking status after receiving a message. If marked, it will restart the scheduled status check after a msg is received. If not, the shceduled task will be done after deployment.

      7. Stop after first match. It will stop the scheduler once the given status has matched after one execution. If the schedured has stopped it will ve indicated in the node status as follows:

        1. Waiting for status/scheduler running

        2. Status found/scheduler stopped


  4. Run the dataflow

    Whenever a message reaches the node (or the scheduler runs matching the statuses), it will try to check the selected DataFlow’s status. The result of the execcion (and its state) will be shown in the msg.payload:

  • No labels