Hi, I have the following scenario in my PEGA Constellation architecture:

I have three layers:

• Business Application: This contains my business case type.

• Modular Layer: Contains all the modules, such as Customer and Credit.

• Enterprise Layer: Holds global assets for all applications.

Doubt:

In the Customer module, I need to register more than one type of address (Residential and Work). In the Credit module, I only need to register one address (Delivery address for sending the product).

Given this, I have three options:

1. Create the Address object in each module, but this would lead to duplication and rework.

2. Create an Address module to centralize the information, but this would break PEGA's best practices, as modules should not be interdependent. I would need to add the Address module as a "Built on Application" in both Customer and Credit.

3. Create the Address object in the Enterprise layer (e.g., as ABC-Data-ObjAddress) and define ObjAddress properties in each module according to the required address type.

In this scenario, if someone has had similar needs related to linking objects, what is the best practice in PEGA Constellation to handle these situations where modules should remain independent, as recommended by PEGA?

Thanks for your time!