Hi Team, I am facing an Internal Server Error while trying to create a case. Could someone please guide me on resolving this issue?
Please verify that your payloads are correct and ensure that both the Process Definition and Case Definition have been onboarded successfully.
We have verified, we are still facing the same error while case creation.
@enochdpm Could you please share the bpm project name??
Could you please try again to create the case??
I have tried still we are facing 500. My BPM project name is Enoch_Motor_POC
Could you please check the case service logs while hitting the api and can you share the error logs from case service??
@enochdpm Can you share the case type that you created? Alternatively, could you share the cURL request you’re using to create the case
Hi @Sam,
Please find the below details.
caseType: Motor-POC
Curl Request:
curl --location ‘https://alpha-pt.neutrinos-apps.com/caseservice/case/instance/create’ \
--header ‘accept: application/json’ \
--header ‘Authorization: Bearer zL40vtCHJwBHkpEpG4HPTz6DHNeZmw4rtRwuxaKmcET’ \
--header ‘Content-Type: application/json’ \
--data-raw '{
“caseType”: “Motor-POC”,
“caseData”: {
"customerDetails": {
"renewal_id": "RNW-20260608-33744",
"source_policy_no": "MTR-1001",
"customer_name": "Test Customer",
"customer_email": "test@gmail.com",
"vehicle_reg": "KA01AB1234",
"vehicle_type": "Sedan",
"year_of_manufacture": 2021,
"ex_showroom_price": 800000,
"claim_free_years": 3,
"zero_dep_selected": true,
"calculated_premium": 9000,
"final_premium": 9500,
"rule_trace": "test",
"route": "UW_REVIEW_OPS"
},
"uwApproval": {
"uw_remarks": "done",
"uw_approved": true
},
"opsApproval": {
"ops_remarks": "done",
"ops_approved": true
}
}
}’
@enochdpm Are you sure the flow configuration is correct? Earlier, there was a cluster issue related to the REST API installation dependency, and that has now been resolved. However, you are still getting a 500 Internal Server Error.
Could you please verify that the REST API configuration is correct? As a troubleshooting step, can you temporarily remove the REST API task, add a Human Task as the first step in the flow, and check whether the case is being created successfully? This will help us isolate whether the issue is related to the REST API configuration or another part of the flow.
Hi @Sam , Let me try this and update you the response
1 Like
@enochdpm I can see that the case is being generated successfully when using a Human Task without rest api initially. This indicates that the issue is not with BPM itself. The problem may be related to an invalid REST API configuration in the flow. Please try to configure it correctly and test again
Hi @Sam , Yes, I am able to create a case successfully. However, after creating the case, it is not reflecting in the Alpha Admin Portal. Could you please help me check on this.
Could you please confirm whether the case type created in the Alpha project is the same as the case type used during the onboarding of the case definition?
Yes, it is the same case type.
{
"processName": "Motor-POC",
"processVersion": "1.0",
"processDefinitionId": "Enoch_Motor_POC.Motor-POC",
"metadata": {
"containerId": "Enoch_Motor_POC_1.0.0-SNAPSHOT",
"variables": **null**,
"reusableSubProcesses": **null**,
"nodes": **null**,
"timers": **null**,
"tagsByVariable": **null**,
"package": "org.jbpm",
"dynamic": **false**
}
@enochdpm It appears that the required groups were not added to the Human Task in BPM, and the corresponding groups were also not created in Alpha. Although these configurations are expected to be done from your side, we have configured them from our side this time for verification purposes.
Could you please try again and confirm whether you are now able to access the case successfully?
Hi @Sam , I am able to see the case creation in alpha admin portal. Thank you