Trigger Proxy
Meet our Remote Trigger.
We have added the ability to choose between running a trigger locally on your client machine or running it from the cloud, on the main Nintex server.
Trigger management can be done from the Nintex server and micro-services can now manage solutions on the local machine.
The use of remote triggers is only available for FCAaaS deployments.
The Trigger Proxy feature is only available when using an External Load Balancer.
Remote Trigger
There is no change in how Triggers are created, but now there is the ability to manage them remotely.
Choosing a Remote trigger is possible for all of the triggers aside from the Time trigger.
To choose the location from which to run the trigger:
-
Log in to Console Plus, see Accessing Console Plus.
-
Select Triggers from the left Navigation menu.
-
Add a new trigger:
/Console_48.png)
. -
After selecting the Trigger event (Email, File, Folder...), Use remote trigger option is visible:
/Console_49.png)
-
Choose between:
-
Run from the cloud - Run on the main Nintex server.
-
Run locally - Run on your local Client.
-
-
Select the Server type.
-
Fill in the Server address.
-
Continue with the steps for creating triggers, see Creating Triggers.
Check the Triggers list to confirm that your Remote trigger was selected successfully:
/Console_50.png)