High level process planning can be created in the Flow Designer by using placeholder steps and other visual elements to plan and collaborate without getting into too many details. Designers can then evolve the high level business model, with additional steps in the toolbox, to create the finished application. These high level business models don’t go to waste after implemented, as they are often later used as diagrams in dashboards to display the status of the workflows to other team members.
Business Metrics in the Workflow.com platform are key business indicators that any step in a workflow can participate in. These business metrics can be displayed on dashboards and even be tied to alerts when changes are made to workflows in order to help improve an organization’s efficiency.
A workflow can be created as a single step that can then be incorporated into other workflows. This process is considered to be nesting a flow within another flow as a Linked Flow, or SubFlow. This not only helps organize large workflows, but is also useful when creating a process that can be used over and over again without ever being recreated. Linking workflows together is a natural process and allows you to move from one workflow to the next when editing so you can understand the overall process.
Since workflows are not always sequential and don’t always follow a ‘direct path’ from beginning to end, there are several control steps that help solve problems that:
Integrations are easy in the platform, since when building a flow it automatically creates a specific service that can be used as SOAP (Simple Object Access Protocol) and/or REST (REpresentational State Transfer) to interact specifically with that flow.
A comprehensive suite of specific web services is also offered to allow developers to integrate with the workflows. A developer can search the system for flows, build up interactions, and run them using the SOAP or REST services.