[MGNLUI-6334] Behaviour of node name in new framework Created: 21/Oct/20  Updated: 09/Aug/21  Resolved: 27/Oct/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.3
Fix Version/s: 6.2.4

Type: Epic Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2.05h
Original Estimate: Not Specified

Issue Links:
Relates
relates to PAGES-424 Wrong page is marked as deleted Closed
causality
is causing MGNLUI-6502 Submodels should not be renamed when ... Accepted
supersession
supersedes MGNLUI-3439 SaveFormAction and SaveDialogAction c... Closed
Template:
Epic Name: nodeName
Acceptance criteria:
Empty
Release notes required:
Yes

 Comments   
Comment by Roman Kovařík [ 29/Oct/20 ]

For release notes:

  • apps generated from content type uses "name" instead of "jcrName" property (same as in the old framework)
  • JCR browser shows only real node names, regardless of presence of "jcrName" property
Generated at Mon Feb 12 09:35:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.