Release Notes > Release Notes for ThingWorx Flow 9.0
Release Notes for ThingWorx Flow 9.0
Fixed Issues in ThingWorx Flow 9.0.13
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.0.13
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 ThingWorx 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 Sheets 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 ThingWorx Flow 9.0.13
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.
.
Known Issues and Limitations in ThingWorx Flow 9.0.10
ThingWorx Flow
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
Fixed Issues in ThingWorx Flow 9.0.5
Bug Fixes
Tracking Number
Authorization changes following updates to Dropbox Authorization
Newly introduced short-lived access tokens, refresh tokens.
Adding permission scopes for authentication while adding a new connection. For more information refer: Now Available: Scoped apps and enhanced permissions
* 
1. Migrate the Dropbox app and set new permissions from the Dropbox website: Migrating App Permissions and Access Tokens.
2. Upgrade ThingWorx Flow using the steps here.
3. Test and update the Dropbox connectors so that new valid tokens get acquired. If the existing Dropbox authentications return an Invalid error message, edit the authentications and provide new credentials using the step mentioned here.
TW-83911
Update to new search APIs from Dropbox
New filters: Filename Only, File Status, Order By , File Extensions, File Categories, for Search File and Folder Metadata.
* 
Older version of Dropbox Search File and Folder Metadata action stops working after February 28, 2021.
To continue using the Search File and Folder Metadata action in workflows, replace the older action by dragging and dropping the new Search File and Folder Metadata action on the canvas.
TW-83912
What's New in ThingWorx Flow 9.0.0
Expanded capabilities for deployment
ThingWorx Flow is compliant with ThingWorx Active-Active cluster environment. Most of the ThingWorx Flow components can be scaled; however, ThingWorx Flow High Availability is not supported. For more information, see ThingWorx Flow in ThingWorx HA.
ThingWorx Flow Dockerfiles and supporting Composer files are available to build ThingWorx Flow on Docker environment. You can deploy ThingWorx Flow along with ThingWorx Docker images for both single ThingWorx mode and HA cluster ThingWorx mode.
ThingWorx Flow automated upgrade installer is available to upgrade from a fresh installation of ThingWorx Flow 8.5.x and later to 9.0.
You cannot use this upgrade installer to upgrade from a fresh installation of 8.4.x. Even if you have manually upgraded ThingWorx Flow from a fresh installation of 8.4.x to an 8.5.x version, you cannot use this automated upgrade installer. In this case, you must migrate ThingWorx Flow .
Enhanced infrastructure functionality
Compared to previous releases that supported predefined fixed accounts only, you can now use a user’s identity in ThingWorx Flow connectors. This ability is essential for secure production use for many applications and enables fetching different content for different users. Two-Way SSL and OAuth (Session User) connection types were introduced to enable this capability. For more information, see Connector types .
You can switch a connection type for the selected connector, which helps in easy maintenance of workflows. The Switch option is available only if the third-party service supports more than one connector type.
You can map connection variables in a workflow, which allows using the same action or workflow for different environments of third-party services. For more information, see Map connector.
ThingWorx media entities can use ThingWorx Flow connectors for authorization. For more information, see ThingWorx Flow configuration in media entities .
Multiple action forms have been updated where you can choose Form to provide inputs for individual input fields listed in the form, or choose Assign JSON to specify a single JSON with all required inputs. Using Assign JSON shortens the forms, and also removes the limit on the length of the items of arrays.
The following services have been added to the WorkflowSubsystem in ThingWorx Composer:
The LoadOAuthConfiguration service must be used to load OAuth configurations to the ThingWorx Flow server. This service provides a default template in the preconfigured format for all third-party services that support OAuth.
The DeleteOAuthConfiguration or GetOAuthConfiguration services must be used to delete or retrieve OAuth configurations from the ThingWorx Flow server.
With the DeleteOAuthAccessToken service, you can delete OAuth access tokens of a user for the specified OAuth provider or delete OAuth access tokens for all users for the specified OAuth provider.
The RefreshMetadata service caches Windchill OData information to improve performance.
User interface
The ThingWorx Flow dashboard has been redesigned to navigate easily to workflows, connectors, triggers, custom actions, and activity logs.
New actions
Added the Sync action under Developer Tools to consolidate results of previous actions in multiple paths to the Sync action. It demonstrates the logical AND or OR operation.
Added the Return Result action under Developer Tools to return the output of any executed action in the workflow to the synchronous ThingWorx service or webhook invoker, during workflow execution.
Added Create Entity, Delete Entity, Get Properties, and Update Entityactions under SAP OData to query and manipulate datasets in your SAP system through CRUD (create, read, update, and delete) operations.
SAP OData actions support the Basic and OAuth connector types.
Added Execute BAPI action under SAP RFC to execute default or custom BAPIs. The input form dynamically changes according to the BAPI that you provide.
Added Execute Swagger APIaction under Windchill to execute Windchill Swagger APIs.
Added Download Content action under Windchill to download content from the Windchill server.
Added Upload Content action under Windchill to upload content in the form of a file, stream, or string to the Windchill server.
Added Execute Stored Procedure action under SQL Connector to execute an SQL stored procedure.
Updates to existing third-party services and actions
All third-party services that previously supported predefined, fixed OAuth accounts, OAuth (Named User) have been enhanced to additionally use the current session user’s identity. This new connector type is called OAuth (Session User). For more information, see Connector types.
The HTTP Request action supports the basic connector type.
Ability to add custom headers to actions that have HTTP-based interactions.
Gitlab, JIRA , and ThingWorx support the OAuth connection types, OAuth (Named User) and OAuth (Session User).
While loop added to the Loop action.
All Bitly and Dialogflow actions have been updated.
SQL Connector
Ability to create and update multiple rows in the Create Rows and Update Rows actions.
The Distinct check box provides the ability to return unique values in the column for the Get Rows and Get Rows with Join actions.
Ability to add free-form SQL in the Where Clause and Join Clause input fields for Delete Rows , Get Rows, Get Rows with Join, and Update Rows actions.
Dynamics 365 CRM
The Include Reference Domains check box in Execute Actions and Execute Functions actions provides the ability to display actions and functions that are described by ActionImport and FunctionImport in the referenced domains, respectively.
Ability to include referenced navigation properties for Create Record and Update Record actions. The input form dynamically changes according to the entity set that you select.
Ability to filter object properties through a Form-Based Query, Discrete Query, or Raw Query for Execute Actions, Execute Functions, and Get Records actions.
OData
The Include Reference Domains check box in Execute Actions and Execute Functions actions provides the ability to display actions and functions that are described by ActionImport and FunctionImport in the referenced domains, respectively.
Ability to include referenced navigation properties for Create Entity and Update Entity actions. The input form dynamically changes according to the entity set that you select.
Ability to filter object properties through a Form-Based Query, Discrete Query, or Raw Query for Execute Actions, Execute Functions, and Get Properties actions.
Windchill
The Include Reference Domains check box in Execute Actions and Execute Functions actions provides the ability to display actions and functions that are described by ActionImport and FunctionImport in the referenced domains, respectively.
Ability to include referenced navigation properties for Create Entity and Update Entity actions. The input form dynamically changes according to the entity type that you select.
Ability to filter object properties through a Form-Based Query, Discrete Query, or Raw Query for Execute Actions, Execute Functions , Get Entities by ID , and Get Entities by Query actions.
Was this helpful?