I use a hybrid approach. In the email template on FME Server, I might have something like
<fmeblock><p>Job {id} has completed successfully</p>
<p>Click here to download the results:
{downloadUrl}</p></fmeblock>
<fmeblock type="optional">{AdditionalData}</fmeblock>
In the workspace I create a textfile with the following json:
{
"AdditionalData" : "stuff I want to include in email"
}
In the service properties I include the name of the textfile in the Post Data from Writer option.
Any JSON element in the post data can be referenced in the email template by {name}.
I use a hybrid approach. In the email template on FME Server, I might have something like
<fmeblock><p>Job {id} has completed successfully</p>
<p>Click here to download the results:
{downloadUrl}</p></fmeblock>
<fmeblock type="optional">{AdditionalData}</fmeblock>
In the workspace I create a textfile with the following json:
{
"AdditionalData" : "stuff I want to include in email"
}
In the service properties I include the name of the textfile in the Post Data from Writer option.
Any JSON element in the post data can be referenced in the email template by {name}.
My idea behind using FMEServerEmailGenerator was to create a published parameter for the Email address to-field and publish this to FME Server. If I provide the Shareable URL to a user with limited rights (Run Workspace only) then he will see a field for Data Upload and a second one for his email address. After the job has completed he should get an email with information about his job: if it was processed successfully then he should get the Data Download URL otherwise information about the cause why the job has finished with an error.
Do you have any ideas how to create a published parameter for the target email address?
My idea behind using FMEServerEmailGenerator was to create a published parameter for the Email address to-field and publish this to FME Server. If I provide the Shareable URL to a user with limited rights (Run Workspace only) then he will see a field for Data Upload and a second one for his email address. After the job has completed he should get an email with information about his job: if it was processed successfully then he should get the Data Download URL otherwise information about the cause why the job has finished with an error.
Do you have any ideas how to create a published parameter for the target email address?
We do this with the opt_requesteremail directive when calling the data download service.
We do this with the opt_requesteremail directive when calling the data download service.
Unfortunately I have no experiences with these types of directives so far. Could you please describe in more detail what you are doing?
In my scenario we have a common FME Server user account for different users with different email addresses eg. user 'geouser' which is used by different users with different email addresses. I would like to see something like a published parameter where the users can put in their email addresses for notification. At moment I have filled in the subscription details with one (fixed) email address but I want this to be dynamic...
