I have seen this issue. If you use the same variable and modify its
values in a setvalue operation within gateway, it will give you this
issue because of some race-conditions.Is it mandatory that you use the
same variable? Any business logic? I would advise using different
variables within gateway and putting a logic after gateway to handle the
data coming from different variables.
You can always append new nodes which has a unique tag name (this won't
get overwritten).Which means, each time when you add a node, it should
have tag name which has not already present within the same parent
node.Later you can replace the tag name with the actual name by using
XSL transformations.I've tried this in one of my project and worked
I got this sort of working. I used a 2 step process.Using Word, I
created a "blank" PDF. I used a greenish background color on the Word
doc so I could see it.Use DDX to create a PDF with the Watermark I want.
I am doing this really only to provide the background color.The content
of the StyledText is generated on the fly from user input, so I can't
"hardcode" the size.
This is line 1 of my watermark with a background color This is
line 2 of my watermark with a background color This is line...
One of the major internal changes of the Process Editor is to base its
graphic manipulation on a Flash based authoring experiance.
Additionally, the periodic background commuication with the server has
been largely removed. Your experience editing large process maps with
ES2 should be substaintially better than it was with the 8x product.
Steve ... Yes, I had tried wrapping my index in a number() function. And
to make sure that wasn't the issue, I hard coded the number  and it
still didn't work.Marcel ... Yup. I just built a DSC to work around the