Page Comparison

...

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

...

Let's see how we you 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 useryou want to work on:
   

   

    

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 configuration 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 dataflow whose status will be startedchecked. If msg.dataflowIdentification exists in the incoming message and it has content, this its value 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 allows you to configure whether you want a status check to run when receiving messages, or a scheduled check by polling. The available options are:

      1. none: Default behavior of the node behaviour. It will check the status only if there is an incoming messageof the selected DataFlow when a message is received.

      2. interval: It will check the status automatically every x time you configure since the last deploy instantnode changes are deployed.
         

         

      3. interval between times: It wil set a scheduled check in a crontab like mannerwill launch the status checks in a planned manner as if it were a crontab.
         

         

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

         

         
         If any of the scheduled options is selected, two more an option other than "none2 is chosen, two new properties will appear:.
         

      5. Status: It will only generate an output if the DataFlow is in the specified statusindicates the status you are expecting when checking. If the DataFlow status matches the one marked in this field, an output message will be generated.

      6. Restart checking status after receiving a message.: If marked as active, it will restart the scheduled status check after a msg is received. If not, the shceduled task will be done after deploymenthealth check will be performed every time an incoming message is received from the node. Otherwise, planning will be carried out after performing a "deploy".

      7. Stop after first match. It : If enabled, 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 scheduled health check run when the first match occurs. You will be able to tell whether the desired state has been found or not by looking at the state of the node in the flow as follows:

         1. Waiting for indicated status/scheduler runningactive planning:
            

            

         2. Status found/scheduler stoppedmatching the indicated/scheduling disabled:
            

            

            
            

4. Run the dataflow:

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