Visual workflow builder (SOAP)
 Previous Topic  Next Topic 
Workflow (SOAP) widget in the custom category can be used to rapidly create workflows through drag and drop in a workflow builder. The code for this custom workflow can then be generated just like for other widgets.

First start by adding 1 or more SOAP webservices. To add a webservice, just point to the wsdl url.





Now click on Workflow and add one or more nodes (screens/pages). Make connections between nodes. The connections help us figure out the order for showing the nodes. Right click on the node to launch property sheet for it or to delete it.

There can be various types of nodes in a workflow. Any type of app can be built by a combination of these nodes:
  1. Static content: This type of node can be used to put static content like description, instructions etc.


  2. Menu: This type of node can be used to show a list of navigation options to the users. Users can navigate to another node or to an external url

  3. Decision: This type of node can be used to route to a specific screen based on the matched condition. Select a webservice operation whose result determines the routing. Enter 1 or more conditions.

    Each input parameter can be entered by user or hardcoded.


  4. Search: This type of node can be used to display records from a webservice operation. Select a webservice operation. Edit input params and hardcode them or leave for users to fill out. Edit output params and set labels, visibility and type (text, image, other)


  5. Add: This type of node can be used to add records via a webservice operation. Select a webservice operation. Edit input params and hardcode them or leave for users to fill out. Labels can be set for each field for input form


  6. View: This type of node can be used to display a specific record from a webservice operation. If this node comes after a search node, you can set it to automatically get input params from the result of the search query by marking parameter scope as request. Labels can be set for output fields. The fields can also be hidden as required.


  7. Delete: To delete records, use the Delete node. Select webservice operation, edit fields for input form as required. If this node comes after a search node, you can set it to automatically get input params from the result of the search query by marking parameter scope as request. Labels can be set for output fields. The fields can also be hidden as required.


  8. Update: To update records, use the Update node. This node has 2 webservice operations. The first operation is used to retrieve a record for update. The second operation is used to submit updated record to the webservice. If this node comes after a search node, you can set it to automatically get input params for first operation from the result of the search query by marking parameter scope as request. Input/output parameters can be edited as described earlier.



    Here is an example of a finished workflow. Click Save when you are done.


    And here is the app generated from this workflow.