Guidelines for Using ThingWorx Navigate with Windchill+
The following guidelines are designed to help ensure ThingWorx environments and projects securely integrate with Windchill+. Make sure you review these guidelines before creating any custom applications and integrating ThingWorx Navigate with Windchill+.
Mandatory
• Hosting all instances (development, QA, and production) on the PTC Cloud.
• For custom applications:
◦ Building custom applications using ThingWorx Navigate web components or ThingWorx widgets from the
Standard category. For detailed steps, refer to the
Use ThingWorx Navigate Components in a Custom Task topic from the ThingWorx Navigate Help Center.
◦ Building custom applications using the OData connector with Windchill REST Services to communicate with Windchill.
◦ Publishing custom applications only to the CUSTOM TASKS COLLECTION.
Allowed
• Using the out-of-the-box ThingView widget that is bundled with ThingWorx Navigate, with no customizations made to the widget.
|
When ThingWorx is SSO enabled, embedding ThingWorx mashups is not supported within Windchill tabs.
|
Prohibited
|
As additional capabilities are gradually added to Windchill+, these prohibitions will be relaxed.
|
• Accessing the ThingWorx database.
• Connecting with systems or databases other than Windchill.
• Connecting to any device.
• Connecting via a VPN (Virtual Private Network).
• Allocating, using, or editing App Keys.
• Modifying or deleting users and App Keys that PTC creates using automation.
• Using third-party and custom extensions (including Java Services) and libraries, excluding the ones supported and utilized in Windchill+ and ThingWorx. PTC recommends updating to the latest maintenance release version of the third-party dependencies, to ensure compliance with the latest security updates. For details, review the
ThingWorx Maintenance Release Policy for 3rd-Party Software article.
• Duplicating ThingWorx Navigate entities or using them in custom applications in production.
• Creating and using custom widgets.
• Connecting external systems or devices to the ThingWorx REST API. Customers must authenticate via Atlas IAM to access the ThingWorx REST API.
• Using ThingWorx Solution Central for deploying custom applications.
|
Contact PTC for configuring filters in ThingWorx. After the filters are configured, you can create action models by referring to Find the Action Model to Update.
|