Skip over navigation
You are currently viewing documentation for a previously released version of OroCRM. See the latest long-term support version.


Filename workflows.yml
Root Node workflows


type: map

During each step transition, a set of entity attributes can be shown to the user for which they can enter values. Each entry in this map is the name of an attribute which can be configured with a map that can contain the following options:


type: map

There are two keys that can be used with this option: If the delete key is set to true, the attribute is treated as the name of an ACL that is evaluated to check if the user is allowed to delete the underlying entity. If update is set to true, the ACL is used to check for update permissions.


type: string

The label shown next to the attribute form in the UI.


type: map

There two options which must be configured based on the chosen type:

class (type: string)

A fully qualified class name which is needed when the attribute type is entity or object.

multiple (type: boolean)

When the type is entity, this option control whether or not multiple entities can be selected.


type: string

An optional property path used to access the attribute’s value (if this is set, the other options can be guessed). You can refer to the underlying entity by a variable whose name is controled with the entity_attribute option (its default value is entity).


type: string

The attribute’s type can be any scalar (boolean/bool, float, int/integer, string), array (list of scalars or objects that are serializable), object (a serializable object) or entity (FCQN of a Doctrine entity).


type: string

The fully qualified class name of the entity the workflow is associated with (a workflow can only be used with exactly one entity type).


type: string default: entity

Name of an attribute used to store main entity.


type: boolean

If this option is set to true, the workflow is treated as built-in which means that it cannot be modified or removed in the UI.


type: string

A human readable string that is used in the UI to distinguish workflows.


type: string

The name of the workflow’s start step. The value must refer to one of the steps configured with the steps option.


type: map

The steps option configured the states a workflow can have. The keys are step names and each value is a map that contains options that configure the particular step:


type: sequence

A list of transitions that can be applied at this stage.


type: map

Two options can be configured under this key to control which kind of actions can be performed in this step:

delete (type: boolean)

If true, the entity can be removed.

update (type: bolean)

If true, the entity can be modified.


type: string

A human-readable string to identify the step in the UI.


type: boolean

This option must be set to true to identify final workflow states.


type: integer

Steps are ordered by this value in the workflow steps widget.


type: boolean

If set to true, all steps will be shown in the workflow step widget in the UI. Otherwise, only steps that have an order value less than or equal to the current step will be shown. This is useful to indicate the following steps of an entity.


type: map


type: map

Transitions define how one step is transformed into another using the following options:


type: string

A message that will be shown in case the user does not have access granted through the access control list configured with the acl_resource option. This option will be translated before being shown in the UI.


type: string

The id of an access control list a user must be granted access to to perform the transition.


type: string default: OroWorkflowBundle:Widget:widget/transitionForm.html.twig

When the display_type is dialog, this template will be used to create the page displayed in the front-end. The template being referenced here should extend the default OOroWorkflowBundle:Widget:widget/transitionForm.html.twig template.


type: string

The type of the widget to be shown when the transition is performed. This can be either dialog or page. When the page value is used, the form_options must be configured too.


type: map

Form options that will be passed to the created form type when the display_type option is set to page.


type: map


type: boolean

If true, this transition is hidden from the front-end.


type: boolean

If set to true, this transition can be applied when a workflow is not in a start step. There must be at least on transition having this option set to true if the workflow does not have at least one start step.


type: boolean

When the user is not allowed to perform this transition, it will not be displayed in the front-end when this option is set to true.


type: string

A notification message that will be shown in the front-end before the transition is performed. This message will be translated before being shown in the UI.


type: string default: OroWorkflowBundle:Workflow:transitionForm.html.twig

When the display_type is page, this template will be used to create the page displayed in the front-end. The template being referenced here should extend the default OroWorkflowBundle:Workflow:transitionForm.html.twig template.


type: string

The name of the step the workflow is transformed to (this must be one of the keys used in the steps option.


type: string

A transition definition to be applied to this transition.

Browse maintained versions:
Back to top

You will be redirected to [title]. Would you like to continue?

Yes No