>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3543083. --> Reported by: [d34dman](https://www.drupal.org/user/751698) >>> <p>A detailed report is published here : <a href="https://project.pages.drupalcode.org/flowdrop/meta/learnings/experiments-with-modeler_api/">https://project.pages.drupalcode.org/flowdrop/meta/learnings/experiments-with-modeler_api/</a></p> <h2>Learnings:<br> </h2> <h3>Success</h3> <ol> <li><strong>Abstraction validated with POC:</strong> The Modeler API provides sufficient abstraction. The proof of concept shows that FlowDrop UI can visualize an ECA workflow generated with the BPMN.io modeler.</li> <li> </ol> <h3>Risk</h3> <ol> <li><strong>Integrated configuration editing not yet available</strong> Updating configuration within the workflow is not yet exposed by the Modeler, which limits FlowDrop UI's ability to provide integrated configuration management.<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/flowdrop/issues/3543256" title="Status: Closed (won't fix)">#3543256: In-workflow configuration editing not yet supported by Modeler</a></span> </li> <li><strong>Risk of becoming a themed variant of BPMN.io</strong> With the current Model Owner, FlowDrop UI could effectively become a themed variant of the BPMN.io modeler. If editing is off-loaded into modal forms, FlowDrop UI's main contribution may be a different drag-and-drop experience and styling.<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/flowdrop/issues/3543257" title="Status: Closed (won't fix)">#3543257: Avoid FlowDrop UI becoming a themed variant of BPMN.io</a></span> </li> <li><strong>Hierarchical editing UX is complex:</strong> The user experience when editing hierarchical agent workflows is complex and not ideal.<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/flowdrop/issues/3543258" title="Status: Closed (won't fix)">#3543258: Improve UX for editing hierarchical agent workflows</a></span> </li> <li><strong>Limited net UI benefit today:</strong> Even with the BPMN.io modeler, the UI currently provides limited advantages; users still spend most of their time in Drupal's Edit form configuring the agent.<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/flowdrop/issues/3543259" title="Status: Closed (won't fix)">#3543259: Limited UI benefit in current FlowDrop editor</a></span> </li> </ol> <h3>Notes</h3> <ol> <li><strong>Architecture limited by Model Owner</strong> Limiting FlowDrop capability to the BPMN model (and thereby the ECA ecosystem in general) is a double-edged sword. You benefit from the large number of plugins, but you also have to respect the architecture and its limitations.<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/flowdrop/issues/3543260" title="Status: Closed (won't fix)">#3543260: Architectural constraints imposed by BPMN model owner</a></span> </li> </ol> <h3>Questions</h3> <ol> <li>Nested agent creation from a single model? Can the AI Agent Model owner provide nested agent creation from a single model?<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-5"><a href="https://www.drupal.org/project/flowdrop/issues/3543261" title="Status: Closed (won't fix)">#3543261: Investigate support for nested agent creation in AI Agent Model</a></span> </li> </ol>