Paths and Actions

To support more complex workflows, Sliderule allows you to create workflows with multiple branches, known as Paths. You can use Breakout Rules to decide when to follow an optional branch in your Workflow, known as a Breakout Path.

Starting with v2.11, Paths can end with any type of logic block, allowing customizable Actions to fire when your Workflow reaches the end of a Path.

Default Path

As your Workflow runs, it will execute each Logic Block in order from right to left, starting with the Input Block. When you add Logic Blocks to the right of your Input Block, your Workflow will advance to the next Block by default, unless:

  1. A rule interrupts the workflow to return a Result immediately (by calling Approve, Reject, or Investigate) - see Then and Action Cells for more details
  2. Your Workflow reaches a Breakout Rule

The Path that only uses Blocks to the right of your Input Block is the Default Path, since each Block will run by default.

The path below, which begins with a dashed line, is a Breakout Path

Breakout Paths

For more complex Workflows, you can use Breakout Paths – alternative paths to follow when certain conditions are met.

You can create a Breakout Path by:

  1. Dragging a new block under an existing Ruleset Block until the drop zone appears below the original Block
  2. Dragging a path from the bottom handle of a Ruleset Block to another Block
  3. Using the breakout keyword inside a Rule, for example breakout ‘Ruleset #2’

If you create a Breakout Path by dragging on the graph, Rules will be automatically created inside your Ruleset. You can then customize these rules with the conditions that must be true for your Workflow to follow this new Path

Your workflow will always return an Output, including a result of Approve/Reject/Investigate, and custom variables if needed, regardless of which Path the workflow follows. You can click the End Point of any branch to see the Output that will be returned.

Actions

You can create Paths that end on Logic Blocks that call out to other systems and tools outside Sliderule. These can be used to trigger automated actions when your Workflow completes a Breakout Path, including:

  • Notifications – using the Notification Block, you can message your teammates using Slack or Email when your
  • API Calls – call internal services at your company to take actions like blocking a customer, account, or device_id, etc
  • Database Calls – mark customers or transactions as blocked, fraud, etc by making calls to your internal databases (coming soon)

Learn more on how to use these Block Types here https://docs.sliderule.io/docs/data-connectors

Coming fall ’22, Sliderule is getting an Action Templates library, allowing you to re-use common actions based on these block types, across all your Workflows.

Error Paths

Dragging a path below Block Types other than Rulesets, for example API Connector Blocks or Database Connector Blocks, will also create a new Path in your Workflow. These paths are typically used when a Block tries to call for more data, but receives an error or a timeout.

To configure the conditions for these Error Paths, click on the Error Path tab in any data connector block.