Add UI/UX to add multiple automators on a field

Switching to the correct tag

Add skill tags for issue discovery

I think this form is actually the wrong spot for these, the field form is for the field config (i.e. field.field.node.article.field_image.yml), however, Automators are their own config entity (i.e. ai_automators.ai_automator.node.article.field_image.default.yml)

There is technically already an admin interface here at /admin/config/ai/ai-automators/ai-automator:

→

Why not utilize this to handle automators and just link to it from the field config form? Given the idea seems to be to allow multiple automators on a field instance, you could also set this up similar to image styles in which each automator chain from the next using weight to determine order?

I'm envisioning something like this, where you would first pick your entity type and field, once saved the entity/field cannot be changed, only deleted, but then the automators become available based on the field type, as many as you want can be added and changed, also allowing the result to provide context to the next in line:

→

Thoughts?

I like the suggestion. The first screenshot is nasty-long. As well as separating out the automators, a simple link from file Operations would be good.

Ok, I'm going to start down this route and see if any snags appear

Another idea, maybe this deserves its own tab on field edit page? Like a separate page "Automators" with its own link that can also go into operations dropdown?

@a.dmitriiev I like that, I will add after the refactor on the plugins, this is a big ol rat's nest with the automators vs automator types

I do think having the simple option to describe how to fill out a field via AI on the field configuration form is good UX/UI - based on working with three different F500 companies, this was the only way we could enable them to work with chainable AI and understand how the field configuration connected to how the AI generated the field.

They had none-developer domain specialists from their companies sitting and setting this up for them and got it working. However the only thing we did compare to was Field UI + ECA, that is a lot more complex.

I do like the new ux from @b_sharpe, it reminds me of how Field Validation module does work, which is easy once you understand the workflow.

There is an reordering page/tab already - it might make sense to add the add button there, see screenshot:

→