Enhance the Public Marketplace by introducing support for Human Task Orchestration (HTO) and Decision Model and Notation (DMN) within blueprints. This initiative will enable the sharing of more advanced models, including comprehensive HTO and DMN use cases, which are currently limited or missing. By promoting linking over embedding, this update aims to facilitate easier updates, better management, and enhanced flexibility of forms and decisions.
User Problem 🤦
Currently, users are restricted by the embedded-only blueprint support in the marketplace, which limits the complexity and adaptability of shared models, particularly for advanced HTO and DMN applications. This limitation hampers the ability to maintain and update forms and decision logic without risking data loss or integrity. The new Zeebe User Tasks can only be linked.
User Stories 🧑🚀
As a process designer, I want to link forms and DMN decisions within my marketplace blueprints, so that I can easily update and manage these components without impacting the underlying process model.
As a developer, I aim to leverage advanced HTO and DMN use cases in my projects by accessing blueprints that incorporate these elements, enhancing my applications' capabilities and integration potential.
As a process designer, I want to use Zeebe User Tasks in my models that I share on the marketplace, requiring linked support for forms.
As a marketplace user, I want to understand which dependencies the selected process has.
As a marketplace user, I want to download a process blueprint with all its dependencies.
As a marketplace user, I want to be able to download blueprints that just contain HTO or DMNs as single asset.
As a developer, I am able to import process blueprints into process application folders.
Implementation 👷
Update the blueprint bundling mechanism to support linking of forms and DMN, moving away from embedding to enhance modularity.
Enhance the import link functionality within the SaaS offering to include robust support for forms and DMN, ensuring seamless integration and use.
Develop guidelines and best practices for marketplace contributors on how to create and share linked HTO and DMN elements.
Implementation DRI: @ev-codes
Value Proposition Statement 🚀
Enhance the Public Marketplace by introducing support for Human Task Orchestration (HTO) and Decision Model and Notation (DMN) within blueprints. This initiative will enable the sharing of more advanced models, including comprehensive HTO and DMN use cases, which are currently limited or missing. By promoting linking over embedding, this update aims to facilitate easier updates, better management, and enhanced flexibility of forms and decisions.
User Problem 🤦
Currently, users are restricted by the embedded-only blueprint support in the marketplace, which limits the complexity and adaptability of shared models, particularly for advanced HTO and DMN applications. This limitation hampers the ability to maintain and update forms and decision logic without risking data loss or integrity. The new Zeebe User Tasks can only be linked.
User Stories 🧑🚀
As a process designer, I want to link forms and DMN decisions within my marketplace blueprints, so that I can easily update and manage these components without impacting the underlying process model.
As a developer, I aim to leverage advanced HTO and DMN use cases in my projects by accessing blueprints that incorporate these elements, enhancing my applications' capabilities and integration potential.
As a process designer, I want to use Zeebe User Tasks in my models that I share on the marketplace, requiring linked support for forms.
As a marketplace user, I want to understand which dependencies the selected process has.
As a marketplace user, I want to download a process blueprint with all its dependencies.
As a marketplace user, I want to be able to download blueprints that just contain HTO or DMNs as single asset.
As a developer, I am able to import process blueprints into process application folders.
Implementation 👷
Update the blueprint bundling mechanism to support linking of forms and DMN, moving away from embedding to enhance modularity.
Enhance the import link functionality within the SaaS offering to include robust support for forms and DMN, ensuring seamless integration and use.
Develop guidelines and best practices for marketplace contributors on how to create and share linked HTO and DMN elements.
Stretch Goals (will likely require follow-up tickets)
:robot: This issue is automatically synced from: source