Customize Pega DX API bad request response
Hi everyone!
In our app we use the Pega cases DX API to trigger case creation.
Is there any way to customize the ootb bad request response (http 400) for this API?
Thank you already so much for your input!
Updated: 17 Sep 2023 17:37 EDT
Sopra Steria
NL
DKB Code Factory
DE
@BasRulesMatter Hi :)!
Thanks so much for your response. I checked said decision table but still don't exacetly know how you would go on from there. Sorry, I'm a junior dev :D.
As far as I understand the response configuration of the REST service for case creation, I would need to configure a new Response parameter to modifiy the response message -> which I can't because all the activities are final/internal. A work around would be to have a constant message sent back, but to set it dynamically based on Clipboard data would of course be way better.
Could you elaborate a bit more on your approach please?
Sopra Steria
NL
@Franz H So you cannot specialize the activities or decision table, but you can save the fields values in a ruleset and / or class that is specific to your application. I'll post an example later this afternoon :)
@Franz HHi,
OOTB uses the decision table pzSetErrorDetail for API errors. I checked a few field values that are referenced therein and most are at the very least not final / internal. Note that these are quite generic but you can always use class and ruleset specialization.