Work order connector set up

Description

The Camera Connector has been designed to redirect users at the camera level in the Deepomatic application. With this connector, the user follows these steps :

  • The field engineer is on his primary field app, on his job screen. In the job form, he is asked to verify his work or audit with Deepomatic.

  • When clicking on the button to take a photo, he is redirected seamlessly to the Deepomatic app :

    • he arrives directly on the work order screen where he sees all the pictures he has to take for this job. For each of these picture, the user will have the following flow once he clicks on "take picture" :

      • arrive on the camera screen,

      • takes a picture and validate,

      • AI runs on device

      • sees the analysis results,

      • in case of errors, and according to your configuration, he might have to declare an exception within the Deepomatic interface.

  • Once they are done, they finally click the "done button" to return to their original field application to continue their journey.

To Lens deeplink

Path

::://deepomaticlens/connector/work_order/

Query Params

  • site_id - UUID of site.

  • org_slug - The organization slug.

  • region - eu or us .

  • work_order_id - UUID of work order.

  • callback_uri - URI where the users will be redirected after leaving Deepomatic Lens (see Path)

  • use_fragment - (optional) Some softwares, as Oracle Field Services, do not support query parameters in the call back and the results of the analysis provided by Deepomatic (via query parameters in the callback) may be lost. By default the results are provided with query parameters, but you can ask Deepomatic to provide them as fragments using the query parameter use_fragment=true when calling the connector.

Example 

::://deepomaticlens/connector/work_order/?site_id=ecfa722f-c8e0-41b7-bd46-cbef249bce99&org_slug=deepodemo&region=eu&work_order_id=6d9a69fa-e54f-4599-8492-f4f8bfb4e91b&callback_uri=backtomywebsite.com

If you open the link again, the user will land directly on the results of the analysis.

To primary app Deeplink (callback)

Path

It is the callback_uri field that you included in the To Lens deeplink.

You should include in this link all the necessary reference to take the field engineer at the right place for example :

  • job_id

  • anchor

Protected Query Params

Some query parameters are protected and cannot be used in the callback_uri :

  • work_order_id

  • work_item_id

  • input_id

  • status

  • justify_failure

  • is_edited

If used, you the following error will be returned error=protected_query_params_used

Query Params

  • work_order_id ( required) - UUID of work order.

  • justify_failure (optional) - Returned if the user justified a failure justify_failure=true .

  • is_edited (optional) - Returned if the user edited the analysis result is_edited=true .

  • work_order_progress

  • status (required) - Status of the work order

Example

backtomyprimaryapp.com?work_order_id=6d9a69fa-e54f-4599-8492-f4f8bfb4e91b&work_item_name=street_cabinet_open_after&status=offline_analysis_ok&justify_failure=true

Last updated

Was this helpful?