Centurio Dokumenty systemowe i modułowe
🔍
🏛️ Architektura platformy
🇩🇪 Deutsch 🇬🇧 English 🇫🇷 Français 🇪🇸 Español 🇮🇹 Italiano 🇳🇱 Nederlands 🇵🇱 Polski 🇵🇹 Português 🇨🇿 Čeština 🇸🇰 Slovenčina 🇭🇺 Magyar 🇷🇴 Română 🇧🇬 Български 🇬🇷 Ελληνικά 🇩🇰 Dansk 🇫🇮 Suomi 🇸🇪 Svenska 🇱🇹 Lietuvių 🇱🇻 Latviešu 🇪🇪 Eesti 🇭🇷 Hrvatski 🇸🇮 Slovenščina 🇲🇹 Malti 🇮🇪 Gaeilge 🇷🇺 Русский 🇺🇦 Українська 🇹🇷 Türkçe 🇳🇴 Norsk bokmål 🇷🇸 Српски 🇮🇸 Íslenska 🇨🇭 Schwiiz/Suisse
🔑 Login
🏠 Wszystkie moduły / crm_office / Kalendarze i konferencje
📘

Kalendarze i konferencje

calendar crm_office 🛡️ RLS Protected

Kalendarze i konferencje <unk> dokumentacja procesowa i API pochodząca z kodu.

Fachliche Bestimmung: Kalendarz Terminów i Konferencji <unk> dokumentacja procesów i API pochodząca z kodu.
⚡ Przepływy pracy i cykle życia (1) 🗄️ Modele danych (4) 🔌 Punkty wyjścia (UI & API) (21) 🛡️ Regulatoryzacja i zgodność

⚡ Przepływy pracy i cykle życia

Wskazówka użytkownika: agent kalendarzowy plan:command_calendar_agent

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

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

🗄️ Modele danych

CalendarAttendees calendar_attendees RLS Aktiv
16 Wyroby

Tabelle calendar_attendees

Feldname Typ danych Wymóg Schlüssel Znaczenie specjalne
event_id UUID Ja * FK ➔ calendar_events.id Feld event_id
user_id UUID Nein FK ➔ users.id Feld user_id
name VARCHAR(255) Nein - Feld name
email VARCHAR(320) Nein - Feld email
required BOOLEAN Ja * - Feld required
response VARCHAR(12) Ja * - Feld response
responded_at DATETIME Nein - Feld responded_at
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
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata
CalendarEvents calendar_events RLS Aktiv
33 Wyroby

Tabelle calendar_events

Feldname Typ danych Wymóg Schlüssel Znaczenie specjalne
title VARCHAR(255) Ja * - Feld title
description TEXT Nein - Feld description
start_time DATETIME Ja * - Feld start_time
end_time DATETIME Ja * - Feld end_time
all_day BOOLEAN Ja * - Feld all_day
event_type VARCHAR(48) Ja * - Feld event_type
color VARCHAR(32) Nein - Feld color
location VARCHAR(255) Nein - Feld location
video_call_url VARCHAR(512) Nein - Feld video_call_url
video_call_provider VARCHAR(32) Ja * - Feld video_call_provider
assigned_user_id UUID Nein FK ➔ users.id Feld assigned_user_id
customer_id UUID Nein FK ➔ customers.id Feld customer_id
entity_type VARCHAR(64) Nein - Feld entity_type
entity_id UUID Nein - Feld entity_id
attendees JSONB Ja * - Feld attendees
organizer_id UUID Nein FK ➔ users.id Feld organizer_id
recurrence JSONB Nein - Feld recurrence
reminder_minutes INTEGER Nein - Feld reminder_minutes
org_unit_id UUID Nein FK ➔ org_units.id Feld org_unit_id
meeting_room_id UUID Nein FK ➔ meeting_rooms.id Feld meeting_room_id
status VARCHAR(32) Ja * - Feld status
visibility VARCHAR(32) Ja * - Feld visibility
ical_uid VARCHAR(128) Ja * - Feld ical_uid
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
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata
deleted_at DATETIME Nein - Feld deleted_at
CalendarFeedTokens calendar_feed_tokens RLS Aktiv
14 Wyroby

Tabelle calendar_feed_tokens

Feldname Typ danych Wymóg Schlüssel Znaczenie specjalne
user_id UUID Ja * FK ➔ users.id Feld user_id
token_hash VARCHAR(64) Ja * - Feld token_hash
label VARCHAR(64) Nein - Feld label
last_used_at DATETIME Nein - Feld last_used_at
revoked_at DATETIME Nein - Feld revoked_at
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
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
metadata JSONB Ja * - Feld metadata
MeetingRooms meeting_rooms RLS Aktiv
18 Wyroby

Tabelle meeting_rooms

Feldname Typ danych Wymóg Schlüssel Znaczenie specjalne
room_key VARCHAR(64) Ja * - Feld room_key
title VARCHAR(255) Ja * - Feld title
kind VARCHAR(8) Ja * - Feld kind
mode VARCHAR(8) Ja * - Feld mode
event_id UUID Nein FK ➔ calendar_events.id Feld event_id
channel_id UUID Nein FK ➔ chat_channels.id Feld channel_id
invited_user_ids JSONB Ja * - Feld invited_user_ids
invited_portal_user_ids JSONB Ja * - Feld invited_portal_user_ids
ended_at DATETIME Nein - Feld ended_at
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
created_by UUID Nein - Feld created_by
updated_by UUID Nein - Feld updated_by
source_type VARCHAR(32) Nein - Feld source_type
source_id UUID Nein - Feld source_id
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/calendar/events/{event_id}
delete_event
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API DELETE /api/v1/calendar/feed-tokens/{token_id}
revoke_feed_token
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API GET /api/v1/calendar/availability
dostępność
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /api/v1/calendar/events
list_events
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /api/v1/calendar/events/{event_id}
get_event
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /api/v1/calendar/feed-tokens
list_feed_tokens
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /calendar
calendar_page
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /calendar/feed.ics
calendar_ical_download
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /calendar/feed/{token}.ics
calendar_ical_subscription
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /calendar/meeting/{room_key}
legacy_meeting_route
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /kalender
calendar_page
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /kalender/feed.ics
calendar_ical_download
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /meeting/{room_key}
meeting_page
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API GET /portal/{slug}/termine
appointments_page
Semantic binding: inventory_only; mutation=False
 calendar
⚡ REST API PATCH /api/v1/calendar/events/{event_id}
update_event
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API POST /api/v1/calendar/events
create_event
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API POST /api/v1/calendar/events/{event_id}/respond
odpowiedz
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API POST /api/v1/calendar/feed-tokens
create_feed_token
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API POST /api/v1/calendar/meetings/quick-room
quick_room
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API POST /portal/{slug}/termine/anfragen
appointment_request
Semantic binding: operator_surface; mutation=True
 calendar
⚡ REST API POST /portal/{slug}/termine/anfragen/{request_id}/stornieren
appointment_request_cancel
Semantic binding: operator_surface; mutation=True
 calendar

🛡️ 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.