feltham1 Absent Member.
Absent Member.
174 views

SOAP Start Workflow with empty Field values

User App 4.7.2 upgraded from 4.5

Used to be, if you want to do a SOAP call to Start Workflow (do-start-workflow token) you need to provide in the soap call, every single form field by name, but not neccasarily with a value. I.e. There are 30 fields, but this call only needs to fill in 12.
In 4.5 that worked. In 4.7.2 the same PRD has 30, but is sending 15, but in fact the do-start-workflow call has all 30 defined, sent as "" basically.
Since the do-start-workflow token does NOT show in trace the actual SOAP message (That would be a neat enancement) it is hard to know what is actually sent.. But watching in Catalina trace, with sufficient logging enabled, we see that only 15 data items are sent. And we get an error that a required field is missing.
Is this a change in the behavior in 4.7.2? And if so, how do you send an empty field in the SOAP call now?
Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: SOAP Start Workflow with empty Field values

On 5/9/2019 10:54 AM, feltham wrote:
>
> User App 4.7.2 upgraded from 4.5
>
> Used to be, if you want to do a SOAP call to Start Workflow
> (do-start-workflow token) you need to provide in the soap call, every
> single form field by name, but not neccasarily with a value. I.e. There
> are 30 fields, but this call only needs to fill in 12.
> In 4.5 that worked. In 4.7.2 the same PRD has 30, but is sending 15, but
> in fact the do-start-workflow call has all 30 defined, sent as ""
> basically.
> Since the do-start-workflow token does NOT show in trace the actual SOAP
> message (That would be a neat enancement) it is hard to know what is
> actually sent.. But watching in Catalina trace, with sufficient logging
> enabled, we see that only 15 data items are sent. And we get an error
> that a required field is missing.
> Is this a change in the behavior in 4.7.2? And if so, how do you send
> an empty field in the SOAP call now?


I have been helping Robert on this one, and it was really interesting.
We could see exactly what was happening in the flow. I collected the
info and it would make a great article, just dissecting how to
troubleshoot it.

We can see the incoming values, we can see the engine send the Start
Workflon call with more values (lots of empties) and it does not seem to
make it.

Apparently this is a bug in the engine, and Support has a patch for it.
(dirxml.jar).

I do wish they would trace out the actual SOAP call they make since that
would have made this obvious I suspect.

I am guessing the engine was stripping out empty nodes, which normally
is a good idea. Except for this one.



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.