Upgrade a Custom Task that has Info*Engine Tasks

If you created custom tasks in PTC Navigate 1.4 or earlier, and your custom tasks use Info*Engine tasks, you can continue using them. You must keep the old Windchill Connector, WindchillConnector, installed. Then, you can recreate your configuration. You can have both connectors installed simultaneously.

• WindchillConnector does not support Content proxy functionality.

• Windchill also provides the OData-based Windchill REST services. In future releases, ThingWorx Navigate will utilize those services.

We recommend that you plan for this change when you customize ThingWorx Navigate.

For details and instructions on configuring OData services on Windchill data, see the Windchill REST Services User’s Guide.

• For information on the connectors supported in each release of ThingWorx Navigate, see Work with WindchillSwaggerConnector.

• This section applies only to recreating legacy custom tasks. If you are building a new custom task in ThingWorx Navigate 1.5 or later, Info*Engine tasks are only supported for old connectors.

• Windchill must be configured for SSL. To configure with old connectors, see Using SSL for a Secure Connection.

PTC includes the general-purpose ExecuteTask service in the WindchillConnector thing template. The ExecuteTask service allows you to invoke any task in the Windchill task codebase:

• Optional: Define an Infotable where row data is converted into Info*Engine group elements and is used as the task’s input group.

To use the ExecuteTask service, create a thing using the WindchillConnector thing template. For example, you can add a new service in ptc-windchill-demo-thing as shown in the following screen.