Question
Cognizant
AU
Last activity: 7 May 2021 7:02 EDT
case not appearing in the application which are are created using Pega Rest cases API
Hi,
Case created successfully by Pega Rest cases API without any error
- Not able to see case in the work class instances
- But able to see assignment in the assign-workbasket instances
Created case present in the data base and also not able to fetch by using report definition also. It is strange issue and could you please provide inputs on this.
Maantic Inc
US
Hi Yerasu, Can you check are you passing the correct class name in API request.
I tried in pega v84, it is working fine.
Steps to debug
1. Validate the class name in API request
2. Make sure work object is stored in work table
3. Make sure work table is connected with your class or class group
4. Sample query called when you click on a class instance, it just gets information from the work table and in where clause class name is passed
SELECT "PC0"."pyid" AS "pyID" , "PC0"."pylabel" AS "pyLabel" , "PC0"."pxupdatedatetime" AS "pxUpdateDateTime" , "PC0"."pxupdateopname" AS "pxUpdateOpName" , "PC0"."pzinskey" AS "pzInsKey" FROM pegadata.pc_MyTo_MyTown311_Work "PC0" WHERE "PC0"."pxobjclass" = 'MyTo-MyTown311-Work-Enrollment' ORDER BY 3 DESC
5. Check your Report definition class and where class parameters
Validation screen print
Hi Yerasu, Can you check are you passing the correct class name in API request.
I tried in pega v84, it is working fine.
Steps to debug
1. Validate the class name in API request
2. Make sure work object is stored in work table
3. Make sure work table is connected with your class or class group
4. Sample query called when you click on a class instance, it just gets information from the work table and in where clause class name is passed
SELECT "PC0"."pyid" AS "pyID" , "PC0"."pylabel" AS "pyLabel" , "PC0"."pxupdatedatetime" AS "pxUpdateDateTime" , "PC0"."pxupdateopname" AS "pxUpdateOpName" , "PC0"."pzinskey" AS "pzInsKey" FROM pegadata.pc_MyTo_MyTown311_Work "PC0" WHERE "PC0"."pxobjclass" = 'MyTo-MyTown311-Work-Enrollment' ORDER BY 3 DESC
5. Check your Report definition class and where class parameters
Validation screen print
Updated: 14 Jul 2020 2:51 EDT
Cognizant
AU
Hi John,
Your mentioned points are must required to create case.
All are correct (Workpool, class pointed out correct DB table, context, Commit happening during create case...etc). I have 2 applications, no issues in 8.4.0 and facing issue in 7.4.0 only.
All basic sanity check are verified and all good. Case is created and it is available in the data base and also able to fetch case details using get case details api but it is not showing in the work class instances.
FYI -> report definition used to check whether able to fetch from data base or not.
It is strange issue.
Thanks.
Updated: 14 Jul 2020 20:25 EDT
Cognizant
AU
Here problem with not report definition or query and any way here it is - SELECT "PC0"."PYID" AS "pyID" , "PC0"."PYSTATUSWORK" AS "pyStatusWork" , "PC0"."PYCUSTOMERNAME" AS "pyCustomerName" , "PC0"."PZINSKEY" AS "pzInsKey" , "PC0"."PXCREATEDATETIME" AS "pxCreateDateTime" FROM PEGA_DATA.WorkTableName "PC0" WHERE ( "PC0"."PYSTATUSWORK" NOT LIKE 'Resolved%' AND "PC0"."PYSTATUSWORK" = 'Open-XYZ' );
Yes, Cases are created by using other method are available in the work class instances.
Please note - Cases are created by using create case api without any errors and available in the database, able to fetch case details by GET Case API. Only issue is cases are not appearing in the work class instances.
Updated: 7 May 2021 7:02 EDT
Accenture
DE
@VenkatYerasu Hi PLease check the existing records in the database where you create a case manually. Please check the column pxObjClass.
in API request use the same pxObjClass while passing in casetypeID as it is case sensitive.. very important. Then you will see the case in pega