-
Bug
-
Resolution: Won't Fix
-
Neutral
-
None
-
5.2.4
-
None
Consider the following scenario:
- create a contentApp with multiple subApps
- each subApp got his own workbench with distinct trees & nodetypes
There is no way to reference one of the subApps browser dialogs. We can only reference the contentApp by property 'appName' within a external dialog (e.g LinkFieldDefinition), but subApps are not considered by this approach. By Default, the first subApps browser dialog is displayed.
A work-around is to split the contentApp into multiple contentApps, one for each subApp.
Acceptance criteria
- duplicates
-
MGNLUI-2111 LinkFieldDefinition ignores the targetTreeRootPath property
- Closed