Skip to main content
Solved

Automation passes through the parameter key if the parameter is not provided

annette2
Contributor
Forum|alt.badge.img+10

I have an FME workspace on FME Server 2021 that writes a dwg file. The workspace has multiple parameters including 2 that are mandatory: FILENAME and EMAIL.

 

We want to send an email on success or failure and I have set this up via an automation. This automation will be triggered via the rest api.

 

In the automation 2 of the parameters are passed from the trigger via 2 manual keys. When I manually trigger the automation with a json file and only supply one mandatory parameter (EMAIL) the workspace still continues assigning the output filename to be automation key manual.FILENAME. If run manually via Run workspace it fails.

 

What is the best way to handle this? Should I just test that the parameters are valid via the workspace? Or is there anyway to test if the parameters have been supplied via the automation.

 

Thanks,

 

Annette

 

 

 

Best answer by redgeographics

I think it'd be best to test this in-workspace. There is the option to filter messages in the automation, but that only looks at a single key (and is in itself another workspace that needs to be run).

View original
Did this help you find an answer to your question?

3 replies

redgeographics
Celebrity
Forum|alt.badge.img+49
  • redgeographicsCelebrity
  • Celebrity
  • Best Answer
  • May 18, 2022

I think it'd be best to test this in-workspace. There is the option to filter messages in the automation, but that only looks at a single key (and is in itself another workspace that needs to be run).

annette2
Contributor
Forum|alt.badge.img+10
  • annette2Contributor
  • Author
  • Contributor
  • May 18, 2022

Thanks Hans. Yes I have implemented like this via a Creator testing the parameters and Terminating if the tests fail. Was just wondering if there were other options. Automations like this are new to me. Thank you.

H
Forum|alt.badge.img+2
annette2 wrote:

Thanks Hans. Yes I have implemented like this via a Creator testing the parameters and Terminating if the tests fail. Was just wondering if there were other options. Automations like this are new to me. Thank you.

Hi @annette2​ ,

I think the other option would be to use the Filter action within the Automation.

After the Manual Trigger I'd add two Filters like:

 

Screen Shot 2022-05-19 at 9.42.39 AMWhere the first filter checks the FILENAME contains .json, if this fails, no further action will take place, if it passes it will be routed through the second filter to check if EMAIL contains @. If this passes, both keys contain values so you can trigger the workspace, if it fails there is no further action.

 

 This may be the preferred route as then you won't trigger the workspace if the criteria isn't met.

 

Reply


Helpful Members This Week

Community Stats

31,209
Posts
118,340
Replies
38,814
Members

Latest FME

Terms & ConditionsCookie settings

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
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.