[BLOSSOM-274] Dialog creation is no longer supported in custom content apps Created: 13/Jun/20  Updated: 01/Jul/20  Resolved: 15/Jun/20

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 3.4.2
Fix Version/s: 3.4.3

Type: Bug Priority: Neutral
Reporter: Mikaël Geljić Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
caused by BLOSSOM-272 DialogCreatorDefinitionDecorator is w... Closed
is causing BLOSSOM-277 DOC: Update Blossom release page for ... Closed
dependency
depends upon MGNLUI-5964 Expose running app contexts via AppCo... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:
Sprint: Maintenance 11
Story Points: 2

 Description   

Following up on SUPPORT-11346, BLOSSOM-272 was too hasty/too strict in restricting Blossom dialogs to only old & new Pages apps, with no way to re-enable support for custom M5 content-apps.

App names have been used primarily due to missing APIs exposing current AppDescriptor and its type (old vs. new, ContentAppDescriptors vs. others).
Now we've decided to lift this limitation in UI Framework - see MGNLUI-5964.



 Comments   
Comment by Federico Grilli [ 15/Jun/20 ]

mdrapela/docuteam this fix requires Magnolia 6.2.2 as it relies on MGNLUI-5964 which exposes running and active app contexts via AppController

Generated at Sun Feb 11 23:31:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.