Expand my Community achievements bar.

SOLVED

AEMaaCS - validation of components using globals

Avatar

Level 10

Using core components within AEM forms and I was trying to use the date before after for the date say end date, eg if end date is keyed in, it should be less than the start date but due to a bug that adobe has confirmed this would not work on core components. If I were to write a rule or rules how could I fail validation via script  to avoid moving to next panel or submit ?

globals.function.markasinvalid does not block submission 

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Employee

@NitroHazeDev Here is a reference for marking a field as invalid: https://github.com/adobe/aem-core-forms-components/pull/1356/files

 

Please note that - you would need to pick the latest core-components build - ver. 3.0.52 or greater for this support.

 

Thanks,

-Sudhanshu

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

@NitroHazeDev Here is a reference for marking a field as invalid: https://github.com/adobe/aem-core-forms-components/pull/1356/files

 

Please note that - you would need to pick the latest core-components build - ver. 3.0.52 or greater for this support.

 

Thanks,

-Sudhanshu

Avatar

Level 1

Also, if you are using AEMaaCS then this bug has been fixed in July release and dates can be compared using rule editor: 
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/ma....