There are two ways you can do that.
You can write a json notification to a text_line writer and when publishing the workspace include the text file in Post Data from Writer.
Alternatively you can use the FMEServerNotifier to send an email.
The FMSEServerEmailGenerator is an easy way to create the json structure.
See
https://knowledge.safe.com/articles/547/sending-email-part-2-sending-an-email-using-the-fm-1.html and https://knowledge.safe.com/articles/576/sending-email-part-3-sending-an-email-when-a-works-1.html
Thanks , But when I used FMEServerNotifier to send email from workbench users receives two email one from workbench and the other from server directly when the job is complete , can't we just modify the subject of the job sent .
Thanks , But when I used FMEServerNotifier to send email from workbench users receives two email one from workbench and the other from server directly when the job is complete , can't we just modify the subject of the job sent .
If you're using the FMEServerNotifier, then you shouldn't have a topic for job success.
Dear All ,
We are using the method suggested by @jdh but now we need to get the total features written in order to change the subject of the email , if there is a way to get the below files
total features written to control the body and subject of the letter ,
job started date and time
job end date and time
Total duration of the work-space time
thanks ,
Hi @khalid_omer,
I think that the easiest way to get all this info about a job is via the REST API of FME Server, see the /transformations/jobs/id/<jobid>/result end point via the Help menu > REST API from your FME Server.
Hi @khalid_omer,
I think that the easiest way to get all this info about a job is via the REST API of FME Server, see the /transformations/jobs/id/<jobid>/result end point via the Help menu > REST API from your FME Server.
That looks to be a good way , but how to make sure that HTTPCaller transformer ran at the end of the translation , since we are using Creator transformer
That looks to be a good way , but how to make sure that HTTPCaller transformer ran at the end of the translation , since we are using Creator transformer
You can try the Create at End setting in the Creator.
Still the same , it reads the URL before it is ending writing to the FME server , that is why the result it not showing on the return value
Still the same , it reads the URL before it is ending writing to the FME server , that is why the result it not showing on the return value
This is a bit difficult to understand the order of actions in your process, can you elaborate on that, or show a screen dump of the workspace?
Still the same , it reads the URL before it is ending writing to the FME server , that is why the result it not showing on the return value
We need to overwrite the subject of the mail receive from server wether there is a Intersect or not .
We need to overwrite the subject of the mail receive from server wether there is a Intersect or not .
You could use the FeatureWriter and once its done writing use the summary feature to trigger the REST call.
Unfortunately we still using 2015 and featurewriter is not there , is there is any otherway , sorry to trouble you.
Unfortunately we still using 2015 and featurewriter is not there , is there is any otherway , sorry to trouble you.
No trouble, yes you could essentially create a second workspace containing the REST call that is chained to the first workspace via the notification service in FME Server.
This is a good place to
start with notifications and FME Server, there is much more to find on the Knowledge Center on the subject.
Still the same , it reads the URL before ending the first workbench , I think I gave up , it is the first time FME let me down . appreciaet your supports .
Still the same , it reads the URL before ending the first workbench , I think I gave up , it is the first time FME let me down . appreciaet your supports .
I think you might have misunderstood me, if you create 2 workspaces and the second one is run AFTER the first one then reading the URL ( if that is what you mean by the REST call) will always take place after the first workspace is finished writing the data.
If you want information that is only available after a workspace has finished writing, like the number of features written, you cannot use an FMEServerNotifier in the workspace, but need to write a textfile and use it as the (sucess) topic post data.
The text you write can include Notification Directives and client specific directives.
The one of interest to you would be {NumFeaturesOutput}.
See
http://docs.safe.com/fme/2017.0/html/FME_Server_Documentation/Content/ReferenceManual/Email_Templates.htm for the available keywords
and
http://docs.safe.com/fme/2017.0/html/FME_Server_Documentation/Content/ReferenceManual/EmailTemplateLanguage.htm for a better discussion of email templates.
The equivalent pages should be available in your 2015 documentation.