Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Relationship or spine table included with the Pega Customer Relationship Management for Healthcare suite

Updated on September 13, 2021

A cross-reference spine table is available for you to match the common data types that exist in both the applications. For example, the Pega® Customer Service for Healthcare application contains customer data and the same customer data is also available in the form of customer, lead, opportunity, or prospect in Pega Sales Automation for Healthcare. You must specify the matching IDs from both systems of record to identify the matching data and display the same data to the end user.

Contact relationship table

The crm_entity_contact-xref table shows the contact relationship table structure and sample record pattern.

CRMEntityIDExternalIDExternalSystem
PEGACRM-ENTITY-CONTACT CON-1001MB201507248CSHC
PEGACRM-ENTITY-CONTACT CON-1002MB201507249CSHC
PEGACRM-ENTITY-CONTACT CON-1003MB201608261512CSHC
PEGACRM-ENTITY-CONTACT CON-1004MB201608261513CSHC
PEGACRM-ENTITY-CONTACT CON-1005CONT-31241CSHC
PEGACRM-ENTITY-CONTACT CON-1006CONT-31228CSHC
PEGACRM-ENTITY-CONTACT CON-1007CONT-31239CSHC
PEGACRM-ENTITY-CONTACT CON-1008CONT-31198CSHC

Relationship management table mappings

The PegaCRM-Data-EntityxRef-Contact data class is mapped to the crm_data_contact_xref table. All of the above rules, classes, and properties are available in the PegaCRMBase application.

  • Previous topic Sample components included with the Pega Customer Relationship Management for Healthcare suite
  • Next topic Data model for the Pega Customer Relationship Management for Healthcare suite

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us