Guide field workers
Several features can be implemented to guide field workers in uploading the right data.
It is recommended to display information to the field workers to help them perform their work properly. Several information can be retrieved at the task group level :
Display name : user-friendly name of the task group.
Description : a short-text description of the task group, to help field workers better understand the type of information that is expected.
Input examples : an example image of what is expected, also to guide the field workers.
To better understand how these endpoints could be used in practice, please refer to our mobile application documentation.
Here are described two endpoints to retrieve a specific task group and the complete list of task groups associated to a specific visual application.
All endpoints are described with the EU (Europe) server format. If your application runs on the US server, you will need to use the following format: https://api.{site-id}.customers.us1.deepomatic.com/v0.2/.
Every Deepomatic application is versioned. We recommend to not integrate any logic based on the tasks and task groups ids as those ids changes when a version is upgraded. You can instead use tasks and task groups names that are agnostic to version changes.
Retrieve a task group
GET
https://api.{site-id}.customers.deepomatic.com/v0.2/task-groups/{name}
Path Parameters
name*
string
Slug identifier of the task group to retrieve
Headers
Authorization*
string
Deepomatic API Key associated to your account.
Response format
input_examples
- array : array containing URL links leading to the input examples (photo) set for a specific task group.
only_for_dashboard
- boolean : whether or not a task should be pushed to field workers. If false, the task should be pushed.
conformity_status
- boolean : whether or not a task is included in the conformity score which allows to compute the completion state of a work order.
outcome_type
- string : type of value returned after the analysis (Number, Boolean...).
outcome_validation
- array : array containing the information (color, message, validation status) of how the task should behave depending on different analysis results. The different analysis results scenario are defined in the schema
.
In the example below, if the value detected is superior to 1, then the color
"#e4264e " and the sentence
(message) "At least one issue has been detected" should be displayed to the field workers. is_conformity_validated
returns the validation status of the task, in that case the task is not validated.
To retrieve how those different information are configured in our platform, refer to the tasks documentation and task groups documentation.
Request example
Retrieve all task groups in a visual application
GET
https://api.{site-id}.customers.deepomatic.com/v0.2/task-groups/
Headers
Authorization*
String
Deepomatic API Key associated to your account.
Response format
input_examples
- array : array containing URL links leading to the input examples (photo) set for a specific task group.
only_for_dashboard
- boolean : whether or not a task should be pushed to field workers. If false, the task should be pushed.
conformity_status
- boolean : whether or not a task is included in the conformity score which allows to compute the completion state of a work order.
outcome_type
- string : type of value returned after the analysis (Number, Boolean...).
outcome_validation
- array : array containing the information (color, message, validation status) of how the task should behave depending on different analysis results. The different analysis results scenario are defined in the schema
.
In the example below, if the value detected is superior to 1, then the color
"#e4264e " and the sentence
(message) "At least one issue has been detected" should be displayed to the field workers. is_conformity_validated
returns the validation status of the task, in that case the task is not validated.
To retrieve how those different information are configured in our platform, refer to the tasks documentation and the task groups documentation.
Request example
Last updated