📘

Przeprowadzanie i badania dokumentów

circulations crm_office 🛡️ RLS Protected

Dokumentenumläufe & Prüfungen — aus Code abgeleitete Prozess- und API-Dokumentation.

Fachliche Bestimmung: Dokumenty i badania <unk> dokumentacja procesów i API pochodząca z kodu.

⚡ Przepływy pracy i cykle życia (2) 🗄️ Modele danych (3) 🔌 Punkty wyjścia (UI & API) (23) 🛡️ Regulatoryzacja i zgodność

⚡ Przepływy pracy i cykle życia

Wskazówka użytkownika: środek do obrotu `plan:command_circulation_agent`

Sprawdzony plan trwały (durable_plan), start: manual_command.

1. circulation_agent

circulation_agent

{"key": "execute_command", "label": "Befehl prüfen, ausführen oder zur Freigabe vorlegen", "adapter": "agent.execute", "agent": "circulation_agent", "condition_fact": null}

Aktionen: circulation_agent

Wykorzystanie `status:circulation`

W przypadku, gdy urządzenie jest w stanie obserwowanym (only observable_only), nie ma konieczności dokonywania przechodów.

1. draft

wdrażanie

Status <unk>draft <unk> ruchu maszyny stanu.

2. active

aktywne

Status <unk>aktywny <unk> ruch maszyny stanu.

3. completed

wypełnione

Status <unk> zakończony <unk> ruch maszyny stanu.

4. rejected

Odmowa

Status <unk> odrzucony <unk> ruch maszyny stanu.

5. returned

zwrócone

Status <unk>wrócony <unk> ruch maszyny stanu.

6. cancelled

odwołane

Status <unk>annulwany <unk> ruch maszyny stanu.

🗄️ Modele danych

CirculationComments circulation_comments RLS Aktiv

13 Wyroby

Tabelle circulation_comments

Feldname	Typ danych	Wymóg	Schlüssel	Znaczenie specjalne
`circulation_id`	`UUID`	Ja *	FK ➔ document_circulations.id	Feld circulation_id
`step_id`	`UUID`	Nein	FK ➔ circulation_steps.id	Feld step_id
`document_id`	`UUID`	Ja *	FK ➔ documents.id	Feld document_id
`author_id`	`UUID`	Nein	FK ➔ organization_users.id	Feld author_id
`page`	`INTEGER`	Ja *	-	Feld page
`x`	`FLOAT`	Ja *	-	Feld x
`y`	`FLOAT`	Ja *	-	Feld y
`text`	`TEXT`	Ja *	-	Feld text
`id`	`UUID`	Nein	PK	Feld id
`tenant_id`	`UUID`	Ja *	FK ➔ organizations.id	Feld tenant_id
`created_at`	`DATETIME`	Ja *	-	Feld created_at
`updated_at`	`DATETIME`	Ja *	-	Feld updated_at
`metadata`	`JSONB`	Ja *	-	Feld metadata

CirculationStamps circulation_stamps RLS Aktiv

16 Wyroby

Tabelle circulation_stamps

Feldname	Typ danych	Wymóg	Schlüssel	Znaczenie specjalne
`circulation_id`	`UUID`	Ja *	FK ➔ document_circulations.id	Feld circulation_id
`step_id`	`UUID`	Nein	FK ➔ circulation_steps.id	Feld step_id
`document_id`	`UUID`	Ja *	FK ➔ documents.id	Feld document_id
`placed_by`	`UUID`	Nein	FK ➔ organization_users.id	Feld placed_by
`page`	`INTEGER`	Ja *	-	Feld page
`x`	`FLOAT`	Ja *	-	Feld x
`y`	`FLOAT`	Ja *	-	Feld y
`width`	`FLOAT`	Ja *	-	Feld width
`height`	`FLOAT`	Ja *	-	Feld height
`text`	`VARCHAR(255)`	Ja *	-	Feld text
`color`	`VARCHAR(7)`	Ja *	-	Feld color
`id`	`UUID`	Nein	PK	Feld id
`tenant_id`	`UUID`	Ja *	FK ➔ organizations.id	Feld tenant_id
`created_at`	`DATETIME`	Ja *	-	Feld created_at
`updated_at`	`DATETIME`	Ja *	-	Feld updated_at
`metadata`	`JSONB`	Ja *	-	Feld metadata

CirculationSteps circulation_steps RLS Aktiv

17 Wyroby

Tabelle circulation_steps

Feldname	Typ danych	Wymóg	Schlüssel	Znaczenie specjalne
`circulation_id`	`UUID`	Ja *	FK ➔ document_circulations.id	Feld circulation_id
`position`	`INTEGER`	Ja *	-	Feld position
`assignee_id`	`UUID`	Ja *	FK ➔ organization_users.id	Feld assignee_id
`status`	`VARCHAR(48)`	Ja *	-	Feld status
`instructions`	`TEXT`	Nein	-	Feld instructions
`assigned_at`	`DATETIME`	Nein	-	Feld assigned_at
`started_at`	`DATETIME`	Nein	-	Feld started_at
`completed_at`	`DATETIME`	Nein	-	Feld completed_at
`decision`	`VARCHAR(32)`	Nein	-	Feld decision
`notes`	`TEXT`	Nein	-	Feld notes
`due_at`	`DATETIME`	Nein	-	Feld due_at
`decision_comment`	`TEXT`	Nein	-	Feld decision_comment
`id`	`UUID`	Nein	PK	Feld id
`tenant_id`	`UUID`	Ja *	FK ➔ organizations.id	Feld tenant_id
`created_at`	`DATETIME`	Ja *	-	Feld created_at
`updated_at`	`DATETIME`	Ja *	-	Feld updated_at
`metadata`	`JSONB`	Ja *	-	Feld metadata

🔌 Punkty wyjścia (UI & API)

Art	Wykorzystanie	Punkt końcowy / droga	Titel & Zweck	Właściwości
⚡ REST API	DELETE	`/api/v1/circulations/{circulation_id}/assignees/{step_id}`	remove_assignee Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	DELETE	`/api/v1/circulations/{circulation_id}/documents/{document_id}`	remove_document Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	GET	`/api/v1/circulations`	list_circulations Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	GET	`/api/v1/circulations/{circulation_id}`	get_circulation Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	GET	`/api/v1/circulations/{circulation_id}/documents/{document_id}/preview`	document_preview Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	GET	`/api/v1/circulations/{circulation_id}/final-pdf`	download_final_pdf Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	GET	`/circulations`	circulations_page Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	GET	`/circulations/new`	circulation_create_page Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	GET	`/circulations/{circulation_id}`	circulation_detail_page Semantic binding: not_evaluated; mutation=False	`circulations`
⚡ REST API	PATCH	`/api/v1/circulations/{circulation_id}`	update_circulation Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	PATCH	`/api/v1/circulations/{circulation_id}/assignees/{step_id}`	update_assignee Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations`	create_circulation Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/assignees`	add_assignee Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/begin-review`	begin_review Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/cancel`	cancel_circulation Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/comments`	add_comment Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/complete-step`	complete_step Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/documents`	add_document Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/return`	return_for_revision Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/stamps`	add_stamp Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/start`	start_circulation Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/steps/reorder`	reorder_steps Semantic binding: not_evaluated; mutation=True	`circulations`
⚡ REST API	POST	`/api/v1/circulations/{circulation_id}/upload`	upload_document Semantic binding: not_evaluated; mutation=True	`circulations`

🛡️ Regulatoryzacja i zgodność

Dieses Modul unterliegt folgenden gesetzlichen, regulatorischen und Revisionsstandards:

Wykrywalność
W przypadku gdy systemy i systemy są w stanie być wyłączone, systemy i systemy identyfikacyjne mogą być wykorzystywane w celu zapewnienia zgodności z wymogami określonymi w art. 2 ust. 1 lit. a) i b) niniejszego rozporządzenia.