Message builder node value truncates after the User action node

Hi,

I am building message builder node with 50-60 lines.. I am passing builder to the user action node email notification. Email content is good for the first notification. After first notification, the message builder value truncates. For the second notification node, email content truncates and formatting was bad.

Has someone experience the same or any resolution for this.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

you need to define the variable you are using in the message builder in your start node. only variables in the start node are saved during a Wait Node or User Action Node.

russel-cornelson

Good morning Lavanya,

Creating the variable in the start node will not resolve the problem for you, since your value is being truncated, the real issue is that a PfiActivityVariable has a maximum length of 2,048 characters. The variable holds the full value until the flow stops, when it does it is being saved to the PfiActivityVariable and gets truncated to 2048 characters in length.

Depending on what type of flow you are using, the solution could be fairly simple. IF your flow is not triggered by a File Channel and is not triggered by a Landmark Application that is sending input data the solution is simple. To confirm ... open the workunit from Process Server Administrator > Administration > Workunits > Workunits. Find your workunit and double click it; goto the "Input Data" tab and verify if there is no data in there.

-- If there is no data in there you can use the following solution.

1. Build your content into your message builder.

2. When you are done modifying it; use a landmark transaction to save the data into input data. For example if you are using var1 in your message builder...

_dataArea="<!LPSDataArea>" & _module="pfi" & _objectName="PfiWorkunitInputData" & _actionName="Create" & _actionOperator="NONE" & _actionType="SingleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & PfiWorkunit="<!WorkUnit>" & CreatedBy="pfiuserprofile" & Description="Description" & TextData="<!var1>" & Type="2" & CreationDate

** replace pfiuserprofile with a valid pfiuserprofile
** replace <!var1> with the variable name from your message builder.

3. Now wherever you are sending an email use <!_inputData> instead of <!var1>
-- this will be available with full content at all points during the execution of the flow.

unknown

Thank you Very much Russel for the detailed explanation.. Its very userful.. I will try this from my side ..

russel-cornelson

FYI - I recently saw someone try using this method where a Landmark Application was already using the inputdata; in which case the solution is to save a temp file with the contents, and read it it in after each wait node or user action node.

Remember: temp file should be unique; including the workunit number in the file name instead of a "datetime" will ensure the file is unique. Remember to cleanup the file at workunit completion.

bhillz

Good points to remember. Good coding is not just getting the job done, its efficiency and cleaning up after you're done. Your Systems Administrators will appreciate the help keeping the system tidy and smooth operating.

Copyright © 2025 Infor. All rights reserved.