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.

@JamieT47

I’m not completely sure about the requirements. If the intent is to create the case from One App to another Pega Application, then leverage the cases DX API to create the case.

If the intent is to create the case and also advancing the case workflow in the other application, then leverage Remote Case type.

@RameshSangili

the intent is to create an application in application B as part of a case workflow in application A. DX API is the way to do it, but the question is how to invoke the API request, with a savable data page and the api request in the save plan, or with a read only data page and the api request in the source.

@JamieT47 *the intent is to create a case

@JamieT47

Please leverage the case creation API

Create Case POST https://{LabInstanceURL}/prweb/app/retail-banking/api/application/v2/cases?viewType=page Case {
  “caseTypeID”: “ABC-AppName-Work-DXExample”,
  “content”: {},
  “processID”: “pyStartCase”
}

If you’re looking to pass the fields during the case creation, pleaes find the below post

@JamieT47 in addition to what Ramesh has provided, you might find this from @Will Cho to be a good read/inspiration

@MarcCheong That is an excellent example of the option 2 mentioned above, with the Connect REST configured as the data source, thank you very much!