Hey folks,
has anyone worked with any out of the box XDM field groups or classes for insurances?
Which would they be, and are they a good starting point or do they require a lot of adaptation work?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @bjoern__koth - The below OOTB field group and class looks good to utilize for the insurance use cases. However, it should be coming along with "XDM Individual profile" schema and you may come across to use the object array concepts to ingest data that would accommodate more on insurance side. Again, it depends on the use case that you gonna implement it for the insurance, as you may need to customize the XDM model utilizing those OOTB components. Moreover, I would suggest to stick with standard component (what you are looking for) to make more reliable on the relationships between these schema and to avoid conflicts on the data side. Please let me know if you have any specific related questions.
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/policy
Field Group - Insurance Claim Process
Thank you,
Jayakrishnaa P.
Hi @bjoern__koth - The below OOTB field group and class looks good to utilize for the insurance use cases. However, it should be coming along with "XDM Individual profile" schema and you may come across to use the object array concepts to ingest data that would accommodate more on insurance side. Again, it depends on the use case that you gonna implement it for the insurance, as you may need to customize the XDM model utilizing those OOTB components. Moreover, I would suggest to stick with standard component (what you are looking for) to make more reliable on the relationships between these schema and to avoid conflicts on the data side. Please let me know if you have any specific related questions.
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/policy
Field Group - Insurance Claim Process
Thank you,
Jayakrishnaa P.
Thx! Yeah I found that one, too. Also, every company is different, so I know there is no one-fits-all schema.
Will give it a try