Terminology¶
Welcome to the "Terminology" chapter of the FlowRunner™ User Guide. Understanding the key terms used in this guide will make your experience with FlowRunner™ smoother and more intuitive. Let’s dive into the essential terms you’ll encounter as you explore the platform.
The Basics¶
-
Flow: A Flow is the heart of an automated process in FlowRunner™. It’s like a roadmap that guides a series of events and actions to accomplish specific tasks, whether you’re automating business operations or simplifying daily routines. Flows are flexible and customizable, allowing you to design processes that fit your exact needs.
-
Flow Version: Flows are not set in stone—they can evolve as your needs change. Each Flow can have multiple versions, each one reflecting different updates or tweaks. Although you can only have one version active at a time, it’s easy to make changes. Just clone the current version, make your edits, then stop the old version and start the new one. Remember, you can’t edit a Flow that’s currently running, so always clone before making changes.
Components of a Flow¶
-
Block: Blocks are the building pieces of your Flows—think of them like the Lego bricks that make up your automated process. Blocks include Triggers, Actions, Transformers, and Conditions. Each one has a specific job in making your Flow work smoothly.
-
Trigger: A Trigger is like a switch that waits for something to happen before your Flow continues. It might be waiting for a form to be submitted, an order to be placed, or any other event. Triggers can be placed anywhere in your Flow, giving you control over when and how your automated process moves forward.
-
Action: Actions are the steps that get things done in your Flow. They’re the tasks that do the work—like sending an email, generating a report, or calling an API. Actions take in data, do something with it, and can pass along results to the next step in the Flow.
-
Transformer: Transformers are like data editors within your Flow. They let you adjust, extract, convert, or manipulate data to fit your needs. If you need to make changes to your data as it moves through your Flow, Transformers are the tool for the job.
-
Condition: Conditions are decision points in your Flow. They let your Flow take different paths based on whether something is true or false. This adds a layer of logic to your Flow, making it more dynamic and responsive to different scenarios.
-
Groups: Some Blocks can act as containers that hold other Blocks, helping to keep your Flow organized. FlowRunner™ has two types of groups: Triggers Group and Actions Group. These groups help you manage multiple triggers or actions within a single, cohesive structure.
-
Flow Editor: The Flow Editor is where you build, edit, and test your Flows. It’s a visual workspace that lets you design your automated processes with a drag-and-drop interface. Think of it as your canvas for bringing automation ideas to life.
-
Test Mode: Before putting your Flow into action, it’s a good idea to test it out. Test Mode in the Flow Editor lets you run your Flow with test data, helping you find and fix any issues before going live.
-
SLA Condition: SLA Conditions are the benchmarks you set for your workflows to make sure they’re meeting certain standards. FlowRunner™ monitors these conditions to keep your processes running smoothly and on track.
-
Non-compliance Rules: If something goes off track and your Flow doesn’t meet the SLA Conditions, Non-compliance Rules kick in. These rules define what actions should be taken to address the issue and ensure things get back on track.
-
SLA Configurator: The SLA Configurator is a tool within the Flow Editor that helps you set up and manage your SLA Conditions and Non-compliance Rules. It’s essential for making sure your Flows perform reliably and meet the standards you’ve set.
By getting familiar with these terms, you’re setting yourself up to make the most of FlowRunner™. With this foundation, you’ll find it easier to navigate the platform and start automating processes that enhance your business or daily life.