Flow Deployment and Versions

Flow Deployment and Versions

Flow Deployment

Once you have built and tested a new flow in the Flow Studio it’s time to deploy it on some nodes for production usage. There are two ways you can do this:

Deploying flows from the Flows page

On the flows page you can use the Deploy action in the right-most colun of the flows table to deploy a flow to one or several nodes. This action will open up a dialog that lists all nodes currently registered in your organisation. You can select one or more nodes from the list and then click on Deploy. The flow will then be installed permanently on the selected nodes. Alternatively you can switch to the Labels tab and instead to select a label and then click on Deplopy. Now the flow will be deployd to any node that has the selected label, which can be any number of nodes. When you click on Deploy the popup window will close and the deployment process will start. In the detailed view to the right of the Flows table you will see the progress of the deployment. When completed the status of all nodes will show Started. From this panel you can also manage your deployed flows by selecting one or more nodes from the list. The bottom of the panel will then show some actions, like Stop (temporarily stop the flow), Start (start a stopped flow) and Delete (remove a flow from the selected nodes).

Deploying flows from the Nodes page

Another option is to deploy nodes from the Nodes page. You then start by selecting a node from the list, or filter out a group of nodes using the Labels column filter. In the detailed view to the right of the nodes table you can then click on + Add Flow. This will open a list with all your flows, where you can select a flow and a version of that flow. Finally you click on Add flow and the flow will be deployed to the selected nodes.

Flow Versions

Crosser Cloud has integrated version control of flows. When a flow is deployed on some nodes the current version is locked (read-only) and to make changes you have to create a new version. You do this by using the ‘+’ action on the previous version. This will create a new version which is opened in the FlowStudio editor. This version remains editable until you deploy it into a node.

To upgrade a deployed flow to a new version you can either just deploy the new version using any of the above methods, or you can select the node you want to upgrade in the detailed view to the right of the flows table and then use the Change Version action. This will present a list of all available versions and you can select any of them, i.e. you can bot upgrade and downgrade flow versions. In the list you see all nodes that run the previous version and if you want to upgrade them all, just select all nodes and use Change Version.

    • Related Articles

    • Flow to Flow communication

      Introduction One of the benefits of the Crosser solution is that you can deploy multiple flows (processes) into one existing container. Due to that, you can add new use cases without influencing running processes at the edge, even without restarting ...
    • The Flow Studio

      The Flow Studio If you are using Flows built with previous versions of the Flow Studio, please check the "Using Flows built with the old Flow Studio" section below. The Flow Studio is the design tool you use to build and test flows. This is a drag & ...
    • Deploy Your Flow

      Deploy Your Flow These steps does not apply to a Sandbox, you cannot deploy a flow to a Sandbox. In order to be able to deploy a flow to a Crosser node you first need to have registered your nodes. (Please see Node installation for more information) ...
    • Introducing Crosser Control Center and a new Flow Studio

      Release Note Crosser Control Center Feb 2, 2023 Introducing Crosser Control Center With this release we are introducing some brand changes that gradually will be implemented across all documentation, illustrations and marketing materials. The main ...
    • Flow Parameters

      Flow Parameters Flow Parameters address the following two use cases: You want to use the same flow on multiple nodes, but some settings are different You use the same setting in multiple flows, e.g. credentials for access to some external service, ...