Rhythm 2.0 Specifications

Appearance

FAS-CRM-ENT-04Affiliations and Roles acceptance

Markdown

FAS-CRM-ENT-04

Affiliations and Roles acceptance

Markdown
  • DocumentProposed
  • Product intentProposed

Planning

Feature
FEAT-CRM-ENT-04
Capabilities
CAP-CRM-ENT-009, CAP-CRM-ENT-010, CAP-CRM-ENT-011

Product areaCRMModuleEntitiesRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Affiliations and Roles: Feature Acceptance Suite ​

What the Feature Must Do as a Whole ​

The suite follows a person’s organizational relationship through creation, dated changes and responsibilities. It checks the relationship’s saved information alongside the calendar-driven outcomes that depend on it. Permission and regression cases exercise these outcomes with controlled grants and dates.

Interactions Between Capabilities ​

The future-relationship case joins calendar reconciliation with automatic role assignment. Each dependent outcome is checked after the relationship becomes current; the suite retains the capability scenarios that specify the separate date and role checks.

Regression Record ​

RevisionChangeScenarioWhy
1initialallEstablish the feature acceptance suite from the planning and design contracts.
2continuation examinationallRewrite the suite explanation, verify its evidence and restore source-backed bindings where available.

Scenarios

5 scenarios proving FEAT-CRM-ENT-04 as a whole.

01 Record an employer and its responsibilities behaviour proposed
Exercises
CAP-CRM-ENT-009 CAP-CRM-ENT-010 CAP-CRM-ENT-011
Relies on
ATS-CRM-ENT-009-11 ATS-CRM-ENT-010-01 ATS-CRM-ENT-011-05
Preconditions
The workspace has a default employer type and an eligible automatic role.
Steps
Set a person’s primary organization on the workspace day and read its relationship and responsibilities.
Expected
The saved relationship identifies the employer, effective dates and eligible responsibilities consistently.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
Source
rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md
02 A future tie acquires responsibilities when it becomes current interaction proposed
Exercises
CAP-CRM-ENT-009 CAP-CRM-ENT-010 CAP-CRM-ENT-011
Relies on
ATS-CRM-ENT-009-07 ATS-CRM-ENT-010-04 ATS-CRM-ENT-011-06
Preconditions
A future affiliation has a permitted automatic role and the workspace date can be controlled.
Steps
Inspect it before its start, reconcile on its start day and inspect the person and organization people list.
Expected
The tie becomes current and receives due responsibilities; the two record perspectives agree.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
Source
rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md
03 Move an employer and preserve the former service period lifecycle proposed
Exercises
CAP-CRM-ENT-009 CAP-CRM-ENT-010 CAP-CRM-ENT-011
Relies on
ATS-CRM-ENT-009-16 ATS-CRM-ENT-011-03 ATS-CRM-ENT-010-01
Preconditions
A person has a primary employer affiliation with open responsibilities.
Steps
Choose a new primary employer and end the earlier stay; inspect current and past views and the ended responsibility periods.
Expected
The new primary is current, the former stay remains as dated history and its open responsibilities end with that stay.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
Source
rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md
04 Organization authority does not authorize a person’s relationship edit permissionnegative proposed
Exercises
CAP-CRM-ENT-009 CAP-CRM-ENT-010 CAP-CRM-ENT-011
Relies on
ATS-CRM-ENT-009-15 ATS-CRM-ENT-010-06 ATS-CRM-ENT-011-04
Preconditions
A caller reads organizations but lacks contact update and bulk authority.
Steps
Attempt a person affiliation correction and a date reconciliation request; verify the person afterward.
Expected
Both unauthorized mutations are refused and the saved relationships and responsibilities remain intact.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
Source
rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md
05 Concurrent first joins establish one first-contact assignment regressionnegative proposed
Exercises
CAP-CRM-ENT-009 CAP-CRM-ENT-010 CAP-CRM-ENT-011
Relies on
ATS-CRM-ENT-011-11 ATS-CRM-ENT-009-04 ATS-CRM-ENT-010-01
Preconditions
An empty organization has an active first-contact role and several eligible people.
Steps
Join the people concurrently on the same workspace day; read each resulting relationship and role list.
Expected
The relationships are saved and exactly one person receives the first-contact responsibility.
Data
Run-owned people, organizations, classifications and definitions in an isolated workspace; controlled calendar or failure fixtures where the case requires them.
Source
rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-009-record-who-works-where-and-the-person-s-primary-organization.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-010-keep-affiliations-true-to-the-workspace-s-calendar.md; rhythm-v2-docs:specs/crm/entities/planning/capabilities/CAP-CRM-ENT-011-give-people-roles-at-their-organizations-automatically-where.md

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software