Please evaluate to add a variable in fmeserver that contains the useremail from the logged user if present in the useraccount table. Is useful to send mail directly to the user. Thank you.
+1 to the suggestion of having a FME Server parameter that holds the executing user’s email address - that would avoid a hack in the workspace to try and build that email address based on the user, but I’d like to expand the idea to try and address why you might be doing that in the first place.
Currently, if you execute a workspace directly, you can nominate specific email(s) to notify on completion, and you set up an automation that will send those emails on success/failure. However, if the workspace is wrapped in a workspace app, there is no option to specify those target emails.
Given the goal in doing app-wrapping is to simplify the end-user experience, I think there should be support for an option in the app configuration that lets you specify whether completion emails should be sent to the executing user. In our environment, we have a nice, simple UI in the form of a workspace app around a fairly complex workspace that runs in the Data Download Service. We want the executing user to get an email with the outcome, and a link to the resulting data. Feels like that should be a generic FME Flow capability rather than something you have to consider at a workspace level.