• Upgraded the node.js version to 12.19.0

• Added ValidateFlowSetup service in the workflow subsystems

• 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.

• Fixed an issue that was causing a Flow server to generate extraneous core.* files located in /opt/ThingWorxFlow/modules/ux/.

• Fixed an issue that was preventing logs from opening after selecting View Logs.

• Fixed an issue that was causing an error when connecting an http action in ThingWorx Flow.

• Fixed an issue that was preventing the User Deletion Enabled option from working in a directory service.

• Fixed an issue that was preventing a custom service derived from the CreateEquipment service to create value streams for newly-created assets.

• The number primitive supports positive and negative infinity along with NaN as legitimate number values. ThingWorx does not prevent the persisting of these values; however when running one of the Query Property History APIs on a value stream, a run time exception is generated if an infinity value would meet the query parameters.

• After PLCs are disconnected for an extended period of time and then reconnected, a race condition causes a binding failure with Kepserver that interrupts updating of tag quality and value.