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

Whitespaces in notification emails

Avatar

Level 3

Hello,

we've just noticed that (I suppose since LC ES SP 3) no notification email seems to contain any whitespace (LC ES running on Win2K3, JBoss, MSSQL). I'm 100% sure that this has been working before SP3 was applied.

Is there any fix to solve this issue, or a way to work around it? Or maybe we're doing something wrong here?

Thank you very much,

Steffen.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

So there is no confusion, ask for the latest SP3 hotfix for the email dsc component.  This is part of base LiveCycle and is also used by Process Management.

View solution in original post

2 Replies

Avatar

Former Community Member

Hello Steffen,

Ah, that is the problem of Adobe after SP3 is applied. Contact Adobe support to get a patch to fix that problem with type of email such as Outlook, Lotus, etc.

Hope it helps.

Han Dao

Avatar

Correct answer by
Former Community Member

So there is no confusion, ask for the latest SP3 hotfix for the email dsc component.  This is part of base LiveCycle and is also used by Process Management.

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