Potential compatibility issues upgrading custom WRS (import.js) from Windchill 12.1 to 13.0 (Nashorn & Olingo 5.0)

Hi everyone,

We have a highly customized Windchill REST Services (WRS) endpoint functioning perfectly in Windchill 12.1. We developed this using a custom domain setup with import.json and a complex import.js file for an unbound function.

Inside our import.js, we heavily rely on the Nashorn engine using Java.type(...) to access core Windchill APIs. For example, we dynamically call wt.session.SessionHelper.getPrincipal() and com.ptc.projectmanagement.assignment.AssignmentHelper to fetch and manipulate user resource assignments directly from the JS context.

We are currently planning an upgrade to Windchill 13.0. I noticed in the release notes that the WRS framework in WC 13 has been updated to support Java 17, OpenJDK Nashorn, Tomcat 10, and Olingo 5.0.

My questions for those who have migrated to Windchill 13: 1. Are there any known syntax or runtime compatibility issues with the new OpenJDK Nashorn engine when making heavy Java.type() calls to WC core classes compared to the standard Nashorn engine in 12.1? 2. Does the shift to Olingo 5.0 or Java 17 introduce any breaking changes for custom JSON string responses or OData parameter parsing in JS? 3. What is the recommended way or best practice to debug these custom import.js scripts during the WC 13 upgrade process?

Any insights or shared experiences would be highly appreciated. Thanks in advance!