Archer SaaS: Key Changes in the New Java Script Transporter

As part of the latest JST enhancements in Archer SaaS, there are two key updates related to proxy parameter handling and global variable usage.

What’s Changing?

• Proxy Parameter Handling: In the new JST, the proxy parameter is no longer required. It is now automatically set to an empty string before being passed to the script. As a result, any proxy configuration in custom parameters will be ignored.
• Global Variable Reference: The internal handling of global variables has been updated to reference globalThis with no impact on how they are referenced in scripts.

What Needs to Be Done?

You do not need to make any changes to your scripts regarding the proxy parameter or global variable references.

What to Do If Issues Occur?

If unexpected behaviour is noticed related to proxy settings, consider the following:

• Check your custom parameters: Ensure that your script does not depend on the proxy value.
• Validate network connectivity: Since the new JST does not use a proxy, verify that your network access is functioning as expected.
• Review script execution logs: Review the logs for any errors that may have previously been handled by a proxy and make necessary adjustments to your configurations. Enhancement in JST includes a new logging framework for Developer script logs, accessible through the JST Run Report in the Archer Back Office.
• Reach out for support: If issues persist, contact support for further assistance.