Workflow Modeller and an inconsistent configurable variable

I'm getting inconsistent behaviour with Workflow Modeller and a particular Configurable variable for all users.

A Configurable Variable declared on the instantiation screen is sometimes being truncated when passed through to the workflow. The behaviour is erratic. The same two variables of approximately 30 are showing this behaviour.

In debug mode the Job Specification shows that the variable is being truncated and the degree of truncation varies. I believe this indicates the action of creating the Job Specification file is being corrupted.
e.g. "Morrissey" declared in the Instantiation form is processed to "Morrissey" (correct value) or "Morriss" or "Mo" or another truncated form of Morrissey.

I can find no errors in the logs.

The instantiation screen is an "inline ipl" with accompanying FormAPI. All the bahaviour appears OK.
Most code and configuration is maintained within a "code branch" on the backing store and sym links from iw-home path to the STAGING area of the "code branch"
The custom instantiation screen has a lot of variables (around 30) - are there any known limitations in number of variables the instatiation screen can manage ?
My suspiciaon lies with the Interwoven internals creating the Job Specification file. Are the any ways of getting additional debug information ?

Appreciate any ideas and thoughts ?

TS 672 Linux
WFM

Find more posts tagged with

Comments

krishna_kumar

Hi

I am facing the same issue. But in my case, the value is getting truncated after 1782nd character and it is the same in all cases without any variation. So is there any limit to the amount of data the variable carries from the instantiation screen to the workflow (a custom java class which is being called as part of External URL task. In my case it is not carrying more than 1782 characters)???

Let me elaborate the problem i am facing. I am setting value to a text area defined within the instantiation screen. The value is very large (its a string with xml data and is dynamic based on the number of files user submits). Its working fine within the screen(client) i.e., within the cfg, but when the control passes to the workflow(server), the value is getting truncated to 1782 characters. I have tried passing some static content but the result remains the same (1782 characters Smiley Sad

) and i also changed the item type to text and assigned maxlength but doesn't work.

Is this a limitation with TeamSite Workflow variable?? Is there a way we can pass such large strings to the workflow? What i found was the response to the server is sent via POST but still the value gets truncated.

Any suggestion is highly appreciated and thanks in advance.

thatfish

Atleast I am not alone - certainly our issues sound similar.

I've used Fiddler to examine the POST request from the Instantiation screen.

In my scenario I have proved that the "outs" POST request are not the same as the "ins" from the returning Job Specification File i.e. the form instantiation appears OK and gets passed via a HTTP POST request with the correct values. It is getting corrupted (a variable is being truncated) by the Interwoven Workflow application which produces the Job Specification and Expanded Workflow Model.

Not much more I can do so it's off to Interwoven Support I go.

With your issue I'd suggest doing something similar by examining your POST request and if you can prove the issue lies with Interwoven then raise a ticket.

When I have a resolution I'll post it back here.

thatfish

The issue has magically fixed itself - yippee - not quite.

A make_toolkit and iwreset (which has not been executed for a couple of months is my guess).

If you get this issue can you firstly try an iwreset -ui to see if that resolves it.
If not try a make_toolkit to see if that resolves it.

And post your results.

In the meantime I'm leaving the ticket open with interwoven.

krishna_kumar

We are unable to resolve it and so i had to follow an alternate way. The variable which carries the content is sent via callserver and is retrieved in my workflow.

If you find any other solution please post it here.

Thanks
Krishna.

MichaelP

I am also having the same problem and was wondering if anyone ever found a fix. I have noticed the amount of truncation seems to be relative to the amount of text I put in the job description field. If I put "test1" as the job description, one of my variable was truncated by 4. If I put in "test1234", my variable was truncated by 7. If my job description was longer than the variable, then it seemed to be fine. So for my case, if I put in "test12345678", it was not truncated. I know it is not my code since my code does not touch that variable and the variable should be using the default set in the model.

I have a case open and have provided support with many log files and examples.

-Michael

thatfish

Finally the engineers came up with a fix and patched a couple of jars. I suggest using a http packet inspector like fiddler to prove the issue lies with the workflow black box and not your code and give support a clear picture of the issue. Although I would Hope to see the patch included in a SP release.