Assistance Needed with Case Creation on Case Server

Hello Team,

I’m reaching out for assistance with creating a Case using Case Server. The process is working as expected in our sandbox environment; however, when attempting the same in the newly deployed environment, I’m encountering a 500 error (details below).

Any insights or guidance on resolving this would be greatly appreciated.

Thank you.

4 Likes

@vaibhav @gaurav.pandey @Irfan_Ali please help

2 Likes

Hey @Promise_Bafana_Kopo , can you confirm that you have following each step given in this post ?

If you are getting error while creating case, there are two general issues:

  1. The container is not available in the BPM Server. Please, navigate the process definitions list, and try to start the process from the BPM UI itself.
  2. The process definition onboarding inside Case Manager has some mistake.

Please, don’t share the logs on community. In case you are still not able to figure out where the issue is originating from. Please, send a support request to support@neutrinos.com, our support team will contact you on Teams.

3 Likes

Hi @Paul_Thomas ,

Hope you’re well,

I was able to onboard the process and the subprocess successfully.

I also started the process from the BPM UI itself with the necessary parameters and got the response

{
“success”: true,
“message”: “Process Instance is started”,
“processInstanceId”: 123
}

, and I can fetch all the case I’ve created on JBPM without any issues.

However, when I try to create a case via the Alpha Case Server APIs using the endpoint /caseservice/case/instance/create, it returns a 500 Internal Server Error.

Here is the payload I’m using:
{
“caseType”: “string”,
“caseData”: {},
“wfData”: {}
}

Noted, Paul thank you. I won’t be posting the logs.

3 Likes

@Sam @Irfan_Ali @vaibhav @Paul_Thomas @gaurav.pandey please help

1 Like

the payload cannot be “caseType” is “string”, the caseType should be the name of the Case Definition that you set when you onboarded the case. Can you please double check that as well?

3 Likes

Hi Team,
We’ve resolved this issue. The root cause was missing wfData in the request payload. Once the required workflow data was included, the case was created successfully.

Thanks!

7 Likes