I have a short question. How can I share an automation app so that an user doesn't need to authenticate. himself/herself?
I am able to share workspace apps with users by disabling the Require Authentication button, but I can't find something like that for an automation app.
I also looked at manage token and enabled some options with Automation, but still the autonmation app does require an user to authenticate himself/herself.
Best answer by johannafalk1
Hi,
as far as I am aware this is a set restriction and there is no way to make an Automation App itself accessible without authentication.
However, you can possibly overcome this with a little workaround. Create a workspace app, that does not require authentication and then trigger from there the desired automation. For example: You can trigger a “topic” in the Workspace behind the workspace app, the topic is then further triggering the automation. (A topic can be set as a trigger for the automation).
as far as I am aware this is a set restriction and there is no way to make an Automation App itself accessible without authentication.
However, you can possibly overcome this with a little workaround. Create a workspace app, that does not require authentication and then trigger from there the desired automation. For example: You can trigger a “topic” in the Workspace behind the workspace app, the topic is then further triggering the automation. (A topic can be set as a trigger for the automation).
Thanks for the advice — I just have a few questions before getting started.
How do I trigger from a workspace app to an automation? Probably I have to create a workspace that does that?
In my current automation app, I have a manual trigger for geometry and an email. If I’m going to use the workspace app as the trigger, I still need the user to provide the geometry parameter. Is it possible to do that when using a workspace in combination with an automation?
If I understand your message correctly, I need to trigger the workspace app, but I also need the FME Topic to be notified within the automation itself, is that right?
Then you create a workspace where you have the required user parameters → Geometry and email. You then transform this information from the user parameters into a json and send it to the newly created topic through the FMEFlowNotifier.
Then you will have your desired automation, that has a “FME Flow Topic” as a trigger. You can configure custom output attributes that will contain the trigger content (Geometry and Email). And that you can further process in your automation as you planned it.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.