Deepomatic Platform
  • Overview
  • Release notes
    • January 2025
    • November 21, 2024
    • October 17, 2024
    • September 19, 2024
    • July 18, 2024
    • June 27, 2024
    • May 23, 2024
    • April 18, 2024
    • March 21, 2024
    • February 22, 2024
    • January 18, 2024
    • December 13, 2023
    • October 26, 2023
    • July 20, 2023
    • June 29, 2023
    • May 29, 2023
    • April 27, 2023
    • March 30, 2023
    • February 17, 2023
    • January 19, 2023
    • December 22, 2022
    • November 18, 2022
    • October 19, 2022
    • September 19, 2022
    • July 27, 2022
    • June 26, 2022
    • May 17, 2022
    • April 13, 2022
    • March 17, 2022
    • February 10, 2022
    • December 21, 2021
    • October 26, 2021
  • Getting started
  • ADMIN & USER MANAGEMENT
    • Invite and manage users
      • Invite group of users at once
      • SSO
        • Azure Active Directory
  • Deepomatic Engage
    • Integrate applications
      • Deepomatic vocabulary
      • Deepomatic connectors
        • Set-up
        • Camera Connector
        • Work Order Connector
      • API integration
        • Authentication
        • Errors
        • API reference
          • Work order management
          • Analysis
            • Guide field workers
            • Perform an analysis
            • Correct an analysis
          • Data retrieval
          • Endpoints' list
      • Batch processing
        • Format
        • Naming conventions
        • Processing
        • Batch status & errors
      • Data export
    • Use the mobile application
      • Configure a mobile application
      • Create & visualize work orders
      • Complete work orders
      • Offline experience
    • Manage your business operations with customisable solutions
      • Roles
      • Alerting
      • Field services
        • Reviewing work orders
        • Exploring work orders
        • Grouping work orders
        • Monitoring assets performance
      • Insights
  • Security
    • Security
    • Data Protection
Powered by GitBook
On this page
  • Single task-group
  • Multiple task-groups

Was this helpful?

  1. Deepomatic Drive
  2. Configuring Visual Automation Applications
  3. Assembling workflows

Workflow execution

The wf_client run command can be used to execute a project.

Use -p {PATH TO THE WORKFLOW PROJECT} to run a project from another directory (it defaults to current working directory)

Single task-group

  • You can specify the analysed task group using the --task-group flag.

  • You can pass entries using -e entry_name:entry_value

  • You can pass metadata using -m metadata_name:metadata_value

  • You can provide the path to your .env file if not previously sourced using the --env flag

To pass several entries/metadata, simply repeat the above syntax (multiple -e ...)

wf_client run  --task-group pm_ouvert_avant_travaux -e image_input:./pm-ouvert-avant-travaux.jpeg 

[INFO 16:54:13.961 client.py:37] engine initialization: 0.016 seconds
[INFO 16:54:13.968 client.py:37] workflow execution: 0.002 seconds
pm_ouvert_avant_travaux:
        [✓] pm-ouvert-avant-travaux-bool (bool): True
        [✓] pm-ouvert-avant-travaux-pres-etiquette-bool (bool): True
        [✓] pm-ouvert-avant-travaux-ocr-etiquette (str): 14222

Add the flag -d if you want the analysed image to be displayed with the drawn predicted regions

Multiple task-groups

You can run multiple task-groups with a shared environment (like a work-order) using an input file.

The format for the input file is:

[
    {
        "task_group": "pm_ouvert_avant_travaux",
        "entries": {
            "image_input": "./pm-ouvert-avant-travaux.jpeg"
        },
        "metadata": {
            "key": "value"
        }
    },
    {
        "task_group": "pm_ouvert_apres_travaux",
        "entries": {
            "image_input": "./pm-ouvert-apres-travaux.jpeg"
        }
    }
]

Then, running the workflow using

wf_client run -i inputs.json

Was this helpful?