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
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Manage and author Custom Error message for Modal component

priya3
Level 2
Level 2

Hi,

 

We have a requirement to store UI validation Message and  Backend error message(displayed as modal)  in AEM so they are authorable. 

These error messages will be used across pages in site . Can someone suggest best way to manage it . Is it advisable to have a page dedicated for managing error messages where content authors can edit and manage error messages or create experience fragments for group of error messages to be referenced.

This is a React Application where the content is passed as Json to Front End.

1 Accepted Solution
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

The experience fragment approach looks fine, you can use some selector lets says /content/exper...../button-invlaid.content.html to remove unnecessary content,

You can try to create an error container component with another experience fragment button-erorr.modal.json which can refer above experience fragment as a group and messages can be grouped and reused.   

View solution in original post

3 Replies
KiranVedantam1992
Community Advisor
Community Advisor

Hi @priya3,

 

For setting the values globally or site-specific, you can use context-aware-configuration functionality in AEM. With this, you create a page with wcm.io Context-Aware Configuration Editor template, author your values and access them across the site.

Refer:

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/context-...

 

Hope this helps.

 

Thanks,

Kiran Vedantam.

Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

The experience fragment approach looks fine, you can use some selector lets says /content/exper...../button-invlaid.content.html to remove unnecessary content,

You can try to create an error container component with another experience fragment button-erorr.modal.json which can refer above experience fragment as a group and messages can be grouped and reused.   

View solution in original post