Add Field Widget Actions (FWA) support for FAQ Field using the faqfield_default widget.
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3566577. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1098 >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Description: </strong>Add Field Widget Actions (FWA) support for FAQ Field using the faqfield_default widget.<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>FAQ fields typically contain structured question-and-answer pairs that can be generated, refined, or expanded using AI. Currently, the FAQ Field rendered with the <code>faqfield_default</code> widget does not offer an in-widget way to trigger AI Automators.<br> This issue proposes adding Field Widget Actions (FWA) support for the FAQ Field + <code>faqfield_default</code> widget combination, using <code>modules/ai_automators/src/Plugin/FieldWidgetAction/Email.php</code> as reference implementation. The implementation requires the FAQ Field module (<code>faqfield</code>) to be enabled, as it provides both the field type and widget.<br> A simple way to test this is to configure an AI Automator that takes a block of text and generates relevant FAQ entries, storing the resulting questions and answers directly into the FAQ Field via the FWA.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Add a new FWA plugin for the FAQ Field when using the <code>faqfield_default</code> widget, modeled after <code>modules/ai_automators/src/Plugin/FieldWidgetAction/Email.php</code>.</li> <li>Declare a dependency on the FAQ Field module and ensure the FWA is only available when the FAQ Field type and widget are in use.</li> </ul> <p>- <strong>This issue was created with the help of AI</strong></p> > Related issue: [Issue #3572745](https://www.drupal.org/node/3572745) > Related issue: [Issue #3572751](https://www.drupal.org/node/3572751)
issue