input and output of a 'user input task'

RE: input and output of a 'user input task'

Mike Schmitt — Fri, 14 Jun 2024 14:36:40 GMT

The real answer to this is, of course, that conflicts like this should be avoided as much as possible (and luckily it's possible to avoid it at approaching 100% if design is done carefully), because one can never be sure what the order of precedence will actually be without either testing it or asking around (and i'm not completely convinced it is guaranteed to happen in a particular order either).

RE: input and output of a 'user input task'

Stefan Helzle — Fri, 14 Jun 2024 08:48:44 GMT

That is a very common configuration issue. Any output assignment that you configure will evaluate in a random order! Writing to the same process variable from INPUTS -> SaveInto and OUTPUTS calls for trouble.

RE: input and output of a 'user input task'

Meme02 — Fri, 14 Jun 2024 08:07:09 GMT

Thanks for support
I need to leave the destination for saving inputs blank.

RE: input and output of a 'user input task'

Meme02 — Fri, 14 Jun 2024 08:06:06 GMT

I thought the order was

1) Value in input
2) Save into in inputs
3) outputs

I need to leave the destination for saving inputs blank. Noted.

RE: input and output of a 'user input task'

Meme02 — Fri, 14 Jun 2024 07:31:19 GMT

JayaPrakash Ravipati Ultimately, I expect 'errMsg' to be NULL. If I do not set SaveInto for INPUT, I can achieve this, so it is probably a mistake in my implementation, but I asked the question because I wanted to know the root cause and the relationship between INPUT and OUTPUT.

RE: input and output of a 'user input task'

Shubham Aware — Fri, 14 Jun 2024 07:25:40 GMT

Meme02

For a user input task, the value you enter takes priority over any value set in the output.
Your test confirms this - the input sets "errMsg" and the attempt to clear it in the output is ignored.

RE: input and output of a 'user input task'

Sri Ram Kaja — Fri, 14 Jun 2024 07:13:18 GMT

Hi Meme02 ,

As far I know, The execution order will be

1) Value in input

2) outputs

3) Save into in inputs

So first the value are saved in activity class parameters and then outputs are executed and in the save into fields are executed.

In your example, whatever the value in form is saved into ac!errMsg first, then output is executed i.e, null is saved into pv!errMsg and then again ac!errMsg is saved in pv!errMsg

RE: input and output of a 'user input task'

JayaPrakash Ravipati — Fri, 14 Jun 2024 07:05:50 GMT

can you provide some more info about the issue and what are you trying to achieve.