cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

OSLC Integration between RVS and Modeler should display proper error messages

0 Kudos

OSLC Integration between RVS and Modeler should display proper error messages

the oslc integration between RVS and Modeler does not surface the real error message to the end user.

 

it always returns the value for the "code" key. the oslc.log file contains the real information, the "message" value should be shown to the end users as well (or instead the code)

 

2021-03-05 14:25:05:497, info, ldp-service: Resource Request error :: {"error":{"code":"400","message":"MKS124788: You require Windchill RV&S Client license with workflow and document capabilities."},"headers":{"x-frame-options":"deny","x-content-type-options":"nosniff","ilm-version":"12.3.1.0","content-language":"en","odata-version":"4.0","content-type":"application/json","content-length":"130","date":"Fri, 05 Mar 2021 13:25:05 GMT","connection":"close","server":"PTC Integrity Server"}}

 

4 Comments
KartikOak
14-Alexandrite
Status changed to: New Idea

Hello, 

              The use case is not very clear- is the OSLC Client in Windchill RV&S or Windchill Modeler?

 

Thanks

Kartik

KartikOak
14-Alexandrite
Status changed to: Clarification Needed
 
PE_NangaSystems
6-Contributor

The error 400 is showing up to end users in Modeler..just have a look at the attached screenshot from the original post. This is the (german) Modeler interface; the error message just says "the remote server returned an error (400) invalid request".

 

the log file from the initial post is showing the log of the OSLC server, the error message in this log clearly states the reason - this message should show up in Modeler.

PatrickOllerton
14-Alexandrite
Status changed to: Under Consideration

Thanks for the request, and we agree the errors displayed in Modeler should be more helpful so we've added this request to our backlog with the ID: ART21-20949006 and will consider for a future release.

 

For now, you have to refer to the OSLC Log file instead.

 

thanks,

Patrick