Can you describe what you are running into a little bit, just so we can verify there isn't a way around this for you in particular.
In general what this article is refering to isn't something you can really fix. If the application is specifying a source address then that's what you'll see come across, there isn't really a way to fix that from a GlobalProtect administration side of things. You could potentialy route this traffic around the GlobalProtect routes, but this would be a highly manual process and would likely have a maintenance cost associated with it as far as maintaining those routes are actually correct.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!