How to pull input parameters from one jobflow to another

CloverDX Platform
1

I have a listener with input parameters (“FILE_PROVIDER_NAME”, “FILE_PROVIDER_ID”) set to run jobflow_1 when a new file is added to S3. i have another jobflow_2 listener set to run upon completion of jobflow_1 – in the clover server, i have the option to "Pass parameters from the checked jobflow ". Whenever i select that option and save, that option is deselected for me. i cant seem to find a way to turn this feature on.

Any ideas?

2

Hi Mohamed,
the selected “Pass parameters from the checked jobflow” checkbox is persisted only if you fill in the respective parameters in the below field. Otherwise, it would automatically deselect since if the list of passed parameters is empty which is expected behavior. If this is not the case and the “Pass parameters from the checked jobflow” checkbox deselects despite filling the parameters in, please let us know which version of CloverDX Server you are using. Thank you.
Regards,

3

Hi Mohamed,
the selected “Pass parameters from the checked jobflow” checkbox is persisted only if you fill in the respective parameters in the below field. Otherwise, it would automatically deselect since if the list of passed parameters is empty which is expected behavior. If this is not the case and the “Pass parameters from the checked jobflow” checkbox deselects despite filling the parameters in, please let us know which version of CloverDX Server you are using. Thank you.
Regards,

“bartonv”

thank you for the reply, when i set the parameters, do i leave the field blank? is there an example of this being done anywhere?

4

Hi Mohamed,
when you select the checkbox, you need to fill in the parameters manually. Attached is an example. The parameters called ${ONE} and ${TWO} will be pushed to the job4.jbf from the job3.jbf run.
Regards,

5

unfortunately i’m not seeing a way to add those parameters, i attached a screenshot of what’s available to me.

6

Hi Mohamed,

This is unfortunately a known bug. However, it is fixed since version 5.2.0. So upgrading to 5.2.0 or newer will resolve this issue. I would recommend upgrading directly to version 5.3.

Best regards.

7

Thanks for the information.