Release Notes > Release Notes for ThingWorx Flow 9.1
Release Notes for ThingWorx Flow 9.1
Fixed Issues in ThingWorx Flow 9.1.8
Fixed an issue with a Flow connector that was preventing a user from using connected apps if they didn't have an SAP account.
Fixed an issue with the MSSQL connector that was preventing it from working if the database was set with collation v=Latin1_General_100_CS_AS_SC.
Fixed an issue that was causing workflows to stop working.
Known Issues in ThingWorx Flow 9.1.8
• ThingWorx Flow execution will fail if:
◦ A user switches from one type of Windchill connector to another type for the same Windchill server and again switch back to an earlier connector type from a later one. For example, If a user switches from Windchill Basic to Windchill 2-WaySSL and again from Windchill 2-WaySSL and vice-versa.
◦ A user recycles a connector to another type and then changes it back to the original type. Then the new connector is used in a Flow.
• As a result of changes in Azure API, earlier Azure action Execute Function will fail. Recreate the action using the latest version in all the existing workflows before workflow execution.
To recreate the action:
1. Drag and drop in the action in the workflow region.
2. Configure the action fields same as old action.
3. Delete the old action and reconnect the new action in the workflow.
.
Updates to Google Forms and Google Connector
If you have an existing OAuth provider and/or connectors for Google Forms and Sheets, you may be unable to add the connector. Use the following workaround:
1. Delete all tokens for the Google Forms and Sheets Connectors if they exist.
2. Using the Workflow Subsystem service LoadOAuthConfiguration, upload the OAuth provider/s for the Google Forms and Sheets for each of the configured providers.
3. Restart the OAuth service.
Known Issues and Limitations ThingWorx Platform 9.1.5
Issue
Tracking Number
When a connector is imported with the same name of an existing connector, but with a different connection type (such as Basic, OAuth named user), a duplicated connector is created instead of ignoring the imported credential. The workaround is to delete the duplicated connector that was created.
TW-89278
After importing Windchill Oauth connectors where the resource URL was set as part of connectors' creation, these connectors become invalid. The workaround is to set the resource URL via reconfiguring OAuth setting, refer to the details here.
TW-89277
What's New in ThingWorx Flow 9.1.0
• ThingWorx Flow metrics have been added and are displayed in ThingWorx Flow Performance Advisor.
• The Activity Logs page has been redesigned to provide advanced search and group by workflow name to view a complete overview of workflow execution.
ThingWorx Flow deployment enhancements
• The ThingWorx Flow installer supports automatic uninstallation.
• The ThingWorx Flow docker deployment has been simplified, and now uses a single configuration file.
Connectors enhancements
• OSLC and HTTP connectors support the OAuth connection type.
• SAP connector—The Execute BAPI action has been updated to search for BAPIs in the authorized SAP system.
• The Windchill connector has been updated to support KeyStores and TrustStores in the PKCS12 and JKS format when using the 2–Way SSL connection type.
Fixed Issues in ThingWorx Platform 9.1.0
Issue
Tracking number
• Fixed an issue that was preventing a workflow from being edited after being imported from ThingWorx 8.5.
TW-81167
• Fixed an issue that was preventing the flow-deploy-settings commands from working with the app key option.
TW-80370
Was this helpful?