Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Configuration parameter in LC ES

Avatar

Former Community Member

Hi all,

I have a simple question ... In ES2 and ES2.5 we can define variables as configuration parameter, which is very very useful.

I'm asked to do a project on livecycle ES (8.0), with Workbench ES and after reading a lot of documentation, it seems that this feature was not available in this version.

So my question is : Is there a way to use variables as "configuration parameters" in LCES ? If not what was the common workaround ?

Regards,

Thomas

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi all,

I finally managed to do what I wanted. Since I'm using a WatchedFolder as endpoint for this process, I defined an input string variable "myPath". When I create the WatchedFolder endpoint, I set this value to literal with the value I need. This way it's always available and editable through the adminui !

Hope this helps,

Thomas

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Hi all,

I finally managed to do what I wanted. Since I'm using a WatchedFolder as endpoint for this process, I defined an input string variable "myPath". When I create the WatchedFolder endpoint, I set this value to literal with the value I need. This way it's always available and editable through the adminui !

Hope this helps,

Thomas

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----