Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Custom validation logic in Content Fragment Model

Avatar

Level 4

08-02-2021

Request for Feature Enhancement (RFE) Summary: With more and more increased usage of Content Fragment for Headless applications (who consume JSON CFs from AEM), there is plenty of requirement where application teams need more control on each fields in Content Fragment. Currently there is no option to add custom field validations, add javascript validations or Regex in Content Fragment.
Use-case: Content Authors make mistake where they save and publish critical data in CFs. Need custom validation logic option to be added in each datatype so that we can add more checks.
Current/Experienced Behavior: No validation logic in datatypes except very basic like Required.
Improved/Expected Behavior: Validation logic for each datatypes and among different datatypes in each content fragment model.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.5
Customer-name/Organization name: Manulife
Screenshot (if applicable):  
Code package (if applicable):  
3 Comments

Avatar

Employee

20-02-2021

Hi @Mayukh007 

Thanks for submitting this improvement idea. It seems to be similar to an idea that has already been submitted in this thread. Please check and let us know.

Status changed to: Needs Info

Avatar

Employee

28-03-2021

Setting the status accordingly once the issue is under investigation/Triage by the product team.

Status changed to: Investigating

Avatar

Employee

26-04-2021

Starting AEM on Cloud Service Version 2021.01, field level validation options have been added. At the time of writing, there is, for a text field:

  • E-Mail
  • URL
  • Custom (allows to provide a regex to validate)

For other data types, such as Content Reference allow to configure file type and image size constrains.

 

The plan is to bring this capability in 6.5.10.