Skip to main content
  • EN
According to the docs when using FMEServerWorkspaceRunner you can specify the value of published parameters to be a value from attributes of the feature that triggered the job:

 

 

"Any published parameters associated with the server workspace must be given values. These values can be taken from attributes of the feature that triggered the job to be submitted, or can be typed in (in which case they will be the same for each job that is sent via the transformer)."

 

 

But I can't seem to find how this is actually done in Workbench. The wizard page lists my published parameters but does not have the usual drop-down arrow to allow me to specify the feature attribute to assign as the value. I also tried setting the value using the macro @Value(attribute_name) but all that did was pass through the string. So is this an error in the docs or am I missing something obvious?

 

 

FME Desktop 2013 and FME Server 2013
The FMEServerWorkspaceRunner can take the value from an attribute if the Published Parameter type accepts an attribute value. Some parameter types do not support this. My recommendation would be to thus create a custom published parameter of type Text and try that.

 

 

I believe FME 2014 may have introduced this capability rather than 2013 but I'm not certain.
I i'm reading this correctly i think u should set it by using @Value(@Value(attribute_name))

 

Because attribute_name holds the ..wel attributename, but you want to set the value of this attributename.

 

 

This is how i acces my triggervalue in (non) server workspace runner sets.

That's very odd. I can't see a reason why attributes wouldn't be allowed (as the doc specifies). I shall investigate.

 

 

I did try to find a workaround, but nothing really appears to work. Even using parameters of type "Attribute Name" doesn't work. So I'll find out what I can and let you know,

 

 

Regards

 

 

Mark

 

 

Mark Ireland

 

Product Evangelist

 

Safe Software Inc
OK. Try the FMEServerJobSubmitter. That seems to be the transformer you need here. I'll talk to the docs team about getting that fixed.
On further inspection, the problem with using the FMEServerJobSubmitter is that I'm not sure you can upload any data with it. If you don't need to then that transformer will be fine. If you do need to upload data, then we have a problem. Contact our support team (safe.com/support) and ask them to add your details to PR#28780

 

 

Regards

 

 

Mark
Thanks for your suggestions Mark. I don't need to upload data in this case but the FMEServerJobSubmitter is not suitable as I need to submit the job in async mode and supply the user's email address that a topic will use to send them a custom email response.

 

 

I worked around the issue for now by just using an HttpUploader to POST to the workspace and building up the parameter string to send in the POST body. So I guess basically mimicing what the FMEServerWorkspaceRunner does.

 

Reply


Community Stats

30,351
Posts
115,341
Replies
38,081
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.