Expand my Community achievements bar.

Adobe Summit 2025: AEM Session Recordings Are Live! Missed a session or want to revisit your favorites? Watch the latest recordings now.
SOLVED

New CF Editor Custom Validation

Avatar

Community Advisor and Adobe Champion

Hello,

has anyone developed a custom validation extension for the new CF editor? I don't want to create a custom field, just add validation to an OOTB field. I checked the docs but I don't see any API for validation available: https://developer.adobe.com/uix/docs/services/aem-cf-editor/api/

I have the following use-case: two multifields, if one contains X items, then the other one needs to contain X items or the validation should fail and show an error to the editor.

 

Thanks,

Daniel

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @daniel-strmecki 

I'm not sure if there are alternative approaches, but validation can be enabled directly within the same React extension used for the fields.


Regards
Albin
https://myprofile.albinsblog.com/

View solution in original post

4 Replies

Avatar

Community Advisor

Hi @daniel-strmecki

I was exploring multifield support in the new Content Fragment Editor, and the details are captured in this post. You should be able to extend it based on your use case, including support for validation.- https://medium.com/tech-learnings/aem-cloud-service-composite-multifield-in-content-fragments-editor...

Regards

Albin

My Profile - Albin Issac

Avatar

Community Advisor and Adobe Champion

Hi @Albin_Issac,

thanks for sharing. I read your post, but you are adding a custom multifield, which is not something I want to do. I only want to add custom validation to an OOTB multfifield. Is there an extension point available to just add custom validation?

 

Avatar

Correct answer by
Community Advisor

Hi @daniel-strmecki 

I'm not sure if there are alternative approaches, but validation can be enabled directly within the same React extension used for the fields.


Regards
Albin
https://myprofile.albinsblog.com/

Avatar

Community Advisor and Adobe Champion

Thanks for confirming my assumption. I will raise a feature request for it.

 

BR,

Daniel