AEM 6.3 clientlibs : make foundation-ui adapter's property value configurable rather than hardcode in clientlibs | Community
Skip to main content
cquser1
New Participant
December 17, 2017
Solved

AEM 6.3 clientlibs : make foundation-ui adapter's property value configurable rather than hardcode in clientlibs

  • December 17, 2017
  • 2 replies
  • 925 views

Hi ,

My custom clientlib file is something similar to Experiencing Adobe Experience Manager - Day CQ: AEM 6 SP2 - Touch UI Extend Site Admin Page Properties Show Submit Confi…

In this article, the pop-up/confirmation dialog has two properties :

id: "CANCEL",

text: "CANCEL",

and

id: "SUBMIT",

text: "SUBMIT",

We do not want this[basically referring to CANCEL and SUBMIT here] to be hardcoded, but to be fetched from say a config file or something of that sort.

Any thoughts on how this can be done.

Any pointers/code snippet/reference articles will be helpful.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by edubey

From the same JS

1. Make a ajax to jcr node where those configurable properties will be stored

2. Replace the values hardcoded in that script

Remember, executing script code to show the pop (submit/cancel) should be callback of the result from step #1.

2 replies

cquser1
cquser1Author
New Participant
December 18, 2017

Hi,

Thank you for your reply.

To make this configurable, we made use of i18n to place the values and fetch from it by the below.

Granite.I18n.get("property"); in the js.

edubey
edubeyAccepted solution
New Participant
December 17, 2017

From the same JS

1. Make a ajax to jcr node where those configurable properties will be stored

2. Replace the values hardcoded in that script

Remember, executing script code to show the pop (submit/cancel) should be callback of the result from step #1.