Question
Ltimindtree
SA
Last activity: 6 Jun 2017 7:22 EDT
Mule Pega connector Put operation on cases resource not working
Hi Team,
I am working on a mule POC to use Mule Pega connector. I am using following URL as reference
I am able to make most of the operations except PUT on cases resource.
I am facing issue with PUT operation in the portal it says to send ETag as If-match header which is received in header during get operation or create operation on a case. I tried the same. But, always getting error message that
{
"pxObjClass": "Pega-API-CaseManagement-Case",
"errors": [
{
"ID": "Pega_API_021",
"message": "Unauthorized access: If-Match does not match ETag",
"pxObjClass": "Pega-API-Error"
}
]
}
I am using following URL
header being sent is
If-Match=20170519T063422.162 GMT
Authorization= <something>
Content-Type=application/json
Cache-Control=cache
where if-Match is the value of the etag which we get while doing get for same case.
Could someone please help me on this.
Hi Team,
I am working on a mule POC to use Mule Pega connector. I am using following URL as reference
I am able to make most of the operations except PUT on cases resource.
I am facing issue with PUT operation in the portal it says to send ETag as If-match header which is received in header during get operation or create operation on a case. I tried the same. But, always getting error message that
{
"pxObjClass": "Pega-API-CaseManagement-Case",
"errors": [
{
"ID": "Pega_API_021",
"message": "Unauthorized access: If-Match does not match ETag",
"pxObjClass": "Pega-API-Error"
}
]
}
I am using following URL
header being sent is
If-Match=20170519T063422.162 GMT
Authorization= <something>
Content-Type=application/json
Cache-Control=cache
where if-Match is the value of the etag which we get while doing get for same case.
Could someone please help me on this.
***Moderator Edit: Vidyaranjan | Updated Categories***
Accepted Solution
Pegasystems Inc.
IN
Hi,
in put request ID and ETag are mandatory parameters.
Etag will be available in the response headers after creating a new case
i.e
Hi,
in put request ID and ETag are mandatory parameters.
Etag will be available in the response headers after creating a new case
i.e
Connection: keep-aliveContent-Length: 88Content-Type: application/json;charset=UTF-8Date: Wed, 24 May 2017 08:40:02 GMTEtag: "20170524T084002.488 GMT"Location: https://intel-dt1.pegacloud.io:443/prweb/api/v1/cases/SAND-FW-SDASANDBOXFW-WORK+A-210Server: serverSet-Cookie: JSESSIONID=481E91F66B9B1CB5C0603D08D538472F; Path=/prweb; Secure; HttpOnly
so while updating a case pass ID and Etag values and update us the status.
Ltimindtree
SA
Thanks Narasimha, it worked this way. I was sending null content in body. So, update was happening and ETag was getting changed, i was not noticing that. With the changed etag it is working.