Hi All,

I'm building a new greenfield Mortgage Origination application using Pega Constellation, and my application is built on top of Pega Common Application / Common Data Model (CDM).

While creating my first case type and defining the data model, I want to follow the best-practice approach for capturing mortgage application details.

Requirement

In my Mortgage Application case type, I need to capture and store the following information within the case:

1. Applicants (Embedded PageList)

• Capture multiple applicants (Primary + Co-applicant)

• Each applicant should include:

  • Personal details

  • Employment details (may have multiple employments)

  • Income details (may have multiple income sources)

  • Outgoings / commitments

2. Property (Embedded Page)

• Capture property details for the mortgage application

• Property is not linked to an individual applicant

• Property is common/shared for both applicant

    3. Some additional data model

Questions / Guidance Needed

1. Should I create these embedded data objects (Applicant / Property) in my implementation layer as embedded pages (Page / PageList) and store them in the case?

2. Should I use the Contact entity from Common Application / CDM to represent applicants instead of creating my own embedded Applicant structure?

3. What is the recommended approach for Constellation mortgage applications:

• Use CDM Contact entity only

• Create my own embedded Applicant & Property data objects

• Follow a Hybrid approach (embedded applicant pages + link to Contact entity using ContactID)

4. Where should I build the views (UI) for these objects?

• In Common Data Model / Common Application classes

• Or in my implementation layer classes (Mortgage case class + embedded data object classes)

I’m looking for expert recommendations / best practices for modeling Applicants & Property in a Constellation-based Mortgage application built on Common Application.

Thanks in advance!