Summary
Coordinating the amount of research and resources it takes to create an ERD is no easy feat, but it is the blueprint for the rest of your design and well worth the effort. Taking the time to properly diagram your build will pay dividends in the future: it will be easier to explain your vision to your stakeholders, all while simplifying building instructions to your administrators and developers. Keep your initial ERDs as an artifact and add to them as you expand on your build work.
In this chapter, you learned the following:
- What data elements are needed to achieve our features
- Which standard objects would work with our scenarios
- When to leverage a custom object or non-Sales and Service Cloud object
- How to design against KPIs
- How to identify sensitive data and determine required security protocol based on audience
- How to account for third-party systems that may need to integrate into your Experience Cloud build and create an enterprise architecture...
