Generalize behaviour of FWA with Automators
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3577050. -->
Reported by: [a.dmitriiev](https://www.drupal.org/user/3235287)
Related to !1283
>>>
<p>[Tracker]<br>
<strong>Update Summary: </strong>[One-line status update for stakeholders]<br>
<strong>Short Description: </strong>[One-line issue summary for stakeholders]<br>
<strong>Check-in Date: </strong>MM/DD/YYYY<br>
<em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br>
[/Tracker]</p>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>At the moment each field widget action in ai_automators module (that use automators) is using its own custom code to manipulate the form element data. This leads to a lot of different approaches and doesn't always allow using multivalue fields or have some problems because of the data structure changes between versions of 3rd party modules that provide the field types.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Generalize approach of FWA automators and adjust the base class in order to have a solution that fits all plugins.</p>
<h3 id="summary-ai-usage">AI usage (if applicable)</h3>
<p>[ ] AI Assisted Issue<br>
This issue was generated with AI assistance, but was reviewed and refined by the creator.</p>
<p>[ ] AI Assisted Code<br>
This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision.</p>
<p>[ ] AI Generated Code<br>
This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human.</p>
<p>[ ] Vibe Coded<br>
This code was generated by an AI and has only been functionally tested.</p>
issue