Variables Truncate after User Action

That sounds scary - what variables? What LSF version are you on?

Yes, non-persistent variables will often clear after a Branch or a UserAction. If you need a query's values throughout the life of your flow you should assign them to persistent variables.

The one I am having an issue with is a Message Builder Variable . . . It collects the data just fine through the first UserAction, but if I reference it after this, only the first line of data appears. The message builder collects Requisition Lines and presents them in an HTML table within an email. David, is there a way to assign a Message Builder Variable to another variable? It won't work within a string type variable, I already tried that. We are on 9.0.1.9 Technology.

That I haven't seen. I've seen the MsgBuilder variable limited to 250 characters and I've seen it where the log warns that you've exceeded 250 characters but it still keeps the value. You should be able to define a string variable and use it in a MsgBuilder. The only advantage to using a MsgBuilder is that it keeps you from having to reference the original variable in the content window.

You could try using an Assign var=var+newstring and that should work as well. I've used a MsgBuilder to build an HTML table of data before so that shouldn't be the issue. You can email your flow to me (david@consultdavidw.com) and I'll look at it to see if anything obvious jumps out.

I define my msg variables as strings in the Start node. Try that if yours are not set up that way.

FYI
I have experienced issues with message builder in regards to length and at times it cut off part of the variable. I decided that if I was going to capture anything long that I would just store it in a file using the file node. Since making the change I've haven't had any issues.

Not sure if I'm jumping into this late or not, or completely understanding, but here's my input. Variable values longer than 250 characters are truncated when they are persisted, which happens when a flow stops at a user action. This is whether the variable is result from a query, created as part of the flow, or, in what it sounds like is your case, the msg builder variable itself. What you have to do if you are building a long message (i.e. an HTML table of requisition lines), after EACH user action, you have to look up the requisition variables again using DME query, and execute the message builder node. Yes, after EACH user action, the variables need to be refreshed. It's a little bit of a pain in that you have multiple copies of a given node if you have multiple approval levels and user actions, but that's been my experience.

Robert, you are officially my hero! The suggestion to use File Access Nodes was the way to resolve this. I even checked out your example from Cue where you build an HTML table and attach it an email. Thanks everyone, this has been very helpful.

I have the same problem with MSGBuilder truncating the variables after the first time I use the variable in the email.

I had a case open a while ago. They know it's a problem.
JT 334081
KB 1340383
212723 - processflow useraction email notification
MsgBuilder Missing data
Resolution JT is not available yet
Since this is a priority 3 fix it may be a little while before Development gets a fix for this issue.


My MsgBuilder stores Line items from a Requisition.
The First Level Approver is Emailed a Notice of Pending Req Approval.
(Work Unit is Created.)
First email (Notice of Pending Req Approval ), Has all Line Items Stored from MsgBuilder.
(With Line Item Number)

Using the same MsgBuilder variable
2nd email, Notice to second Level Approver Does not have all of the Line Items and the Line Item Number is replaced by a Letter?
3rd email, (Notice to requester that Req was approved, Does not have all of the Line Items and the Line Item Number is replaced by a Letter?
The Work unit log file shows all of the Line items in MsgBuilder.

I will have to create an attachment to include all the data.
The approvers would rather just see the info in the email (via Smart Phone) rather than open an attachment.

I would not expect that it will get fixed, since processflow goes away with v10, and is replaced with Process Automation.
My solution when building a long message (i.e. an HTML table of requisition lines) is to just look up the requisition variables again using DME query before executing the message builder node. Yes, after EACH user action, the variables need to be refreshed. It's a little bit of a pain in that you have multiple copies of a given node if you have multiple approval levels and user actions, but that's been my experience.