Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
In user notification plugin, I identify this code :
} else { String tempEmailMessage = emailMessage; if (emailMessage.contains("#assignment.link#")) { tempEmailMessage = tempEmailMessage.replaceAll(StringUtil.escapeRegex("#assignment.link#"), StringUtil.escapeRegex(tempLink)); } else { tempEmailMessage = emailMessage + "\n\n\n" + tempLink; } formattedMessage = AppUtil.processHashVariable(tempEmailMessage, wfAssignment, null, replace); //TODO: consider replace the next line to platform-wise support parsing of hash variables in the value returned by another hash variable formattedMessage = AppUtil.processHashVariable(formattedMessage, wfAssignment, null, replace); email.setMsg(formattedMessage);
Is my code in the TODO case ?
Thank you !
In fact, I have already changed the expression with quotes to have :
#exp.'{assignment.processName?expression}'.isEmpty()?'empty':'{assignment.processName}'#
And the response is
{assignment.processName}
which version are you using?
I use the last one.
7.0.34
add single quotes for the else statement
from
#exp.'{assignment.processName?expression}'.isEmpty()?'empty':{assignment.processName}#
to
#exp.'{assignment.processName?expression}'.isEmpty()?'empty':'{assignment.processName}'#
Hi,
I have a problem with hashvariable in notification.
You can see below :
#assignment.processName# = "Départ d'un agent"
If I use #assignment.processName# alone, no problem.
If I use the expression #exp.'{assignment.processName?expression}'.isEmpty()?'empty':{assignment.processName}#, the hashvariable assignment.processName is unknow.
What's wrong ?