Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 261:metamodelstrategy [2026/04/15 01:02] – Meier, Erich | 261:metamodelstrategy [2026/04/20 17:08] (current) – [Unified Configuration Compatibility Mode] Goetz, Sebastian | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| This new strategy will be implemented with the **next Stages release 26.2**. We share this strategy already with this release to enable our customers to adjust accordingly in a timely manner. | This new strategy will be implemented with the **next Stages release 26.2**. We share this strategy already with this release to enable our customers to adjust accordingly in a timely manner. | ||
| - | ====== Unified Configuration Best Practice | + | ===== Unified Configuration Best Practice ===== |
| The **Unified Configuration Best Practice** will represent a clearly structured and consistent version of the Unified Configuration that reflects our best methodological recommendations for process modeling. | The **Unified Configuration Best Practice** will represent a clearly structured and consistent version of the Unified Configuration that reflects our best methodological recommendations for process modeling. | ||
| Line 12: | Line 12: | ||
| * Customers using this standard metamodel will receive a “state‑of‑the‑art” metamodel with every release, ensuring optimal process modeling in Stages. | * Customers using this standard metamodel will receive a “state‑of‑the‑art” metamodel with every release, ensuring optimal process modeling in Stages. | ||
| - | ===== Unified Configuration | + | ===== Unified Configuration |
| - | The **Unified Configuration | + | The **Unified Configuration |
| Since existing processes were modeled using these elements, continued metamodel support is required. | Since existing processes were modeled using these elements, continued metamodel support is required. | ||