Skip to main content

Employee Integration Events

Summary​

The contracts assembly defines seven Employee integration-event records derived from a common IntegrationEvent base. The records are source-confirmed schemas; consumer support varies by event.

Audience​

  • Producers and consumer developers
  • QA and contract-test engineers
  • Solution architects

Reference Content​

Common metadata​

Every contract includes an event identifier, event type, occurrence time, optional correlation and causation identifiers, optional tenant and user identifiers, source service, and schema version. Employee mappings currently create schema version 1 records and identify Employee Service as the source.

Event-specific field categories​

ContractConfirmed field categories
EmployeeCreatedEventEmployee identifiers, tenant references, employee code, profile/contact projection, organization assignments, status, joining date
EmployeeUpdatedEventEmployee identifiers, tenant references, employee code, profile/contact projection, organization assignments, status
EmployeeDeletedEventEmployee identifier and employee code
ManagerChangedEventEmployee identity plus previous and new manager identifiers
DepartmentChangedEventEmployee identity plus previous and new department identifiers
EmploymentStatusChangedEventEmployee/tenant projection plus previous and new status
EmployeeTimelineEventRecordedEventEmployee identity, timeline type, and description

Some contracts can contain personal data. Consumers and observability systems must avoid logging raw payloads. This portal deliberately provides no populated payload examples.

Contract identity​

The mapping creates a new integration EventId; it does not reuse the internal domain-event identifier. The employee identifier is placed in the mapping's correlation field, while causation, base tenant, and base user metadata are currently null. Tenant reference fields inside applicable Employee payloads remain separate from the nullable base tenant identifier.

Compatibility status​

  • Contract records and the version field are Foundation.
  • A documented compatibility matrix and deprecation window are Not implemented.
  • Whether consumers reject unknown schema versions Requires confirmation; inspected consumers parse selected fields rather than enforcing the base version.

Source References​

  • microservices/src/contracts/Events/IntegrationEvent.cs
  • microservices/src/contracts/Events/EmployeeCreatedEvent.cs
  • microservices/src/contracts/Events/EmployeeUpdatedEvent.cs
  • microservices/src/contracts/Events/EmployeeDeletedEvent.cs
  • microservices/src/contracts/Events/ManagerChangedEvent.cs
  • microservices/src/contracts/Events/DepartmentChangedEvent.cs
  • microservices/src/contracts/Events/EmploymentStatusChangedEvent.cs
  • microservices/src/contracts/Events/EmployeeTimelineEventRecordedEvent.cs
  • microservices/src/employee-service/Infrastructure/EmployeeDbContext.cs

See Also​

Keywords​

  • Shared event contracts
  • Schema version
  • Contract metadata

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly