when I open the Case created there is no page pxFlow. any configuration we need to follow ?
Hi guys,
Need some assistance,
I am using the OOTB Pega API to create the Case
Request :
{
"caseTypeID": "ORT5RH-Fx-Work-CompanyInfo",
"processID": "pyStartCase",
"parentCaseID": "",
"content": {"AccountName": "user","LegalCompanyName": "com"}
}
Response :
{
"ID": "ORT5RH-FEDEX-WORK C-733",
"pxObjClass": "Pega-API-CaseManagement-Case"
}
Problem statement : when I open the Case created Eg: C-733 there is no page pxFlow. any configuration we need to follow ?
***Updated by moderator: Lochan to branch reply and create new posts***
Pegasystems Inc.
IN
Hi Chandan,
Thanks for writing to PSC.
How you are invoking the rest service?
Kindly follow the below steps to test:
1. Open the Pega API landing page :
2. Go to cases >post/cases and add your request body and test if it is working there and share the screen shot.
If your request can be accessible over internet, kindly share full request details, so I can test and debug.
Thanks:
Gurpreet
Mphasis
IN
Hi Gurpreet,
Thanks for the response, above issue was on some instance reason was not known, now its working fine.
Senario 2 :
I tried this on the cloud space provided by pega i was able to create the case using the pega OOTB API.
Same think i tried hitting the request URL from 3rd party app call POSTMAN, i am getting status 304 NOT Modified.
Any think i need to to case when doing on cloud ? This is because i need to try this in cloud in realtime application as well.
URL : -
Method :- Post
Request :
{
"caseTypeID": "TGB-HRApps-Work-Learning",
"processID": "pyStartCase",
"parentCaseID": "",
"content": {
"FirstName": "sample text",
"Location": "sample text",
}
}
Response : 304 Status.
Authentication used : Basic authentication
please find the attachment.
Thanks
ChandaN U
JPMorgan Chase & Company
US
Hi,
The request is processed successfully please check once, 304 response is to minimize information transfer when the recipient already has one or more cached representations, a sender SHOULD NOT generate representation metadata other than the above listed fields unless said metadata exists for the purpose of guiding cache updates.