Skip to main content
Question

Template Variables are always _underfined_

  • December 5, 2013
  • 4 replies
  • 22 views

Hi Everyone, I have looked through all of the community information and knowledge base for some help on this but can't find anything to help with the issue.

 

 

I am trying to use templating in email notifications and I can't get the client specific keywords to be anything but _undefined_. I would like to include the directory of the transformation results in an email to certain users when a job fails. That way they can see in the log where the issue is.

 

 

Thanks in advance :)
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.

4 replies

david_r
Celebrity
  • December 5, 2013
Hi,

 

 

have you looked at the documentation for the template language?

 

 

David

  • Author
  • December 5, 2013
I sure have David. That is where I got the idea of using {urlPrefix} and {ResultRootDir} from. Unfortunately it's always _undefined_ when I run a workspace using job submitter

 


  • Author
  • December 5, 2013
Ah, wish it was possible to edit posts so all my information could be in one place...some more info that might help:

 

 

Our FME is 2013 and the template variables which seem to not work are the Data Download and Job Submitter specific ones.

david_r
Celebrity
  • December 6, 2013
Thanks for the extra info. Not sure what it could be, then.

 

 

I recommend you pass the issue on to Safe support so they can check if it's a bug.

 

 

David