In this article we will describe the process for creating a simple workflow from scratch.
For demonstration purposes, we will create a simple workflow to synchronize employee records between Talent Manager and Quinyx.
First, choose the two (or more) apps you want to connect in the list on the left:
It is a good idea to use a test environment when you build a new integration, if your app supports it.
See this article for more info: Using a test environment
On the screen you will have the option to give the workflow a name and description:
Adding blocks
A workflow is made up of blocks.
A block is a re-usable, modular piece of code that executes one or more tasks.
On the left, you will see a list of available blocks for the applications you have selected, as well as several generic blocks, including Mapper, Code and Join. (These will be described in more detail in separate articles.)
To start building the workflow, simply drag the blocks you want onto the canvas.
In this example, we will need:
A block to fetch employees from Talent Manager.
A block to update employees in Quinyx.
A mapper block to map data and fields between the two applications
<SCREENSHOTS>
Configuring blocks
If you click the blocks on the canvas, you will see each has settings that allows you to customize how it works, with some fields being marked as required information. These are specific for each application, with individual documentation.
Before we do the mapping, we need to some simple configuration for the application specific blocks.
Mapper block
Data coming out of one application will need to be reformatted before it is transferred to the destination application. That is where the Mapper block can be used.
The Mapper block lets you transform data and map fields between a source and a destination application.
When we click on Map Model, the Mapper block will ask the source and target blocks to give examples of the kind of data they use. The mapper block will use this information to dynamically construct a mapping screen.
Please note that the Mapper block is currently a work in progress, so you can expect the Mapper block to gain more features and improve going forward.
The mapping screen can be thought of as a spreadsheet with two columns – one for the source application, and one for the target application.
By simply clicking on the corresponding fields, you are building a map for how data should be transformed.
And like in a spreadsheet, you also have the possibility to use functions, to concatenate fields, put things to upper case, date manipulation, etc.
Save the mappings, and then save the workflow.
So, to summarize, this workflow is going to get data out of the HR app, we are going to map it based on the mappings we created, and then we are going to load it into Quinyx.
Let’s run it!