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

second line in a message box

Avatar

Level 3

Hi guys,

i hope you can help me with this.

I want to create a second line in a message box.

I found out in javascript that i use for that \n somewhere in the xfa.host.messageBox("") but i tried everything out, and it still doesnt work.

Can you help me with that?

Thank you in advance!!

Diana

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Does your script look similar to this and did you select the JavaScript option for the language?

xfa.host.messageBox("This is a message. \nThis is a new paragraph. \n\nHere is a new paragraph with two spaces.", "This is a title", 3, 0);

View solution in original post

4 Replies

Avatar

Correct answer by
Former Community Member

Does your script look similar to this and did you select the JavaScript option for the language?

xfa.host.messageBox("This is a message. \nThis is a new paragraph. \n\nHere is a new paragraph with two spaces.", "This is a title", 3, 0);

Avatar

Level 3

THANK YOU SO MUCH!!!

You are the best!!!

Just one short question.

is this possible to have a two space break? here I applied my code but it doesnt want to do this.

xfa.host.messageBox("!!!Susscessfully submitted!!!. \n\nTo proceed to PRINT VIEW, click YES!. \nTo CLOSE the form, click NO!."

, 3, 2);

Thanks,

Diana

Avatar

Former Community Member

Yes, you can just add another \n for each break.

Avatar

Level 3

Thank you!!!!

It works perfect!!!!!

Diana

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