cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Using Workflow Variables in Build String

Hi All

 

To simplify the maintenance of my workflows I like to use email templates for the complete workflow communication. This means I have a document library where the email templates are stored as HTML files. Inside these HTML files I'm using variable content like {ItemProperty:Creator} etc.

 

This means, I'm reading the content of the HTML file into a workflow variable and then I'm using a "Build String" action to replace the tokens.

 

This works perfectly if I'm using only item properties {ItemProperty:XXX}. Since not all properties (i.e. Creator's display name) are accessible on item level, I need to use workflow variables as well.

 

Unfortunately this does not seem to work: As soon as I'm trying to use a workflow variable like {WorkflowVariable:CreatorDisplayName} the token is not resolved anymore. Setting the "Parse for tokens twice" does not help.

 

Does anyone have an idea what I'm doing wrong or are nested workflow variables never parsed?

Thanks for your help in advance.

Regards,

Martin

Labels: (1)
0 Kudos
Reply
3 Replies
Workflow Hero

Re: Using Workflow Variables in Build String

Hi NintexEnthusiast,

first thing to check is whether you are on the latest build of Nintex Workflow.  Both NW 2010 and 2013 just recently had a new release, so it would be a good idea to check that out.

Also, if it's easily reproducible, you may want to shoot an email to support@nintex.com .   If it's a legitimate bug, then it would need to be raised as a bug to the development team.

cheers,

Vadim

0 Kudos
Accept as Solution Reply
Not applicable

Re: Using Workflow Variables in Build String

Hi Vadim

 

Many thanks for your answer. I found out that the problem is not on the Nintex site but on the "naming standards" for workflow variables we're using.

 

To have an indicator what datatype a variable is we're using an abbreviation behind the name in parentheses, i.e. if I want the display name the variable could be called "CreatorDisplayName (SLOT)", where SLOT stands for single line of text.

 

Now Nintex doesn't seem to recognize a nested workflow variable if its name contains blanks. I don't know if this is intended or a bug, but if I use variable names without blanks then it's working as expected.

 

Cheers,

Martin

0 Kudos
Accept as Solution Reply
Workflow Hero

Re: Using Workflow Variables in Build String

Hi Martin,

It sounds like it's an issue with the way Nintex Workflow is parsing token.  I'd recommend you pass that to support@nintex.com in case it is an issue and the development team needs to look into it.

cheers,

Vadim Tabakman

0 Kudos
Accept as Solution Reply