MDC_Product_Delivery_Scenario_Requirements.pdf
(330.25 KB)
Challenge
Creating the delivery service and MDC applications
Creating the delivery service and MDC applications
5 Tasks
1 hr
Advanced
English
Scenario
Metro Delivery Company (MDC) assists its business partners in booking delivery requests for intra-city shipments of various sizes from one location to another. MDC wants to use the features of Pega Platform™ to automate its business processes, including partner registration, truck vendor registration, delivery service booking, and invoicing.
Your challenge: architect a Pega solution for MDC.
As part of the mission, create a delivery service solution for MDC. Using the business scenario document, apply your knowledge from each module to design the best technical solution that meets MDC's vision to Build for Change®.
The following PDF file contains the detailed MDC Product Delivery scenario requirements document:
Each challenge includes a unique scenario and assignment that identifies the specific business problem to address. Before attempting each challenge, review the scenario and assignment to understand the goal of the challenge.
The following table provides the credentials you need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Administrator | [email protected] | install123! (applicable for VM) |
| Administrator | admin@deliveryservice | rules |
| Administrator | admin@MDC | rules |
Detailed Tasks
1 Establish your challenge system
Pega Academy provides an opportunity for you to practice what you learn. Two system options are available:
Pega Academy provides two different exercise systems for you to complete the exercises:
- Cloud instance (online)
- Virtual Machine (VM) (offline)
The cloud instance (when available) is accessible by clicking Initialize Pega instance for this Challenge in the Scenario section. The cloud instance is the preferred option in Pega Platform because it reflects the container-based, cloud-native deployment architecture that is now the strategic direction for all Pega applications.
The VM is made available as an Open Virtualization Archive (OVA) file that contains a compressed, "installable" version of a virtual machine. Note that as of Pega Infinity '25, VM-based deployments are considered legacy. Pega's strategic direction is toward Kubernetes-orchestrated, cloud-native deployments. The VM option is provided for offline learning purposes only.
You can use any VM Player of your choosing, such as VirtualBox (Windows, macOS), VMWare Player (Windows), or VMware Fusion (macOS). You are responsible for downloading and installing your own VM player.
Exercise VM archive
The exercise VM is available as an OVA file that contains a compressed, "installable" version of a virtual machine. You can download the VM OVA file by using the following link:
The OVA file is approximately 11 GB and can take a while to download. Because of the large file size, the best practice is to use Chrome or Mozilla to complete the download.
Review the Pega Virtual Machine User Guide for crucial information on configuring the exercise VM correctly. Visit the respective website to access instructions on the latest version of the user guide.
Use your virtualization software (VM Player) to open, import, and extract the OVA file.
Although Pega does not provide a VM Player for you to use, use one of the following recommended players:
- VirtualBox (Windows, macOS)
- VMWare Player (Windows)
- VMware Fusion (macOS)
The VM User Guide provides details on downloading and importing the OVA file, and on running the VM with one of the recommended VM players. You are responsible for downloading and installing your own VM player.
You must import the MDC Delivery Service solution RAP file provided into your Pega Platform instance after you install the Linux-Lite VM. To enable all operator IDs during the import of the RAP file, select the Enable advanced mode to provide more granular control over the import process and Enable new operators and overwrite existing operators on import options.
2 Determine the Delivery Service application structure
After a thorough analysis of the MDC requirements, the following architectural conclusions guide the application design:
- Separate individual Case Types are required to handle processes related to Business partner registration, Renewal, Truck vendor registration, Delivery request, Truck request, and Invoice.
- A parent-child Case relationship is a better approach for handling the truck vendor enrollment and approval by different city managers in parallel. This pattern avoids process bottlenecks and aligns with Pega Case hierarchy design for parallel processing.
All Case Types and UI rules should be built using the Constellation architecture. This ensures access to the latest platform features, ongoing maintenance support, and a modern, responsive user experience.
3 Review the construction of the MDC Enterprise application
An enterprise application does not need to include Case Types. The primary purpose of the enterprise application is to provide a standardized Data Model and other reusable record types, such as Libraries. This description refers to the MDC enterprise application, which, in theory, the MDC center of excellence (COE) group maintains.
4 Review the construction of the production delivery service application
The production Delivery Service application is assembled on top of several component applications: Truck Service, Truck Request, Delivery Request, Registration, and Invoice. This highly modular approach is deliberately chosen to:
- Support parallel development across teams to accelerate delivery timelines.
- Align with the Pega microservices strategy, which favors smaller, independently deployable applications instead of monolithic architectures.
- Simplify maintenance, testing, and future extension without large-scale refactoring.
Every Case Type defined within a built-on application must be extended through direct inheritance to develop and test it within the Delivery Service application. The process is:
- Import each Case Type into a separate Ruleset in the Delivery Service application.
- Update the direct inheritance of the generated Case Type class so that it references the class of its corresponding Case Type in the built‑on application.
Note: Edit Case Types only in the built‑on application. Editing Case Types in multiple applications can place Rules in incorrect layers or Rulesets, which is a critical concern for Lead System Architects.
5 Review solution download
If you are using the offline local virtual machine, you must download and import the MDC delivery service solution RAP file provided at the beginning of the challenge. To enable all operator IDs during import of the RAP file, select the Enable advanced mode to provide more granular control over the import process and Enable new operators and overwrite existing operators on import checkboxes.
Available in the following mission:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?