Skip to main content
Question

use default value in published parameters on fmeserverjobsubmitter if not set

  • March 28, 2019
  • 3 replies
  • 46 views

giosp
Contributor
Forum|alt.badge.img+7

Hi,

I have a core workbench that is called from a fmeserverjobsubmitter with several parameters from the submitter workbench.

Now in the core workbench I added a new parameter. If I don't refresh the fmemserverjobsubmitter in the submitter workbench, the behaviour is what I expected: new runs of the submitter workbench works with the default value set in the new parameter.

If I refresh the fmeserverjobsubmitter the new parameter is present in the list of my parameters. Now I'm forced to set a value in the parameter box. If I leave the value empty, the jobsumbitter send an empty value to the core workbench. I've tried to switch to private parameter and set the default value but I have to maintain the value in the private parameter.

How I can force the core workbench to use the default parameter set in it? I'd like that the behavoiur in this case is the same as the programming language. For example:

def myProcedure(param1, param2 = False):

The param2 is set to false when I call myProcedure(value1) .

The goal is to have the autoset of the value from the defaul parameter set in the core workbench.

Thank you for any suggestions

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

david_r
Celebrity
  • March 29, 2019

I'm not sure that's currently possible, short of what you've already tried.


giosp
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • March 29, 2019

I'm not sure that's currently possible, short of what you've already tried.

Thank you @david_r,

I think that I will create a optional parameter empty at default and manage the real parameter used in the workbench as a python script type with a control structure...


david_r
Celebrity
  • March 29, 2019

Thank you @david_r,

I think that I will create a optional parameter empty at default and manage the real parameter used in the workbench as a python script type with a control structure...

Yeah, that's probably the most robust solution. I would've done the same thing myself.