Problem/Motivation

Create an architecture diagram of the CRM entities to help users and developers understand the system.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork crm-3585324

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mortona2k created an issue. See original summary.

mortona2k’s picture

Assigned: mortona2k » Unassigned
Status: Active » Needs review

Hope this helps!

I'm interested in making better entity diagrams, so any feedback is appreciated.

jdleonard’s picture

Status: Needs review » Reviewed & tested by the community

I ran the (manual) GitLab CI job "Pages", which produced this for easy review: https://crm-3585324-f9a97b.pages.drupalcode.org/entity/

A possible nit is that Relationship stores the references to the Relationship's Contacts as a multivalue "contacts" field (contact_a and contact_b are computed), but this is not represented. However, I think the way the diagram represents contact_a and contact_b lends more clarity for most viewers than representing the contacts property would so I don't recommend a change.

Thank you for your contribution!

bluegeek9’s picture

Status: Reviewed & tested by the community » Fixed
//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support makes this project sustainable.
There are multiple ways to show appreciation for the work contributed to this project including:
  • Triage issues and adding more context to existing issues.
  • Flagging CRM as a favorite on the project page to help others discover it and show your support.
  • Review the Developer Docs for accuracy and clarity.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.