mirror of
https://github.com/Tria-plc/edr-platform.git
synced 2026-08-30 02:58:11 +00:00
fd5aedcec7
Two review-workflow gaps for freight customer onboarding: Request for change per document. Backoffice can now flag a single uploaded document (company document, profile licence, or POA delegation letter) with a note the customer sees, instead of rejecting the whole role over it. Adds review_status/review_note/reviewed_by/reviewed_at to freight.files (migration AddFileReviewStatus, partial index for the gate), a POST documents/:fileId/request-change endpoint, the backoffice action + modal, and a portal banner/badge so the customer knows what to re-upload. Re-uploading clears the flag. Approving a role is blocked while any of its documents has an open correction; the gate check and the status write share a pessimistic write lock on the company row (as does the change-request write) so a correction can never slip in between the check and the profile going Active. Resubmission is visible to reviewers. When a customer resubmits a rejected role or amends a change request, backoffice staff are notified (allBackoffice inbox item, deep-linked to the customer) and the resubmission surfaces in a new "Pending changes" list view + KPI, since such companies are status = active and never matched the pending-approval filter.
12 lines
317 B
TypeScript
12 lines
317 B
TypeScript
import { ApiProperty } from "@nestjs/swagger";
|
|
import { IsString, MaxLength, MinLength } from "class-validator";
|
|
|
|
export class RequestDocumentChangeDto {
|
|
/** What is wrong with this document — shown verbatim to the customer. */
|
|
@ApiProperty()
|
|
@IsString()
|
|
@MinLength(1)
|
|
@MaxLength(2000)
|
|
note!: string;
|
|
}
|