1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders. --- 2. What product and version are you currently running? We are using RV&S, server-sided Release 22.214.171.124, Client-sided in Preparation of rolling out same Version. 3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video. 4. What is the use case for your organization? Since Release 10.8, API Version is named as "4.16", since the Syntax of the API did not changed from Release 10.8 till (at least) 12.5. Problem is now following: The Library used for the Commands send over the API is changing partly from Release to Release. In other Words: A Computer having Client 10.8 installed is still able to connect to Server 12.5, whereas -from Compability Info- it should be at least Client 11.0, AND -from PTC' Recommendation- it should be at least Client 12.4. Reason for last Point: Communication methods have changed over the Time, like for eg. BEEP Communication. In other words: Server-sided control of allowed and recommended Client-Version is NOT possible. 5. What business value would your suggestion represent for your organization? Since API Details are a Blackbox, I can only raise some concerns we see with having no control about Client Version using a certain API Version. Worst case would be: If API Version would not be changed at all, for ever a Client of Version 10.8 could connect to any Server via API.
... View more