nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WFM: multiple vars for value

Adam Stoller

Environment[indent]TS 7.3.1 on W2K8 64-bit[/indent]
Issue[indent]I have a Configurable Variable (

SYS_ADMINS

) and a Script Variable (

REVIEWERS

)[indent]The latter essentially uses part of the value of $IW_BRANCH to augment the name of the reviewer group, for example:

Find more posts tagged with

Comments

Rick Poulin

I think you had the right idea with the SCRIPT variable to comma-join the values. The issue you're running into with your replacements is that the "DOMAIN\userid" string is interpreting the \u before the .replace occurs (so no combination of replace() will help). I can't think of any better answer than to suggest you either extend the OOTB Java class, or use a task before the email to compute and set the value of Recipients... unless anybody knows of a way to interpret characters as literals in JavaScript? (similar to q() in perl)

Adam Stoller

I think you had the right idea with the SCRIPT variable to comma-join the values. The issue you're running into with your replacements is that the "DOMAIN\userid" string is interpreting the \u before the .replace occurs (so no combination of replace() will help). I can't think of any better answer than to suggest you either extend the OOTB Java class, or use a task before the email to compute and set the value of Recipients... unless anybody knows of a way to interpret characters as literals in JavaScript? (similar to q() in perl)

I meant to post back on Friday, but was running late.
Yeah - I figured out that by the time I was getting my hands on "$IW_USER" the backslash had already been interpolated and removed, so there was no way for me to latch onto it.

So I ended up hard-coding the string "IW_USER" (no '$') into the task variable and have an External Task that runs at the beginning of my workflow that takes care of fixing the task variable value on all relevant tasks (it takes care of expanding groups into constituent members - since the LiveSite email class apparently doesn't handle that, and (for good measure) does duplicate elimination ;-)

I'll leave the thread open for a day or two in case anyone else wants to comment on it.