Question
Capgemini
NO
Last activity: 8 Jan 2025 5:28 EST
Support for URL mapping in Pega constellation
We are refactoring our existing Theme-Cosmos app to the Constellation app in Pega 24.1. In the current app, we have a functionality where a case is created for a specific patient and shown to the user when they call Pega from another journal application using a parameterized URL defined in the Pega URL mapping rule. Example below.
https://pega-url/patient/******
In the URL mapping rule, we create a case using the svcAddWorkObject activity and use the DoUIAction activity to display the created case.
I noticed that Pega Constellation has out-of-the-box (OOTB) URL Mapping support for existing cases, according to this document: Generating a URL to access a case [SDR-81] | Support Center
Does Pega Constellation support this method of creating and displaying a newly created case to users based on parameters passed in the URL? If so, could you please provide some documentation?
Pegasystems Inc.
CA
Can you please explore using V2 DX API to create the case from the Journal application? You can also pass the starting fields as part of the case creation API.
https://docs.pega.com/bundle/dx-api/page/platform/dx-api/adding-case-creation-fields-v2.html
Thanks,
Ramesh
Capgemini
NO
@RameshSangili Thanks for the suggestion. But in this usecase, We have to create a case via the parameterized URL and show the created case in the Constellation Work Portal for users to proceed further filling other information as well. I dont think it is possible via Service Rest.
Do you have any on thoughts on the above?
Rabobank
NL
@duraisankar Were you able to find a solution ?
Pegasystems Inc.
CA
Sorry, passing parameters as part of the URL to create the case may not be extendable for future cases. For example, if another app wants to send the description, which is 5000 chars, then we have a limitation as part of URL parameters.
With the help of DX APIs V2, you can pass the properties required for the case creation and define the starting fields in the data transform. This can be easily extended for your future requirements and easier maintenance. I understand it's a change required from another application, but it is worth making the change from URL parameters to Request body considering the long term.