Overview

Fact: a pendency left the OPEN state by the hand of its responsible, with outcome DONE or DECLINED. By design the payload carries only the id: a consumer re-reads the pendency’s current state instead of trusting a snapshot.

When it is published. CNA NexusCNA NexusService•v1.0.0Franchise network back-office (franchises, economic groups, partners, contracts and amendments, document storage, AI doc...PublishesInviteUser, ContractActivationRequested +13SubscribesContractActivationRequested, AmendmentApplyRequested +4Ownercna-platformMapRepoView docs, in resolvePendency, reached from the GraphQL mutation of the same name: after validating that the caller is the responsible and the pendency is still OPEN, the status, the note and resolvedAt are written and the producer is awaited. No transaction and no afterCommit. A CANCELLED closure does not publish.

Consumers. None in cna-auth, cna-nexus, cna-one or cna-placement. The intended reader is the process that created the pendency, so it can continue its flow; no such process exists yet.

Kafka

Payload schema

Source of truth

type PendencyResolvedPayload = {
  id: string;
};

export class PendencyResolved extends Event<PendencyResolvedPayload> {
  static readonly owner = "NEXUS";
  static readonly aggregateRoot = "Pendency";
  static readonly routingKey = "id";
}

The class exists only in cna-nexus.