- Issue created by @mindaugasd
- π±πΉLithuania mindaugasd
In my case filling a single field on many nodes (no chaining).
- π±πΉLithuania mindaugasd
Mostly I am looking forward to use this feature with AI β module automator's. In the meantime will do it programatically: db query, a batch and AI module's abstraction API.
- π±πΉLithuania mindaugasd
Renamed "interpolator" with "automator" in description.
- π¬π§United Kingdom yautja_cetanu
Yes very good idea. This is similar to what Martin says of there being UI triggers so similar to widgets except in this case the UI trigger is a bulk operation
- πΊπΈUnited States Kristen Pol Santa Cruz, CA, USA
We are doing some issue management housekeeping and adding/removing components.
We are removing the "Code" component and want people to categorize issues with the best module/submodule component.
Moving this issue to "...to be triaged" as I'm not sure where the best place is.
If we have a new project to move this to, we can optionally do that as a secondary step.
See π Update AI module project components Active for more details.
- π©πͺGermany marcus_johansson
So this is how it should work to make sense.
Add a new processor called "Views Bulk Operation".
When an automator has this processor, it will becomes a deriative action available for VBO.
That Automator will ever only run on VBO action and an entity selected.
Add a possibility for processors to have subforms.
Let the user decide per field if it always overwrites the value or only sets if the value is set.