Release Notes > ThingWorx Apps 9.1.1 Release Notes
ThingWorx Apps 9.1.1 Release Notes
The following enhancements and known issues and limitations are part of ThingWorx Apps 9.1.1:
Enhancements
ThingWorx Apps 9.1.1 is compatible with ThingWorx 9.2.x. Customers using ThingWorx 9.1.x should use ThingWorx Apps 9.1.0.
Known Issues and Limitations
The following known issues and limitations are present in ThingWorx Apps 9.1.1 release:
Known Issue
Solution
A ThingWorx Apps session does not time out automatically after the Idle Session Timeout (min) setting for the UserManagementSubsystem has been reached.
ThingWorx Apps is designed to display updated information in real time, and does not time out.
In the Manufacturing Planning example implementation, when viewing the CAD tab of the Work Instructions page for a work definition, the Orientation pane of the ThingView widget does not expand.
This issue is not present when the PTC.SCA.SCO.UnifiedWorkInstructionsScreenMashup is viewed outside of the Manufacturing Planning example implementation.
For more information, see Work Instructions Example Implementation.
During an upgrade, the equipment status value is not changed by the server shutting down and restarting. The equipment status after the server is restarted reflects the last status value before the server was shut down. As a result, KPI calculations which use the status duration can include misleading data for the upgrade timeframe.
This issue will be addressed in a future ThingWorx Apps release.
When using the CreateEquipment service on the PTC.SCA.SCO.ManageResourceUtils Thing to simultaneously, asynchronously create multiple equipment, some equipment is failing to create.
Simultaneous, asynchronous equipment creation is supported on PostgreSQL, but is not supported on MSSQL.
For PostgreSQL, increase the maxPoolSize setting in platform_settings.json and the max_connections setting for the database so that they are a larger number than the equipment being created. For example, if you are creating 100 assets, increase the maxPoolSize and max_connections settings to 110.
For more information, see platform-settings.json Configuration Details in the ThingWorx Help Center and the documentation available for your database.
Videos do not render in the Video Player widget in the Safari browser on Mac OS.
This issue will be addressed in a future ThingWorx Apps release.
For Windchill MPMLink process plans converted into Operator Advisor in ThingWorx Apps 8.5.2, unit and quantity information is not displayed correctly.
For Windchill MPMLink process plans converted into Operator Advisor prior to ThingWorx Apps 8.5.2, operated-on parts are not stored, and cross-selection highlighting does not function.
Workaround: Convert the process plan again, after upgrading to ThingWorx Apps 9.1.
Viewing mashups directly from within ThingWorx Composer for the first time can result in a message saying that the user does not have a valid license.
Workaround: Reload the mashup.
This issue will be addressed in a future ThingWorx Apps release.
Options navigation criteria does not filter process plans as expected during conversion when operations are "overloaded". Overloaded operations have expressions assigned to resources within the operation, such as tools or equipment, for more than one variant filter.
Overloaded process plans, where expressions are assigned to the operations themselves, rather than to resources within the operations, are filtered as expected during conversion.
In Asset Advisor, the Additional Properties and Monitored Properties tables take more than five seconds to load because the GetAdditionalProperties service is executing slowly.
Ensure that remotely bound properties have a Cache Method setting of Read from server cache rather than Fetch from remote every read.
The Cache method setting controls whether property values are read from a property cache that is maintained on the ThingWorx server, or are read directly from the Edge device. The Read from server cache setting causes property values to be read from the server-maintained property cache, which is more performant.
Was this helpful?