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.

Migration of Japanese Email Templates is not supported with the Evolve to Evolve migration utility. User can export and import the Japanese Email templates using Export and Import option on the Evolve UI.

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.

Field encryption does not work in Evolve, if the form is accessed more than once.

Solution Data Set field name does not support localized characters in French, German, Spanish, and Japanese.

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

Challenge on Approval property for form solution won't work for External Portal user as this property requires domain user authentication while approving Form solution Task.

File upload to SAP is not supported with attachment controls added in a repeating table.

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.

The messages returned from the Azure translation service are always in English even if the Evolve locale is non-English.

In External Portal if you enable Azure Hybrid connection only on one WFE / Worker, when that WFE / worker gets down, system alert gets generated and you should enable hybrid capability on another WFE / worker through the Evolve site.

We recommend Hybrid Connection should be enabled on more than one machine, so that if one machine goes down it should not bring down the portal accessibility.

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.

The Items Per Page Setting is removed from the Drafts List widget when the user clicks the Refresh icon on the portal.

Irrespective of the number of items in the report, a maximum of 20 items are returned on the Portal Chart widget.

Download to Excel/ Download to PDF option does not work on the Portal Table widget if the content in the table is Links.

On launching internal Portal site, authentication window will show Evolve server URL instead of Portal URL. After login, the user will be redirected to the Portal page.

If end user is using both Portal as well as Evolve App to open tasks/templates and faces issue saying "Something went wrong" then,

1. Go to the Server(s) where Evolve is installed and select the WSEvolve site in IIS.

2. Click on "HTTP Response Headers" in Feature View and add a new header of name "Vary" with value "Origin"

3. Clear browser cache of end user.

The Main Page link in the assignment email received by External Portal user does not work correctly and user cannot access Portal via this link.

Image configured in assignment email sent to an External Portal user does not load using relative URL or when direct image is inserted in email.

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.

• While migrating file library, no changes can be done to the file library after it is exported. The user needs to delete the complete file library and then again download it from the source site/app after the changes are done..

SAP SAML configuration: We are 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.

While importing an Excel Solution to the Excel Library, in case the template file has multiple publised solutions, user will get an error. User will have to submit those solutions one by one using Studio.

Sorting with Enterworks data connection is not supported with this release.

For Digital access API, when starting a new form process, the user list provided for a swimlane using parameter ParticipantsInfoArray doesn't validate if the user has permission on the app (i.e. App name given in AppName parameter).

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.

REST APIs: When Generate Repeating section is not checked and API’s URLs include fields from repeating table; such configuration is not supported with Web Service control and Data Connection Adapter plugin.

Drop Down control bound with Rest API DC (Sync Mode), Data connection API URL part only supports non-repeating form field .

When the Winshuttle Update plug-in is configured to run using the Swimlane or RunnerNode and it resolves to an external user, then license will be checked for an external user. This blocks the webservice execution. As a workaround, configure the plug-in to resolve to an internal user.

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