Skip to main content
Solved

How to return the JOB ID in a notification from FME server

  • November 19, 2014
  • 3 replies
  • 22 views

ben_vanderford
Contributor
Forum|alt.badge.img+3
I would like to know how to get the JOB ID included in a notification I get from FME Server. With lots of job's running each  night and I need the job id when I get notified of a failed run. Can someone point me in the right direction? 

Best answer by tg

Hi Ben,

 

 

If you use the Email Subscriber you can use the keyword {id}.

 

http://docs.safe.com/fme/html/FME_Server_Documentation/Default.htm#ServerCore/Email_Templates.htm

 

 

Thomas
View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.

3 replies

  • Best Answer
  • November 20, 2014
Hi Ben,

 

 

If you use the Email Subscriber you can use the keyword {id}.

 

http://docs.safe.com/fme/html/FME_Server_Documentation/Default.htm#ServerCore/Email_Templates.htm

 

 

Thomas

ben_vanderford
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • November 20, 2014
Oh yes it's the one thank you very much my friend.

ben_vanderford
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • November 25, 2014
I have this piece on the notification now. It works for my purpose. 

 

 

<fmeblock type="optional">FME transformation job {id} failed. </fmeblock>

 

      <fmeblock type="optional">The error message was: {StatusMessage}</fmeblock>

 

<fmeblock type="optional">Log file location is {LogFileLocation}</fmeblock> 

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