Share on print

Before You Begin: Workflow Best Practices

Workflows are a powerful tool, but like any powerful tool, they work best when used thoughtfully. This page covers a few best practices to help you get the most out of them, and to help you avoid a few common pitfalls along the way.


"Process Before Technology"

It's worth remembering: Workflows are there to support your processes, not replace the thinking behind them. Before reaching for the platform, it's worth asking whether the underlying process itself is solid.

A Workflow can trigger highly customised notifications and automate all sorts of repetitive tasks, but it can only automate a process that already makes sense. Automating a flawed process just means the flaw happens faster.

Take a moment to nail down your process first. The technology will follow much more smoothly once you have.


Top Tips

  1. Start small. There's no prize for building the most elaborate Workflow on day one. Start with something simple, get comfortable with how the nodes connect and behave, then build up in complexity as your confidence grows.
  2. Test your Workflow. Before you let it loose on your live account, give it a trial run. Check that it triggers when it should and, just as importantly, that it doesn't trigger when it shouldn't.
  3. Plan before you build. A little forethought (a whiteboard, a notepad, or even the back of a napkin) can save a lot of untangling later.
  4. Who has access. By default, only System Administrators have access to the Workflows module in the Rand Platform. If someone in your organisation requires access, you can either promote that user to a System Administrator, which will automatically grant them access to the Workflows module, or we can enable access for a different user role, such as Manager.
    • Please note that enabling access for a role applies to all users assigned to that role.
  5. Review periodically. Processes change, fleets change, priorities change. It's worth giving your Workflows an occasional check-up to make sure they still reflect how you actually work.
  6. Keep it disabled while building. Leave your Workflow in disabled mode while you're setting it up, so nothing fires prematurely.

Before You Begin


Things to Remember

  • Workflows are only as good as the logic behind them: "garbage in, garbage out."
  • Small, well-tested Workflows are far easier to troubleshoot than large, untested ones.
  • Support is always on hand if you get stuck.

Related Articles

Still Need Help?

Contact our Support team. We are always happy to help.