@muhammadirfanalif https://academy.pega.com/challenge/importing-and-exporting-content/v4

Exporting Cases (Instance Data)

To export case data (not just the case type definition), you’ll need to use Data Types and Data Pages or BIX (Business Intelligence Exchange):

Option 1: Using BIX (Business Intelligence Exchange)

1. Enable BIX: Ensure BIX is installed and configured in your environment.

2. Create an Extract Rule:

   • Go to Records > SysAdmin > Extract.

   • Create a new extract rule for your case class (e.g., MyApp-Work-MyCaseType).

3. Configure Output Format:

   • Choose CSV, XML, or database table.

   • Select the properties you want to export.

4. Run the Extract:

   • Use the BIX command-line utility or schedule it via an agent.

   • Exported files will be saved to your configured location.

Option 2: Using Data Pages and REST API

1. Create a Data Page:

   • Define a data page that sources case data using a report definition or activity.

2. Expose via REST API:

   • Create a REST service that returns the data page content.

   • Use tools like Postman or scripts to call the API and save the data externally.

 Importing Cases

Importing case data is more complex because it involves creating new case instances:

Option 1: Using File Listener or REST API

1. Prepare the Data File:

   • Format your case data in CSV or JSON.

2. Create a File Listener (for CSV):

   • Define a file listener that reads the file and maps data to a case creation activity.

   • Use a Parse Delimited rule to interpret the CSV.

3. Create REST Service (for JSON):

   • Build a REST service that accepts JSON payloads.

   • Use a service activity to create cases using pxCreateTopCase.

Option 2: Using Data Import Wizard (for Data Types)

• If your case relies on reference data (e.g., dropdowns, configurations), you can import that using:

  • Records > Data Types > Import

  • Upload CSV and map fields accordingly.  

@muhammadirfanalif

create a Product rule that includes your case type rulesets, data types, access roles, queue processors, and any dependencies; export a RAP and import it into the 24.1 target (or use Deployment Manager). After importing design, reindex search, clear caches, and smoke-test by creating a new case. To move existing case instances (usually for testing, not general promotion), Option A is BIX: extract the work class and related classes to XML/CSV with a manifest, copy attachments from your repository (S3/Azure) to the target, then run the BIX import on the target and rebuild search indexes. Option B is Archive/Restore: if both environments point to the same repository, archive selected cases in source and restore them in target to keep history and attachments intact. Option C is to recreate via APIs: read the source case data and POST /cases (DX/Case API) on the target; you’ll get a functional copy but not the original ID, full audit, or assignments. Before any instance import, pause agents/queue processors and SLAs on the target, ensure the same ruleset versions and data schema exist, then resume after verification. Always run Rebuild Search and, if needed, Reconcile Assignments after loading instances; fix broken references (operators, work queues, data pages). For attachments, copy the files to the target bucket/prefix and confirm the Data-Repository configuration; otherwise attachment links will break. For large refreshes, work with DBAs to clone/restore the data schema into non-prod, then update system name, endpoints, and clear caches.