We have a two schools of thought on the best way to create a case in one Pega application from another Pega application by using a Data Page and Connect REST request to utilise the DX API. In a scenario such as a ‘Procurement Request’ case in a Supply Management application wanting to create a ‘Vendor Request’ case in a separate Procurement application. What would be the recommended best practice out of the options below, or something else?
Option 1 - Use a savable API data page with a stub data transform as the source and the REST connector etc in the data save options. This data page can be called with a save data page step in your case type.
Option 2 - Use a read only API data page with the REST connector etc as the source. This data page can then be called via flow action post processing, from a data transform or activity etc.
@JamieT47 Can you try using a savable API data page and call it with a Save Data Page step from the flow (Option 1). A savable data page is meant for create/update work, so it cleanly separates mapping (data transform) from the REST call (save plan) and gives you predictable error handling and commits. Keep the page requestor-scoped with no caching so it is used only for the create action, not reused accidentally. Build the DX API payload in the page’s parameter/data transform, run the Connect-REST in the save plan, and capture the new case ID from the response. This keeps case logic in the case type and integration logic in one controlled, reusable integration asset.
When creating savable data page/read only data page with pega create case constellation dx api ,always getting 401 unauthenticated issue.The same client registration is working fien when invoking from pega api swagger or postman.initially it was giving PRRuntimeException exception ,then I changed the TLS version to 1.2 instead of 1.3 ,it still giving 401 error.Any specific change I need to do in client registration to make it work?
Would you mind regenerate the secret and try again? I’ve faced a similar issue and I’ve attempted the same from 1.3 to 1.2 and then regenerated the secret.
I did the same,what I found is when I was recreating the same thing from one of our cloud environments (from my organisation) it was working.when I am using pega academy exercise system,it is not able to create client registration.I think some security restriction is blocking creating the Client cred only for exercise system.
While creating any Connector with or without Auth profile is giving the below error. This happens in all pega academy lab environments. Any idea how to fix this ?
SSL/TLS configuration issue detected. Please repair and try again.
Caught Exception while creating OAuth2 client
Unable to obtain access token for client details in authentication profile configured for connector. AuthProfile = ConnectShipment: PRRuntimeException
javax.net.ssl.SSLProtocolException: (unexpected_message) Received close_notify during handshake
Sorry, I never got a chance to check it on the Academy instance. I’m not sure if there is a limitation in Academy instances. It works on community edition, personal lab instances, other customer specific instances.