Set-up
Last updated
Was this helpful?
Last updated
Was this helpful?
Both connectors work via a URL redirection. The users are redirected from their original application to the Deepomatic interface. After finishing their job in Deepomatic, they can be automatically redirected to their original application.
Three elements are necessary to allow this bi-directional redirection :
Token - an authenticator which allows the redirection to the Deepomatic interface.
Default callback URI - a static URL on which the users will be automatically redirected after finishing their job in Deepomatic.
Flow interruption - defines at which step the flow of the field user is interrupted.
The authentification is token-based, a token will therefore need to be passed at the redirection.
The token is linked to our user management system. A token is bound to a single user, the user rights determine what the user can see based on the permissions of the account. It is possible to have a token for multiple users (considering for example that the account in Deepomatic is a grouping of several users).
The token will be set-up and provided by the Deepomatic team. It is possible to specify an expiration date for a token.
The character & is not supported in the token and the token length must be below 256 characters.
In order to have a seamless user experience, it is mandatory to provide a default callback URI so the users are sent back to where they were on the field app after they performed their job on the Deepomatic interface.
This URI is static, will be stored in our database and linked to your token. However, when making a redirection you will be able to pass callback URIs as a query parameter to implement more dynamic redirection. The default callback URI is mandatory to ensure that even when no callback URI is provided as a query parameter the users can be redirected to their parent app. More information on the callback URIs as query parameters in this .
For the callback to work with a native app, the schema URI must be registered as being handled by the native app.
Depending on the desired user flow, it is possible to define when field users will be redirected to their field app. There are three options of flow interruption:
BEFORE_ANALYSIS : field users take the photo and are then automatically redirected to their field app without seeing the AI results in Deepomatic.
AFTER_ANALYSIS : field users take the photo, see the AI results in Deepomatic and then are redirected to their field app.
AFTER_WORK_ORDER : field users are redirected to the field app once they leave the work order page. This option is specific to the Work order connector.