ThingWorx Flow
|
|||
ThingWorx Flow 8.4.15:
• Upgraded the node.js version to 12.19.0
• Added ValidateFlowSetup service in the workflow subsystems
|
Bug Fixes
|
|
---|---|
Security
|
|
• 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.
|
|
Platform
|
Tracking Number
|
• Fixed an issue that was causing a Flow server to generate extraneous core.* files located in /opt/ThingWorxFlow/modules/ux/.
|
TW-83115
|
• Fixed an issue that was preventing logs from opening after selecting View Logs.
|
TW-83110
|
• Fixed an issue that was causing an error when connecting an http action in ThingWorx Flow.
|
TW-83205
|
• Fixed an issue that was preventing the User Deletion Enabled option from working in a directory service.
|
TW-31701
|
• Fixed an issue that was preventing a custom service derived from the CreateEquipment service to create value streams for newly-created assets.
|
TW-81170
|
Platform
|
Tracking Number
|
• 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.
|
TW-82031
|
• 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.
|
TW-78472
|