# 3 - A First Pipeline
In MONDAT on the pipelines page, press Add Pipeline and add a pipeline named
myPipeline
.Add a description to your pipeline.
Click on the definition tab and delete the existing default step, then drag the following steps onto the pipeline definition.
- example /
saySomething
(Open the item and add your own message) - util /
delay
(sleep for 15 seconds) - example /
saySomething
(Set the message to continuing now...) - Fixed reply (Return any message you like)
- example /
Important
Don't forget to press Save! Sorry, the current version gives no indication that the pipeline save worked.
TIP
The search filter can save a lot of time
- Restart server by saving
app.js
using <control>-S.
# Test your Pipeline
Go to the Testing page and add a test case for your new pipeline.
Press the Save button.
Click on Run test for your myPipeline test.
You will see an error message.
{
"code": "InvalidArgument",
"message": "Missing req.tenant (normally set by middleware)"
}
2
3
4
This null transaction is a test transaction that bypasses user authentication, but your pipeline does not. In our code so far we have not done anything to tell DATP which user is starting a pipeline, so it refuses to start our pipeline.
# Pipeline versions
# Exporting and inporting pipelines
# Coming up next...
In the next section we address how users are authenticated, and the tenantId
is passed through to DATP.