Skip to main content
Solved

FME automation - attributes from one workspace into another?


parke372
Contributor
Forum|alt.badge.img+8

Hi,

 

I'm really new to FME, and am a little confused about how to do something.

 

I have an existing automation built by an integrator that parses some emails for specific text. those are then bundled up various ways and sent out to various entities via email.

 

I want to also send an API request with some of that data in it - the vendor i'm sending it to doesn't support a login auth, just tokens, though so i ended up making a workspace to send the call.

 

However, i'm kind of confused as to how i get the outputs from the previous workspace into this one?

 

I see the output keys from the writer, but, I don't understand how to get those keys into the next "run a workspace"

My schema for the API looks like:

{

    "version": "v1",

    "alert_text": "route.Email**#.RAWMESSAGE",

    "title": "route.Email**#.AlarmName",

    "IsTicker": false,

    "lifetime": "1d",

    "computers": ["MACHINENAME","MACHINENAME"]

}

 

where route. ______ is a previous output key from the upstream workspace.

 

this doesn't seem to work, though.

 

I'm assuming i need to somehow read the output keys into features in the workspace, but i'm not really sure how?

 

 

 

Best answer by parke372

it looks like the part i was missing was defining those features are user attributes in the new workspace. Once I did that, i was able to map the upstream output keys to the downstream workspace action.

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

2 replies

parke372
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • August 9, 2023

Forgot to add, when i add the "run a workspace" to the automation, i don't see the dropdown for parameters and maybe that is the issue, but i'm also not sure how to get that dropdown?


parke372
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • Best Answer
  • August 10, 2023

it looks like the part i was missing was defining those features are user attributes in the new workspace. Once I did that, i was able to map the upstream output keys to the downstream workspace action.


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