We've done some customizations that allow a user to launch an executable from within the GP Windows client, but we're experiencing different behaviors that we're unable to explain.
In some installations, it is required that the external executable be located within the GPRuntime\MyDevCompany directory.
In other installations, it is required that the external executable be located within the GPRuntime\Data\MyDevCompany directory. Note that default security has to be modified for this to work, as end users are denied the ability to traverse or run executables from within this directory per Windows security settings.
What determines the location from which GP is launching an external application? The issues apply to both GP 2015 and GP 2016.
Thanks.