-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
DevX 11, DevX 12
-
5
Enable ContentTypes to be used on SaaS.
Background: NORSU-126
Details:
Â
Acceptance Criteria
- Only fields already existing on SaaS must be supported in this ticket. We should create followup ticket for the fields that are not yet implemented by Nuclear team.
- Should not register a new custom multi construct somewhere instead of "ui-framework-jcr", see uiÂ
- Create new content type submodule for norsu
- Check if we can load form template from another config path
- Should allow only 1 content type enable at one time, ex: jcr or norsu
Â
Proposal branch:
- is depended upon by
-
MGNLCT-215 Support auto create workspace content types on Norsu when autoCreate is enable
- Closed
-
MGNLHOOK-174 Replace with ConfiguredModelDefinition since content type 2.0
- Closed
-
MGNLCT-198 [Test] basic field based on content types on Norsu
- Closed
-
MGNLCT-205 Link field based on content types on Norsu
- Closed
-
MGNLCT-206 Composite field based on content types on Norsu
- Closed
-
MGNLCT-208 [Test] richtext field based on content types on Norsu
- Closed
-
MGNLCT-226 Bring all actions that support from 1.2 version to norsu content app
- Closed
-
MGNLCT-269 Multi field based on content types on Norsu
- Closed
-
MGNLGQL-115 Replace with ConfiguredModelDefinition since content type 2.0
- Closed
- to be documented by
-
MGNLCT-309 DOC: ConfiguredModelDefinition since content types 2.0
- Closed
1.
|
Implement | Completed | Oanh Thai Hoang | |
2.
|
Investigate feature tag to see if content type can apply or not | Completed | Oanh Thai Hoang | |
3.
|
Review | Completed | Jaroslav Simak | |
4.
|
piQA | Completed | Jaroslav Simak | |
5.
|
QA | Closed | Dai Ha | |
6.
|
Create tickets for norsu ui field fields that need to tested/implement based on content type | Closed | Oanh Thai Hoang | |
7.
|
Fix rv | Completed | Oanh Thai Hoang |