Bugs fixed in versions 10.6/10.7

Back to

The Winshuttle logon screen now shows SAP systems sorted by system name.
Logon group details and message server host details now appear in the Winshuttle logon screen.
The error message "SAP GUI for Windows 740 hostname '/SYSID=DEM /H/ctadem029.cta.hosting.local/S3200' unknown" no longer appears when using GUI Scripting with SAPGUI 740.
SAP systems are no longer missing when using Winshuttle with SAPGUI 740.
The issue that was returning the error "Invalid URI: The format of the URI could not be determined" has been fixed.

Query now supports adding the CDHDR table on an EHP7 server that is running without the Winshuttle Function Module.
Siteminder short URL logons now automatically redirect to the long URL. They no longer require manual updates when the long URL changes.
Query now supports removing a join after the script has been saved and reopened.

Version 10.7

Query now supports the IS NULL and IS NOT NULL operators for fields in Infosets.
Pop-up confirmation messages have been removed for linked scripts running in a production environment.
Query now respects all rows in Excel input files for IN criteria in logical database (LDB) queries in systems that use Winshuttle Function Module.
Query no longer throws an exception when scripts with the Run Later setting run from the Excel Add-in.
Runner for Query respects the Adaptive Query Throttling settings that the author has specified in the script.

The mismatched join warning no longer appears after the mismatch has been removed.
In a French environment, the Scheduler now displays "A.M." and "P.M." so that tasks can be scheduled for after 11:59 A.M.
All Microsoft Excel files open when the Winshuttle add-in is enabled.

All multitable scripts with criteria send a SQL Lite exception on server W4I if the function module is not installed.
Issue with mismatched joins in HR new Hire Query scripts.
Query (MBWE table) only extracting one line when filter is not set, but when the filter is set it extracts all records as expected.
Additional fields in InfoSet are not retrieved from Query.

Hampering functionality of Workflow: If no record is found for a Winshuttle Query, instead of specifying in log field, an exception is thrown.

Also in this section