[MGNLCT-71] The 'required' property can be used on CT model properties Created: 13/Sep/18  Updated: 19/Oct/18  Resolved: 25/Sep/18

Status: Closed
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Oanh Thai Hoang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.25d
Original Estimate: Not Specified

Attachments: PNG File QA.png    
Issue Links:
Relates
relates to MGNLCT-29 Validation for model properties Open
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)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Content types Developer Preview
Sprint: Saigon 154
Story Points: 2

 Description   

User story:

As a Business Analyst / Developer, I can define fields to be required in my content type, so that users must fill in that property in the app.

 

Acceptance Criteria

  • If 'required:true' is added to a content type model property, then the field in the editor subapp must be supplied in order to save changes in the app.


 Comments   
Comment by Oanh Thai Hoang [ 25/Sep/18 ]

This is example how to configure required property

datasource:
  workspace: config
model:
  properties:
    - name: title
      required: true
Comment by Dai Ha [ 25/Sep/18 ]

Verified latest bundle with magnolia 5.7.2-SNAPSHOT, with new "required:true" property defined, field is required to complete actions on app.

Generated at Mon Feb 12 00:36:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.