For augmented technician use cases, you probably need to create an API on top of your workflow to be able to integrate this API into a Field Service Management tool. Deepomatic platform offers an off-the-shelf component that automatically add an API to your visual automation application. See below for the specifications of the API.
To build solutions to complex problems, you need to tightly connect your workflow and business logic with this API, which is ultimately the interface with which the technician's application interacts.
You define the checkpoints in your application with the outcome steps in your
When calling the API, you get the answers for the questions that generate an output in your workflow. See the integration of the API for the exact data format.
The traditional way of conducting field interventions is that once a control point has been validated, it can no longer be invalidated. To implement this logic, but also to build solutions to more complex problems that require different photos to validate a control point, it is necessary to introduce the notion of memory and of state of an intervention. The state of an intervention is indeed very often determined both by the result of a workflow execution, but also by the past state of the intervention.
To access the current values of the state of your intervention, you must define entries according to the following nomenclature: <outcome_name>_previous. At each workflow execution, this entry's value is the current answer/outcome for the corresponding intervention.
Workflow with memoryworkflow:entries:- name: image_inputtype: Image- name: checkpoint_previoustype: Textoutcomes:- name: checkpointoutput_of: my_step_that_checksconcept:name: status of the thing that needs to be checkedtype: Text
With the above workflow, you are able to use the value of the checkpoint in the execution of the workflow.