Skip to main content
Solved

How to trigger workspace using an upstream workspace within an Automation

michielschram
Forum|alt.badge.img

Within an automation I want to trigger a workspace with a previous result. In this case, as shown in the picture, I only want to process a submitted file if the validation is valid. Most desirable is that I can set a certain parameter within the createValidationStatus workspace and be able to filter on that in the automation filter.

Unfortunately I haven't figured out how to do it this way. I did find a work around by adding a terminator to the workspace when a submission isn't valid. This wil result in an "action failed". But still this isn't desirable because submitter and administrator messages got mixed up. Failure doesn't necessarily mean workspace failure.

 

Question: What is the best way to pass results from an upstream workspace within an automation?

Best answer by jurgen

Hej Michiel,

 

A possible workaround you could use is the following:

 

Create 2 new topics on FME Server.

1) If the submission was valid/passed.

2) If the submission was invalid/failed.

 

In your "CreateValidationStatus" workspace use 2 FMEServerNotifiers depending on the result. One that triggers topic 1 if it was successful and one that triggers topic 2 if it failed.

You can send the information you need into the 'Content' parameter in the ServerNotifiers.

 

*In my case it just checks if a random number is equal or smaller than 5.

 

Then change your automations a bit so it looks like something in the form of this:

 

Your main workspace is still run by the normal trigger (a DirectoryWatch in your case). The result will however trigger one of the "FME Server Topic" triggers.

 

Depending on the result you can send your mails or start new workspaces for further processing.

In the new workspaces you can take the FMEServerParameter; "FMESERVER_TOPIC_MESSAGE" to get your data back again to process it further.

 

If you make good use of Annotations and Bookmarks in your automation I think you can still create a very clear workflow even though you are using Topics (instead of connection lines) that are not directly visible here.

 

Hope this can help you with your workflow.

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

7 replies

michielschram
Forum|alt.badge.img

@hollyatsafe @keithatsafe Do I want something that is impossible with Automations? Should I do it the old way?

siennaatsafe
Safer
Forum|alt.badge.img+10

Hello @michielschram,

Unfortunately, you've stumbled upon a limitation to Automations. We currently don't have multiple output ports on workspaces and therefore can't route the email differently depending on the output of the workspace.

I'm not sure what your output email currently looks like or if it has an attachment. If you aren't currently emailing an attachment, you could include an HTML report and attach it to the email. This could include if the validation was successful or not. I'm thinking of something like this demo: http://demos.fmeserver.com/validation/

 

 

I've raised your case internally and it is now attached to the idea of adding new output ports on the workspaces in automations. I'll let you know if there are any new developments.
lars_de_vries
Forum|alt.badge.img+10

@michielschram

I am not sure what the output of your first workspace is and haven't used the automation filter yet, but would it perhaps be possible to adjust the name of the output (if the validation is not valid) and filter on that? Perhaps you can add a prefix or a suffix to the filename?

jurgen
Contributor
Forum|alt.badge.img+12
  • jurgenContributor
  • Contributor
  • Best Answer
  • June 13, 2019

Hej Michiel,

 

A possible workaround you could use is the following:

 

Create 2 new topics on FME Server.

1) If the submission was valid/passed.

2) If the submission was invalid/failed.

 

In your "CreateValidationStatus" workspace use 2 FMEServerNotifiers depending on the result. One that triggers topic 1 if it was successful and one that triggers topic 2 if it failed.

You can send the information you need into the 'Content' parameter in the ServerNotifiers.

 

*In my case it just checks if a random number is equal or smaller than 5.

 

Then change your automations a bit so it looks like something in the form of this:

 

Your main workspace is still run by the normal trigger (a DirectoryWatch in your case). The result will however trigger one of the "FME Server Topic" triggers.

 

Depending on the result you can send your mails or start new workspaces for further processing.

In the new workspaces you can take the FMEServerParameter; "FMESERVER_TOPIC_MESSAGE" to get your data back again to process it further.

 

If you make good use of Annotations and Bookmarks in your automation I think you can still create a very clear workflow even though you are using Topics (instead of connection lines) that are not directly visible here.

 

Hope this can help you with your workflow.

michielschram
Forum|alt.badge.img
siennaatsafe wrote:

Hello @michielschram,

Unfortunately, you've stumbled upon a limitation to Automations. We currently don't have multiple output ports on workspaces and therefore can't route the email differently depending on the output of the workspace.

I'm not sure what your output email currently looks like or if it has an attachment. If you aren't currently emailing an attachment, you could include an HTML report and attach it to the email. This could include if the validation was successful or not. I'm thinking of something like this demo: http://demos.fmeserver.com/validation/

 

 

I've raised your case internally and it is now attached to the idea of adding new output ports on the workspaces in automations. I'll let you know if there are any new developments.

Sienna, thank you for your response. It would be great for Automations to be able to use a result of a workspace within the automation flow.

michielschram
Forum|alt.badge.img
lars_de_vries wrote:

@michielschram

I am not sure what the output of your first workspace is and haven't used the automation filter yet, but would it perhaps be possible to adjust the name of the output (if the validation is not valid) and filter on that? Perhaps you can add a prefix or a suffix to the filename?

Lars, thank you for your responce. Unfortunately your not able to use the output of a workspace as input for an automation action. Hopefully this will change in the future.

michielschram
Forum|alt.badge.img

Thank you all for thinking allong. Actually the solution of Jurgen works fine but we decided within our project to do it without topics. We are just running every workspace within the automation. The first thing that workspaces do that are dependant on upstream workspaces is check if they should run. This save's a lot of time and keeps things simple. Hopefully in the future we will be able to add filters that are dependant on previous results so unnecessary workspaces aren't run.

Reply


Helpful Members This Week

Community Stats

31,009
Posts
117,520
Replies
38,788
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.