You are browsing the documentation for version 4.1 of OroCommerce, OroCRM and OroPlatform, which is no longer maintained. Security Support ends in January 2023. Read version 5.0 (the latest LTS version) of the Oro documentation to get the updated information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
Both the entity and field options must not be used directly under the
entity_config key, but a scope key must be used as an intermediate mapping key:
1 2 3 4
# src/Acme/DemoBundle/Resources/config/oro/entity_config.yml entity_config: demo_scope: # ...
This scope is later referred to with the
defaultValues option of the
Options defined under the
entity key can be applied on the class level using the
annotation. Refer to the field option to define config
options that can be applied to individual class properties.
This options can be used to configure some global form options. This is mostly useful for adding
custom blocks to the form. This is done with the
block_config option which is a map in which
the keys are block names and the values are the options that configure the custom blocks:
The block title which will be passed to the translator before being displayed.
The block’s priority which is used to control the order in which form blocks are rendered.
The keys of this map are the names of your custom config options. The values for each option are used to control how the options are presented in the UI that lets the modify configuration values:
Validation constraints that must be applied to values that are submitted by the user. Have a look at the validation constraints reference section of the Symfony documentation to see how to set up validation constraints.
Configures the form field that is used to make the option value configurable:
string)A form type name.
map)Additional options that will be passed to the form type through the form builder.
This map configures how the option will be presented in the data grid views in the entity management interface. Have a look at the columns option of the datagrid configuration reference for all available options.
Some basic options are grouped under this key:
false)Changes to the option value will be tracked when the field is audited.
false)When enabled, values of this option will be indexed which may increase performance when you query for particular values of the config option.
integer)This controls the order in which fields are rendered when they are modified. Fields with a higher priority are rendered first.
false)By default, the values configured by the user will be treated as is. They will be passed to the translator if the
translatableoptions is enabled.
Under this key, options that are applied on the field level will be configured:
You can use the same options to configure entity fields that you can use when configuring options for an entity class.