DX API - Case Creation
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.
Accepted Solution
Updated: 1 Feb 2026 12:18 EST
HCA Healthcare
US
@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.
Sixworks Ltd
GB
@SairohithThat’s exactly the sort of explanation/reasoning we were looking for one way or the other, thank you!