When a workflow runs, you can open that specific run in interactive mode to see exactly what happened, job by job.
workflows
27 articles
How-to guides
When building workflows, issues will inevitably occur. A workflow may not start, data may not be created, or a message may not be delivered.
Reference
While working with APIs and JSON resources, you’ll often get the data in an array, rather than a single value. An array is simply a list of items, where each item can have multiple properties,…
The Add Workflow Starts Tag job sets a searchable tag on the current workflow-start instance. Use it to attach dynamic values to a workflow execution so that the workflow start can be found or…
The Clear Workflow Context job removes selected data from the current workflow context. Use it to reset temporary state between workflow steps, clean up after a branch, or make sure downstream…
There are multiple jobs in the Workflow Engine that can make use of comparison operators, the most commonly used being “Route from metadata” or the filters in the operations jobs.
The Data Operations job performs a configurable list of ordered data transformations, mainly working with strings, within the workflow context. Use it to copy, calculate, format, encode, hash, and…
The Execute Workflow job starts another workflow by searching for it by name or ID. Use it when you want to split logic into reusable workflows, trigger a public workflow from another account, or…
The Extract Data job pulls structured data out of events or workflow resources and moves it into workflow context in a form that later jobs can use. Use it when a trigger or process event contains…
This is the reference text shown in the Workflow Builder. For a walkthrough with examples, see For Each Resource.
This is the reference text shown in the Workflow Builder. For a walkthrough with examples, see For Each Resource.
The JSON Pipeline job runs an ordered set of JSON transformation steps on a workflow resource. Use it to load a JSON resource, modify it step by step, and save it back for later jobs.
The Notify UI job sends a toast notification to the Bosbec admin user interface. Use it when a workflow should surface status information, links, or short results directly to one administrator or…
The Parse CSV to Resource job parses CSV-formatted text provided in the Csv source field. The source can be either:
This is the reference text shown in the Workflow Builder. For a walkthrough with examples, see Parse CSV to Resource.
The Parse JSON to Resource job parses JSON text from a workflow value and creates a JsonResource in the workflow context. Use it when incoming payloads, metadata values, or other resources contain…
The Place holder job performs no action on its own. Use it as a visible routing point, a temporary stub while building a workflow, or a clear end point for paths such as error handling where you…
The Reset Synchronized Counter job resets an existing synchronized counter to a specific value. Use it together with synchronizedCounter.md when a quota, rate limit, or event counter should be…
This is the reference text shown in the Workflow Builder. For a walkthrough with examples, see Route From Meta Data.
The Synchronized Counter job increments a shared counter safely even when many workflows run in parallel. Use it to enforce quotas, count events, or rate-limit actions where concurrent workflow…
During the lifespan of Bosbec WE and the Workflow Builder, there have been different iterations of the expression syntax used in the properties fields and resources. While each iteration and…
Strings are one of the more common data types used in Bosbec WE, and learning how to use and manipulate them is essential. Strings are a series of characters most often intended to be read and…
When talking about variables in the context of Bosbec WE, we are usually referring to metadata. Metadata is where we store data to be able to process it later.
Concepts
Jobs are the Workflow Engine's building blocks. Each job is designed to solve a specific, smaller task, operating on the resources and data available in the current workflow context.
In the general integration process, we stated that data usually flows from System A, through Bosbec, to System B. While we would, in a perfect world, be able to simply forward data as it is…
Triggers are the starting points of any workflow and are required for the Workflow Engine to run.
The Workflow Context (WFC) is the current state and the resources and data available during a workflow's execution.