Data model considerations

Use existing APIs to create flexible, real-time connections between your Constellation application and external systems. This approach supports basic create, read, update, and delete (CRUD) operations with data stored outside of Pega Platform so that you can maintain real-time data access while using the standardized structure that Pega provides with Customer Service.

Customer Service includes an API layer that client applications use to interact with both local and external data sources.

This approach includes the following key benefits:

• Real-time data synchronization.
• Flexible integration with multiple external systems.
• Standardized data structure.
• Reduced impact when adding, editing, or removing integrations.

Consider this approach when your application requires immediate access to frequently changing external data or when you need to integrate with multiple external systems that provide REST or SOAP APIs.

Use your existing Customer Service application connectors to interact with external systems through structured, bulk data operations. This method is ideal when you need to pull or push data in bulk or when working with legacy systems that require specific connection protocols.

Connectors provide preconfigured integration features. When you override the default Data Pages with new integration connectors, you help ensure that data flows between the user interface and external databases.

This approach includes the following key benefits:

• Structured integration with external databases.
• Support for bulk data operations.
• Compatibility with legacy systems.
• Centralized data transform logic and auto-mapping fields.

Use this approach when your existing Customer Service application already includes connector configurations that you want to preserve, or when external systems require specific protocols that APIs do not support.

Use Data Pages to manage data retrieval and caching in your Pega application. This approach creates a layer that encapsulates data access logic and improves performance through caching.

You can configure Data Pages to pull data from both local and external sources. They use connectors to access external systems and provide a consistent interface for data access in your application.

This approach includes the following key benefits:

• Efficient data retrieval and caching.
• Consistent data access interface.
• Performance optimization through data caching.
• Support for both local and external data sources.

Choose this approach when you want to display data from multiple sources in a single user interface or when performance optimization through data caching is a priority for your application.

Use this approach to align your local data with the standardized schema provided by Constellation. Migrating your data supports long-term maintainability and ensures full compatibility with the Constellation architecture.

By default, all Customer Service entities use internal or local storage, meaning data is stored in the database of your Pega application. Migrating this data helps you follow Pega best practices and prepares your application for future scalability requirements.

The migration process involves several key steps:

• Conduct a full assessment of existing data assets.
• Use the Constellation Modernization Assistant to identify migration requirements.
• Map your existing data model to the Customer Service entities.
• Identify reusable features for modular implementation.
• Implement data transformation logic to align with standards.

This approach includes the following key benefits:

• Complete alignment with Constellation architecture.
• Standardized data structure that follows Pega best practices.
• Enhanced data reuse across applications.
• Scalable foundation for application growth.

Choose this approach when you want to use the provided framework and when your existing data structure can be effectively mapped to Customer Service entities. This option provides the strongest framework for long-term application development and maintenance.