>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3549250. --> Reported by: [a.dmitriiev](https://www.drupal.org/user/3235287) Related to !915 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Issue <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-13"><a href="https://www.drupal.org/project/drupal/issues/3537773" title="Status: Needs work">#3537773: Config action to set a third party setting of a display (form or view) component</a></span> adds the possibility to setup third party settings for the entity (form and view) displays. As it can be part of Drupal core not earlier than 11.3 is released, it was decided to include the same simplified config action to Field Widget Actions module to not wait for core changes and also for backwards compatibility. The config action will be limited to third party settings from "Field Widget Actions" only, to not conflict with core functionality.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Use <code>hook_config_action_alter</code> to add the new action dynamically in case it doesn't exist in core.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Implement this in Field Widget Actions submodule, limit functionality only to entity form displays and provider should be limited to field widget actions only.</p> > Related issue: [Issue #3537773](https://www.drupal.org/node/3537773)