In this tutorial you will learn how to setup a simple workflow that allows you to handle any type of documents in a safe and semi-automatic way.
The workflow in this tutorial will consist of two steps:
automatic prediction
manual verification
Download the lucidtech CLI​
Create a remote component tutorial​
To create a manual step you first need a remote component that will serve as a user interface. For an example on a simple remote component see This tutorial​
$ las assets create remote_component.js
Create a json file with the following structure,
{"assets": {"jsRemoteComponent": "las:asset:<hex-uuid>"}}
Now you are ready to create the manual step
las transitions create manual params.json
An automatic step is made by creating a docker image that will perform a task without any user involved. Check out our sample images for inspiration and best practices.
The first step is to build a docker image and push it to some repository
$ docker build . -t <image-url> && docker push <image-url>
It is recommended to place the docker image in a private repository, if that is the case you need to store your credentials as a secret.
$ las secrets create username=<username> password=<password> --description 'docker credentials'
The next step is to create a json-file that contains the parameters you need to run the docker image. Note that secretId is only needed if you are using a private image.
{"imageUrl": "<image-url>","secretId": "las:secret:<hex-uuid>"}
Now we are ready to create the transition
las transitions create docker params.json
Now that we have created the two transitions we are ready to put them together in a single workflow. The workflow definition must be provided using Amazon States Language.
The Resource name of each state must be a transition ID.
The only allowed types of States are Task and Choice.
{"definition": {"Comment": "A workflow for prediction and approval","StartAt": "Predict","States": {"Predict": {"Type": "Task","Resource": "las:transition:<docker-hex>","Next": "Approve"},"Approve": {"Type": "Task","Resource": "las:transition:<manual-hex>","End": true}}}}
store the file and use it as input for creating the workflow
$ las workflows create workflow.json --name 'Predict and Approve'