Skip to main content
Archived

Improve consistency and documentation of FME Server subscriptions

Related products:Integrations
siennaatsafe
geosander
  • siennaatsafe
    siennaatsafe
  • geosander
    geosander

geosander

I was recently playing with some notification topics for successful or failed jobs. So I created a Push subscription and didn't specify the subscriber_content. Guess what? FME pushed the JSON job result to the URL I specified. Great! Exactly what I need. No REST polling necessary!
Then I tried the SQS subscriber without subscriber_content. In this case, nothing was sent, because FME did not replace the empty message body with a job result and SQS does not allow an empty message.

This is what I mean with consistency: why would this behaviour be different for each subscriber?

Furthermore, does anyone of you know of a documentation page where I can get a proper overview of all the job result variables I can use in a subscriber message template? For instance: as a workaround to the SQS problem I mentioned above, I am now sending an SQS message that only contains the job ID (so I can then get the job result through the REST API using that ID). To do this, I used the {id} variable in the message template, because I read that in some example somewhere. However, other variables (e.g. {status}) do not seem to work here.

I would love to see a proper overview of all the variables we can use and for which subscribers we can use them.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

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