Skip to main content
Version: ACE 5

Flow Step Overview

Overview​

AS mentioned before, step is the basic building block of a flow that allows creating logic. All steps in ACE have some common properties as well as individual steps have specific properties that can be configured for them.

Common properties​

  • Step Description - this is a non required field on the step configuration that allows you to add additional context to why the step is in the flow (consider it as a comment for a function that describes what the function does). It is useful when you have more than one step of the same kind.
  • Step Condition - you can execute condition on the current doc node values and if the condition returns false then the step will be skipped. Expression uses evaluator to execute condition, see more details here
  • Target path - doc node where the result of step execution should be stored

Example condition

For example we want to execute a step only if the person is 18 years or older then the step condition would be {{age < 18}} - so when the age is 17 the condition would return false and step won't be executed.

Step Types​

ACE in general split into different step types

  • Logic - Stop, Switch, Condition
  • Data transformation - steps that transform the data in a doc node - JSON Clean, Input transform, JSONATA Map, Lookup Map, JSON Map, Key-name Transform, XML ⇄ JSON, DEEP MERGE, File reference
  • Network requests - steps that allow making network requests - REST HTTP, SOAP HTTP, SOAP HTTP(Pure), JSON-RPC2.0, JWT
  • Database Access - steps that allow direct manipulation of a database - MongoDB, OracleDB, SAP IQ DB, IBM DB2, MS SQL, REDIS
  • Utility - Date Functions, JS Code Functions(deprecated), JS Code, Logger, Mixed-flow, Catch, Clear Cache
  • Data Validation - Response Validation, Request Validation, Schema Validator

Step override​

ACE provides a way to override steps by extending flow. More in depth overview is found here.