VBO: Execute Views bulk operation (one by one)¶
Available since: 1.0.0
Provided tokens
| Token | Description |
|---|---|
[event] |
The event. |
[event:view] |
The view config entity. |
[event:view:id] |
The view ID. |
[event:view:display_id] |
The display ID. |
[event:action] |
The action plugin. |
[event:action:plugin] |
The ID of the action plugin. |
[event:action:condig] |
An array with key value pairs of the configuration of the plugin. |
[event:entity] |
The currently processed entity. |
[event:entity:id] |
The entity ID. |
[event:entity:label] |
The entity label. |
[event:entity:type] |
The ID of the entity type. |
[event:entity:bundle] |
The bundle of the entity. |
[event:entity:langcode] |
The language code ID of the entity. |
[event] |
The event. |
[event:machine_name] |
The machine name of the ECA event. |
[session_user] |
The user account that dispatched the event, regardless if ECA is processing models under a different account. |
[entity] |
The entity of the event. |
[ENTITY_TYPE] |
The entity of the event under the name of its entity type. |
Fields¶
Operation name-
The operation name identifies this process and will show up in the bulk operations configuration form as selectable action. If you need custom access handling using the operation name, then make sure that the Views configuration is using the ECA bulk operations Views field plugin.
By using one-by-one execution (for each single entity), you have following tokens available:- [event:view] containing info about the used view
- [event:action] containing info about the executed action
- [event:entity] containing info about the entity in scope
Optionally restrict by view IDOptionally restrict by view display ID