In this article we will describe the process for creating a simple workflow from scratch.
For demonstration purposes, we will create a workflow using the “Test” application.
The Test app uses a dummy API, that allow you to GET and POST some data for testing purposes, but without actually changing data.
If you have never set up a workflow before we encourage you to follow the steps in this guide for practice, to create a simple workflow with the Test app. Since the Test application just uses dummy data there is no risk involved.
To do so:
Add the Test application to your account, as shown previously in step 1.
The Test app does not require any API credentials to be entered - simply add it to your account.Then proceed to create a new workflow from scratch, and copy the steps shown in this article.
1) Select the app(s) to use in the workflow
Choose the apps you want to connect in the list on the left.
In our case we will just be using one app, the Test app, both for getting and posting data.
After clicking the button (“Use single” in our case, otherwise labeled “Connect”) you will be presented with the workflow editor.
In the next steps, we will:
Add the blocks that we need
Configure the blocks for our purpose
Configure the mapping
Adding blocks
Next we will add the blocks that will make up the workflow logic.
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 and drop 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
Configuring blocks
If you click the blocks on the canvas, you will see each has settings (under the “Working Area” tab) that allow you to customize how the block works, with some fields being marked as required information, with a red *.
Next we will look at setting up the mapping, using the mapper block.
Now is a good time to save the changes you have made. Click the save icon to save your workflow.
The 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!