Important
You are browsing the documentation for version 4.2 of OroCommerce, OroCRM and OroPlatform, which is no longer maintained. Read version 5.1 (the latest LTS version) of the Oro documentation to get up-to-date information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
CLI Commands (WorkflowBundle)¶
oro:debug:workflow:definitions¶
To see current workflow definitions registered in the application, use the following command:
php bin/console oro:debug:workflow:definitions
Use --workflow-name
option to display the definition of a specific workflow:
php bin/console oro:debug:workflow:definitions --workflow-name=<workflow-name>
oro:workflow:definitions:load¶
The oro:workflow:definitions:load
command loads workflow definitions from configuration files to the database.
php bin/console oro:workflow:definitions:load
The --directories
option can be used to specify custom location(s) of the workflow configuration files:
php bin/console oro:workflow:definitions:load --directories=<path1> --directories=<path2>
The --workflows
option can be used to load only the specified workflows:
php bin/console oro:workflow:definitions:load --workflows=<workflow1> --workflows=<workflow2>
oro:workflow:handle-transition-cron-trigger¶
To triggers a workflow transition cron trigger, use the following command:
php bin/console oro:workflow:handle-transition-cron-trigger
oro:workflow:transit¶
To transitions a workflow item, use the following command:
php bin/console oro:workflow:transit
oro:workflow:translations:dump¶
The oro:workflow:translations:dump
command dumps (prints) workflow translations (workflow label, step labels, attribute labels, transition labels, button labels, button title and warning messages) of a specified workflow.
php bin/console oro:workflow:translations:dump <workflow>
The --locale
option can be used to specify a different target locale.
php bin/console oro:workflow:translations:dump --locale=<locale> <workflow>