Default Pega API 7.2
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 ?
Accepted Solution
Updated: 10 Jan 2022 4:45 EST
Mphasis
IN
Hi Asif,
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
EPAM Systems, Inc.
ES
Your JSON structures appear to be fine, could you verify it once. Navigate to Resource->Pega API.
Try POST /cases Create a new case. Check the response message.
Mphasis
IN
Asif,
Thanks for the response , i tried the same above response is from Pega API its self. this happens some case type not all so i got this .
Thanks
Chandan U
Accepted Solution
Updated: 10 Jan 2022 4:45 EST
Mphasis
IN
Hi Asif,
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
Pegasystems Inc.
US
Hi Chandan,
No other configuration is needed.
Please share the tracer while work object creation(trace the rest service) and the case designer screenshots.
These would help isolate the issue.
Updated: 19 Jan 2018 8:59 EST
Mphasis
IN
Hi Ravi,
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.