The FinalBuilder script editor and the ability to run inline scripts is excellent! However each action seems to create a new instance of System.Automation (.Net PowerShell Instance).
Generally this is a good idea but sometimes when you may want to persist a powershell session between actions. For example, in our example, we connect to vSphere via Connect-VIServer (PowerCLI) – which takes 10+ seconds, and then have other actions in the FB run script which may want to use the session token from a previous VIServer session. Since each action has a different action has a different PowerShell session instance the connection token from VIServer is invalid as it was closed when the previous PS session was closed.
Is there a way to have a common single automation session for all of FinalBuilder – maybe make this an option if it does not currently exist?