Etag removal form mandatory header parameter in Constellation API
Hi Team,
Is it possible to remove Etag / If-Match from the required header parameter in constellation API. In our application a Micro service layer orchestrate these api, and it sometimes difficult to maintain these etag values for each Patch call.
We are working on Pega 8.8.0 on react built on application and using DX API V2
Pegasystems Inc.
IN
Hi It is always suggested to ensure you leverage eTag - benefit of this is to ensure you are performing data update on the latest/recent most copy of a record. this way pega ensures transaction consistency is maintained.
It is not a good design choice to get rid of Etag.
instead of maintaining Etag value - you could GET the recent most last dated date time and pass the same in the ETag.
Rabobank
NL
Thanks for the response.
In our project we are using constellation API to just update the case assignment and move ahead in the flow. As MS layer trigger these updates and it will be an API addition to just get an ETAG value and then use it in Patch api to update the case.
Increasing the API calls is also not a good solution design and it increases maintenance.
Hence wanted to know if there is any way to get rid of etag mandatory input parameter in constellation API's.
Pegasystems Inc.
IN
Additional API Call vs Database Transaction consistency - give priority transaction consistency only even if it is making an additional call.