Question
3
Replies
1504
Views
Incessant Technologies
Posted: June 19, 2017
Last activity: October 12, 2017
Closed
Tracer error: (Pega-API-CaseManagement-Case)InvalidClassForInstance Abstract
When I try to create a case using the default api api.v1.cases with post to create a case, it does create the case without any issues. But in the tracer it throws an error message (Pega-API-CaseManagement-Case)InvalidClassForInstance Abstract
As the class Pega-API-CaseManagement-Case is of type abstract. Is this acceptable or should we make any changes to the existing api to avoid this error message.
The above error message is thrown in the step 2 of the activity Pega-API-CaseManagement.pzCreateCase
I attempted everything that was mentioned in the article https://pdn.pega.com/community/pega-product-support/question/pega-api-get-play-quickly - the only different is made use of the post method and the create case api.
Appreciate your help!
Original Thread: https://pdn.pega.com/community/product-support/question/pega-api-unable-update-case
***Moderator Edit: Vidyaranjan | Branched comment to create new thread ***
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Hi,
Iam also facing the same issue , did you resolve this issue? pls let me know
Posted: 3 years ago
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
You may have to look at more context, such as the steps in tracer leading up to that error so you can see in more detail what your app is doing. I find it a bit interesting that the class is abstract but doesn't end in a hyphen.
What is going on leading up to that error? Is the abstract class being used for some purpose that only concrete classes should be used for?