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

App Alert

Avatar

Level 4

Hi all:  In Adobe Acrobat, I could create a button with an app. alert that would give the users some sort of information or instruction.  Is this possible in Adobe LiveCycle Designer?  How would one create an button with an app. alert message to instruct users how to use a specific item on the form?

Any assistance would be greatly appreciated.

I have Adobe Acrobat 8.0 Professional

Connie

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Its pretty much the same thing. Create a button and on the click event make sure the programming language is set to javascript. Then enter the line of code:

app.alert("This is my message!")

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Its pretty much the same thing. Create a button and on the click event make sure the programming language is set to javascript. Then enter the line of code:

app.alert("This is my message!")

Avatar

Level 4

Thanks!  It worked like a charm.

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] ----