Skip to main content
Question

Conditional value as parameter for WorkspaceRunner not working


Forum|alt.badge.img

I'm trying to create a conditional parameter value in a WorkspaceRunner, based on an attribute value. I can do this, as the WorkspaceRunner is allowing me to fill in conditional values for the parameters, however, every time I click OK and reopen my WorkspaceRunner, all these conditional values are reset and again replaced by their hard coded values, as read from the model that the WorkspaceRunner is calling.

Is there a reason for this behaviour or is this just a bug?

I'm using FME 2018.1 build 18547 WIN64.

8 replies

philippeb
Enthusiast
Forum|alt.badge.img+22
  • Enthusiast
  • January 10, 2019

Would it work if you put your conditional parameter value into the Workbench that the WorkspaceRunner is calling?


Forum|alt.badge.img
  • Author
  • January 11, 2019
philippeb wrote:

Would it work if you put your conditional parameter value into the Workbench that the WorkspaceRunner is calling?

Yes, my workaround at the moment is an AttributeCreater before the WorkspaceRunner that creates these conditional values as attributes, in order for the WorkspaceRunner to use them. I feel however that this should be working inside the WorkspaceRunner, no?


virtualcitymatt
Celebrity
Forum|alt.badge.img+42
bakkermans wrote:

Yes, my workaround at the moment is an AttributeCreater before the WorkspaceRunner that creates these conditional values as attributes, in order for the WorkspaceRunner to use them. I feel however that this should be working inside the WorkspaceRunner, no?

Sounds like a bug to me. One option you might have as a workaround is to see if the attributes in the Navigator work for you. I think I remember having this issue and using the Navigator as a workaround. The Navigator behavior may have changed, however, in FME 2018.


tim_wood
Contributor
Forum|alt.badge.img+8
  • Contributor
  • January 11, 2019
philippeb wrote:

Would it work if you put your conditional parameter value into the Workbench that the WorkspaceRunner is calling?

The only parameter of the WorkspaceRunner I can see that offers Conditional Value as an option is the name of the Workspace to run. Is this what you're trying to set?

I've never set the Workspace name in the WorkspaceRunner dynamically, but I have done this with other WorkspaceRunner parameters. However, I've always set the values in an AttributeCreator, AttributeManager etc, or generated them e.g. via a Schema Reader, or retrieved them from Workspace Parameter values set when running the Workspace.


Forum|alt.badge.img
  • Author
  • January 11, 2019
tim_wood wrote:

The only parameter of the WorkspaceRunner I can see that offers Conditional Value as an option is the name of the Workspace to run. Is this what you're trying to set?

I've never set the Workspace name in the WorkspaceRunner dynamically, but I have done this with other WorkspaceRunner parameters. However, I've always set the values in an AttributeCreator, AttributeManager etc, or generated them e.g. via a Schema Reader, or retrieved them from Workspace Parameter values set when running the Workspace.

See printscreen attached


tim_wood
Contributor
Forum|alt.badge.img+8
  • Contributor
  • January 11, 2019
bakkermans wrote:

See printscreen attached

Ah OK. Maybe you only get it for certain types of Published Parameter. I get Conditional Value as an option in WorkspaceRunnner for a Published Parameter in the child Workspace that takes a date value.


  • June 8, 2022

Hi, I know this is an old thread, but I am having the exact same issue in FME 2021.2

Has anyone ever found a fix for this?


daraghatsafe
Forum|alt.badge.img
fionahf wrote:

Hi, I know this is an old thread, but I am having the exact same issue in FME 2021.2

Has anyone ever found a fix for this?

Hi @fionahf​ sorry to hear that you are having this issue also. I did a quick test and when I tried to create a conditional value in the workspace runner parameters it also reset I also tested in 2022 with the same result. I will file a bug for this issue I will update this post with any new information I find. Hopefully we can find a resolution soon.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings