Known Issues and Limitations

When Evolve is setup with OKTA (SAML/OAuth), the user needs to enter credentials every time on signing into the Studio application. If user checks the Remember me checkbox at sign in, the email gets pre-filled at time of re-login.

This is the designed behavior of OKTA as mentioned in this article by OKTA support.

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.

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

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

Test connection for SAP SAML manual logon type is not supported.

While migrating scripts from 10.x to 20.x using the migration manager utility, the 10.x scripts with document attachment will need to be migrated manually.

Migration Utility: While migrating scripts with round trip scenarios (having Qsq and Txr scripts), template having more than 1 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.

User will not able to add ALC (Auto Logon Credential) for SAP server of type SAP SAML Manual.

SAP SAML (manual) SAP server will not be available for Auto Run and Update Plugin features as ALC (Auto Logon Credentials) cannot be saved for such SAP servers.

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.

Okta User with different Username and Email ID is not able to login on OAuth setup.