Workflow variable size limit

Hi,

I created one WFT. I am setting one workflow variable "list_of _files" with some list of filepaths with saparation of ";"

ex: $list_of_files = "/var/tmp/test1.txt;"/var/tmp/test2.txt;"/var/tmp/test3.txt";

Setting workflow variable as
variable key="list_of_files" value="$list_of_files"

This is working successfully when i gave less number of files to the variable "$list_of_files ".

I cannot initiate the workflow when i am giving ore than 100 file names to the variable "$list_of_files ".

Getting the below error
Transport marshalling error
could not create workflow variable

Is there any size limit for the work flow variable..?

Can any one help me to solve this issue

Find more posts tagged with

Comments

Adam Stoller

I believe there is a limit to the length of a value for a workflow variable, perhaps a better choice would be to create a temporary file containing the list of all these other files and set the task variable to point to that temporary file list.

Of course, there is some question as to what you're doing with this list of files that don't appear to be associated with the branch/workarea, but perhaps it's not important if you know what you're doing.

Rick Poulin

I believe there is a limit to the length of a value for a workflow variable, perhaps a better choice would be to create a temporary file containing the list of all these other files and set the task variable to point to that temporary file list.

This sounds like the right answer for your use case.. but the direct answer is yes, there is a byte size limit for any given attribute, at least in the PERL/CLT API. I thought it was 4k (4096 bytes), but don't quote me on that. I vaguely recall a thread where someone had stored a ridiculous amount of data using the CSSDK (CSTask#setVariable), but I wouldn't recommend it. If you look at the PLC, they set a filelist as a task variable by splitting the string in chunks of 1000 characters, and using a naming convention with a numbered suffix to name the multiple actual variable names. Yes, it works, but fish's suggestion seems a whole lot more sensible to me.

Garth McMillan

Rick is correct. There is an arbitrary 1000 character limit (who knows why) to workflow variables.

TeamSite CSSDK has a WorkflowUtils.setLargeVariable() and WorkflowUtils.getLargeVariable() methods to create/update/retrieve variables larger than that.

As Rick said, internally they are stored as variablename_1, variablename_2, variablename_3 etc.

Snap 2016-08-18 at 11.08.20.png

srilu

Hi All,

Thank you very much for your quick response.

Let me try with creating saparate file with the list of files rather than creating workflow variable.

Thank you very much once again.

Rick Poulin

TeamSite CSSDK has a WorkflowUtils.setLargeVariable() and WorkflowUtils.getLargeVariable() methods to create/update/retrieve variables larger than that.

The WorkflowUtils class is actually part of the livesite.jar, to support the PLC workflow. This utility class is certainly NOT part of the CSSDK, and isn't even documented as part of the LiveSite API, so I would say any direct use of it is subject to break at best, if not unsupported entirely.

Kapil_sape

As I remember the max length for a workflow variable is 16384.

Thanks.