Release Notes > Release Notes for ThingWorx Platform 9.2 > Fixed Issues in ThingWorx Platform 9.2.4
Fixed Issues in ThingWorx Platform 9.2.4
The following fixed and known issues are part of ThingWorx Platform 9.2.4.
Fixed Issues
ThingWorx 9.2.4 uses log4j 2.17 and is not exposed to the current CVEs with older log4j versions. Guidance for older ThingWorx versions should be referenced here.
Fixed potential security issues, including items proactively identified by vulnerability scanning software or PTC Quality Assurance testing. Please upgrade as soon as possible to take advantage of these important improvements.
PTC has recently implemented a new support policy with respect to Identity and Access Management (IAM) solutions. Please see the appropriate eSupport center section for more information.
See this technical support article for important recommendations regarding the use and update of third-party software for ThingWorx.
Tracking Number
Fixed an issue where setting the same model tags concurrently on multiple threads caused deadlocks in MSSQL.
Fixed an issue with ThingWorx HA that was preventing a job from being cleared from the in memory cache if a file transfer job failed due to a time out issue.
Fixed an issue that was preventing SCM projects from being deployed.
Fixed an issue that was causing the QueryPropertyHistory service to fail on a cloud hosted instance with value streams stored in InfluxDB.
Fixed an issue that was causing services containing JSON arrays to fail.
Mashup Builder
Tracking Number
Fixed an issue with the Schedule Chart legend marker that was preventing the color from updating correctly.
Fixed an issue that was causing an undefined selected row of an infotable to override the default property value it was bound to.
Fixed an issue with the Button widget that was preventing the focus style from being configured.
Fixed an issue where mashup parameters with an undefined value were being passed as a string value.
Fixed an issue where the Grid Advanced was not filling the entire space of a dynamic panel widget when it expanded and collapsed.
ThingWorx Flow
Tracking Number
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 and Limitations
The following items are known issues and are scheduled to be fixed in a future release.
Tracking Number
If you are performing a maintenance upgrade (for example, 9.2.3 to 9.2.4) on MSSQL or Azure SQL, the upgrade will fail if any custom index field value length is 64 characters or more (number of columns in the index plus combined length of indexed column values - 1 = 64). Verify all custom index fields have values before starting the upgrade process. If the upgrade fails, execute the latest schema update script ( thingworx<database>SchemaUpdate<priorVersion>-to-<currentVersion>.bat/.sh) and restart Tomcat. See Maintenance Release Upgrade for more information.
If you are upgrading MSSQL, Azure SQL, or H2, the upgrade will fail if there are any missing values for the custom indexes field/column in the data table entries. Verify all custom index fields have values before starting the upgrade process. If the upgrade fails, you will need to restore the ThingWorx database and platform, remove custom indexes or provide missing values for the custom indexed fields, and then restart Tomcat. See Upgrading ThingWorx for more information.
The file size of uploaded files is not being made available within the platform for eMessage uploads.
An HA server crashes sometimes when a service is executed multiple times.
Users are not persisted and not seen in the users table in an environment configured with HA and SSO.
URLs with a dash ( # ) fail to be resolved and the page is empty.
The server has performance issues when multiple remote things connect and the server ingests the data and processes events.
Creating equipment using multiple API calls that call the CreateEquipment service results in the platform freezing.
The UpdateDataTableEntries service fails to update Data Table data that contains special characters in the Data Shape.
Mashup Builder
Tracking Number
After a session timeout in a mashup, the session timeout pop-up message keeps showing up after clicking the dismiss button.
The Collection widget has performance issues when loaded via the Tab click event.
When navigating from one mashup to another, the styles get applied to the new one too.
Set property values for mashup parameters are retained when new mashup parameters are added.
Migrating a mashup in ThingWorx 8.3 containing validator widgets inside the panel to ThingWorx 9.0 deletes the validator function if the panel is deleted.
ThingWorx Flow
Tracking Number
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.
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.
Was this helpful?