For each workflow: child task with prompt set

[Michael A. Lowry]

A foreach workflow sets a variable in the child task. As far as I can tell, this is an ordinary variable. Is there any way to set a prompt set variable in the child task?

By the way, the documentation page for the ForEach tab of the Properties pane contains some incorrect information.

Publish Value as

The name of the VARA object that is used to provide the source value to the Workflow.

This is completely wrong. This setting is where one specifies the name of the object variable to set in the child tasks.

[Joel Wiesmann]

Hi Michael

Yes you can. You define the variable in which the VARA-key is stored for each iteration on the start task. By default this is &ITEM# which seems to be stored as an object variable for every iteration and is therefore inherited to the child tasks if they accept it.

When you have a workflow task with a promptset within the FE workflow, just use &ITEM# as default value for the input-field. Alternatively, you can use the syntax {[VARA], [KEY], [INDEX]} for gathering another value-field of the iteration source VARA.

Or did I get something wrong?

Regards
Joel

------------------------------
☎️ Swisscom Automation/AI Engineer & 🧙 PEM Creator

Online Automic Training 24/7:
https://membership.philippelmer.com/ (deutsch)
https://pemautomic.com (english)
------------------------------

[Pothen Verghese]

That's right. Below is an example:

The child tasks of the For-Each flow can use/refer the above variable set here and it is not the otherway.

Regards

P Verghese 

[Michael A. Lowry]

Hi Joel,

Happy New Year!

Using the default value is a good idea. I hadn't thought of that. The only catch is that I'm not the owner of the child workflow; I'm simply re-purposing it for my own application.

I'll have to work with the owner of the child workflow to get his approval to change the default value. Perhaps we can find a way to do this that doesn't break how he is using the workflow.

Thanks for the idea.

-Michael