Перейти к содержимому
Nawras Bukhari
Написать
Работы
Enterprise CRMПубличное анонимизированное

Operational CRM

Software ArchitectureBackend EngineeringTechnical Leadership

Relationships, workflows, permissions, and a path off a legacy system

Domain modeling and workflow engineering

Контекст

The previous CRM could not express the real graph: institutes related to contacts related to applicants related to tasks, with permissions that were not “admin or not.”

Граница системы

В системе

  • relationship model
  • filters
  • boards
  • permissions
  • migration

Вне системы

marketing automation blasts

Архитектура

Entities are nodes with typed edges. Status is a workflow on an entity, not a column that everyone edits. Permissions attach to relationship and role, not to a hidden screen flag.

An anonymized operational CRM: institutes, contacts, applicants, tasks, statuses, and granular permissions — including migration from a legacy store.
  1. Institutes
  2. Contacts
  3. Applicants
  4. Tasks
  5. Statuses
  6. Permissions
  • Typed edges
  • Permissions are data
Опубликованная последовательность
  1. Institutes
  2. Contacts
  3. Applicants
  4. Tasks
  5. Statuses
  6. Permissions
Этапы в каждом ряду
  • Ряд 12Contacts · Applicants
  • Ряд 23Tasks · Statuses · Permissions
Роли на схеме
  • сервис2
  • процесс1
  • хранилище2
  • интерфейс1

Счётчики из опубликованной записи. Они описывают структуру, а не измеренный результат.

Как связаны домены системы?

relationships

  • хранилищеInstitutes
  • хранилищеContacts

workflow

  • процессApplicants
  • сервисTasks
  • сервисStatuses

policy

  • интерфейсPermissions
  1. InstitutesContacts
  2. InstitutesApplicants
  3. ContactsApplicants
  4. ApplicantsTasks
  5. ApplicantsStatuses
  6. ContactsPermissions
  7. InstitutesPermissions

Критические потоки

  1. An institute owns contacts

  2. an applicant is linked

  3. tasks and statuses move the case

  4. permission checks decide who sees which edge.

Этапы

  • Relationship graph
  • Applicant workflows
  • Granular permissions
  • Operational boards

Решения

01

Graph before screens

If the model cannot say “this contact at this institute,” the UI will lie.

02

Permissions are data

A new role must be configurable without a deploy. Hardcoded admin checks do not survive the client.

03

Migrate with dual write, then cut

Legacy import is a project. Shadow reads until the graph is complete.

Когда что-то ломается

УсловиеОбнаружениеРеакция
Orphan applicantRequired institute/contact edgeBlock create
Permission missPolicy denyEmpty result, not 500
Legacy id collisionImport keymapHalt batch; keep map

Инфраструктура

  • Application
  • relational store
  • search/filter indexes
  • queued migration jobs
  • audit of permission changes

Результат

Operations run on an explicit relationship graph with permissions that match how the organisation actually works.

Текущее состояние

In production as an anonymized public record. Legacy cutover complete for the published scope.