Known Issues and Limitations

The ME52N script created on S/4HANA 2020 will not work on S/4HANA 2021. The user will have to re-record the script in S/4HANA 2021.

While defining SAP connections or using SAP credentials, user should use two characters in SAP language (like FR for French, EN for English) on Evolve, Studio Manager and Studio. The single character for SAP language does not work throughout the SAP interaction.

For Google SAML SSO, we do not support multi-domain system.

Migration of solutions across system with different locales is not supported.

Chain script macro not working via Connect mode.

While working on the Japanese setup, there are a few Japanese characters that are restricted in Evolve and Studio Manager. The list of such characters is available at this location.

Japanese Characters are not Supported for : -

• Salesforce/Connect customer account details

• Evolve site and portal site name

• SAP Username/Password (except for credentials based logon)

• Domain Username

• Virtual Machine host name

• Email address/password

Unsupported features for Japanese Locale: -

• Studio (Connect only mode)

• SharePoint List data connection

• Enterworks integration with Evolve

Linked Query scripts where one is mapped to Excel and other to SQL are not supported.

While using macro code for script run of multi script scenarios, if only solution name is provided then script run of only the first file will be performed on production server.

When trying to attach documents in CV02N at the time of running the script, user will get an error -- "Runtime error RAISE_EXCEPTION has occurred". This issue occurs with scripts that are recorded in Non Batch Modes (With or Without Controls). Change the mode to Standard (Batch) as a workaround.

If customer is using any custom policy for their Windows Defender or antivirus software, then for successful installation of Winshuttle software, they may need to add Winshuttle installers to white-list for their defender / antivirus.

Long text fields captured at the time of recording will not get uploaded to SAP on SAP HANA server at the time of Run.

GOS document attachment will not work on HANA Servers using CV02N script.

The number of records that can be downloaded using Reference Data as a destination are about 400,000 (with 10 output fields) with default settings. This data also depend on size of fields.

Migration Utility: While migrating scripts with round trip scenarios (having Qsq and Txr scripts), template having more than one published solution will not get migrated.

SAP SAML configuration: We store mysapsso2 ticket / token when user clicks on "Save as Auto Logon". If user saves the ticket / token then they can do scheduling. The scheduling will fail if mysapsso2 ticket / token expires before the run.

Migration Manager: The SAP Mapping is used to change only the SAP Server name with the scripts. Any changes related to the internal properties of the Form or Excel workflow will not get altered.

Local Scheduling and Console Run do not work for SAML and OAuth authentication setups.