Centurio Documentación de sistemas y módulos
🔍
🏛️ Arquitectura de la plataforma
🇩🇪 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
🏠 Todos los módulos / crm_office / Entradas y servicio de ayuda
🎧

Entradas y servicio de ayuda

tickets crm_office 🛡️ RLS Protected

Los servicios de asistencia al cliente, los niveles de escalación de SLA, el encaminamiento de los boletos y la vinculación con las órdenes y el portal de clientes.

Fachliche Bestimmung: Canaliza las solicitudes de los clientes, las notificaciones de problemas y las órdenes de servicio. Los boletos se pueden crear directamente desde el portal de clientes, por correo electrónico o manualmente.
⚡ Flujos de trabajo y ciclos de vida (6) 🗄️ Modelos de datos y campos (5) 🔌 Puntos de inicio (UI y API) (27) 🛡️ Regulación y cumplimiento

⚡ Flujos de trabajo y ciclos de vida

Tratamiento completo cascade:business.delivery_note.intake

Cascada (review_gated)

1. stock
Entradas de mercancías en las cuentas de la
Inventario
Aktionen: post_goods_receipt
2. tour
Plan de viaje / transporte
Servicios de transporte
Aktionen: create_tour
3. task
Verificación / comparación de las entradas de mercancías
tareas
Aktionen: create_task
4. qc
Verificación de calidad en caso de sospecha de defectos
Inventario
Aktionen: calidad.check.create
5. ticket
Tickets de reclamación en caso de defectos
Tickets
Aktionen: create_ticket

mantenimiento / Restauración cascade:business.maintenance.cycle

Cascada (review_gated)

1. fieldservice
Recopilación de los gastos de servicio exterior
Servicio de campo
Aktionen: create_service_report
2. followup
Planificación de los sucesos de mantenimiento
Activos
Aktionen: mantenimiento.
3. ticket
Tickets en caso de defecto/disturbio
Tickets
Aktionen: create_ticket

Tratamiento de devoluciones cascade:business.return_note.handling

Cascada (review_gated)

1. ticket
Tickets de reclamación
Tickets
Aktionen: create_ticket
2. tour
Planar el viaje de recogida
Servicios de transporte
Aktionen: create_tour
3. task
Artículo 1o
tareas
Aktionen: create_task

Servicio exterior → Cuentas cascade:business.work_report.billing

Cascada (review_gated)

1. fieldservice
El ejercicio de la actividad de servicio exterior
Servicio de campo
Aktionen: create_service_report
2. task
Traslado de las cuentas
tareas
Aktionen: create_task
3. ticket
Tickets en caso de defecto/disturbio
Tickets
Aktionen: create_ticket

Entrada / pasaje cascade_target:business.ticket.create

Cascada (review_gated)

1. cascade
Entrada / pasaje

Tickets status:ticket

Las operaciones de la máquina de estado observable (solo observable) no se obligan a realizar.

1. new
Nuevo
Estado de la máquina de estado de entrada.
2. open
de la
Estado de la máquina de estado de entrada.
3. in_progress
in_progress
Estado <unk>in_progress<unk> del ticket de máquina de estado.
4. pending_customer
pending_customer
Estado de la máquina de espera del boleto.
5. pending_vendor
pending_vendor
Estado de la máquina de la entrada en circulación.
6. resolved
Resolvido
Estado de la máquina de estado de la entrada.
7. closed
cerrado
Estado de la máquina de estado de entrada.
8. cancelled
cancelado
Estado de la máquina de estado cancelada.

🗄️ Modelos de datos y campos

TicketMessages ticket_messages RLS Aktiv
16 Cálculos y columnas

Tabelle ticket_messages

Feldname Tipo de datos Obligado Schlüssel Importancia profesional
ticket_id UUID Ja * FK ➔ tickets.id Feld ticket_id
author_user_id UUID Nein FK ➔ users.id Feld author_user_id
author_name VARCHAR(255) Ja * - Feld author_name
author_email VARCHAR(255) Nein - Feld author_email
is_internal BOOLEAN Ja * - Feld is_internal
body TEXT Ja * - Feld body
attachments JSONB Nein - Feld attachments
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
TicketSlaPolicies ticket_sla_policies RLS Aktiv
16 Cálculos y columnas

Tabelle ticket_sla_policies

Feldname Tipo de datos Obligado Schlüssel Importancia profesional
name VARCHAR(128) Ja * - Feld name
description TEXT Nein - Feld description
team_id UUID Nein FK ➔ ticket_teams.id Feld team_id
priority VARCHAR(16) Nein - Feld priority
target_response_hours NUMERIC(6, 2) Ja * - Feld target_response_hours
target_resolution_hours NUMERIC(6, 2) Ja * - Feld target_resolution_hours
is_active BOOLEAN Ja * - Feld is_active
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
TicketTeams ticket_teams RLS Aktiv
17 Cálculos y columnas

Tabelle ticket_teams

Feldname Tipo de datos Obligado Schlüssel Importancia profesional
name VARCHAR(128) Ja * - Feld name
code VARCHAR(32) Ja * - Feld code
description TEXT Nein - Feld description
email_alias VARCHAR(128) Nein - Feld email_alias
assignment_method VARCHAR(32) Ja * - Feld assignment_method
lead_user_id UUID Nein FK ➔ users.id Feld lead_user_id
is_active BOOLEAN Ja * - Feld is_active
color VARCHAR(16) 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
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
TicketTimeLogs ticket_time_logs RLS Aktiv
15 Cálculos y columnas

Tabelle ticket_time_logs

Feldname Tipo de datos Obligado Schlüssel Importancia profesional
ticket_id UUID Ja * FK ➔ tickets.id Feld ticket_id
user_id UUID Nein FK ➔ users.id Feld user_id
work_date DATE Ja * - Feld work_date
hours NUMERIC(6, 2) Ja * - Feld hours
is_billable BOOLEAN Ja * - Feld is_billable
description TEXT Nein - Feld description
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
Tickets tickets RLS Aktiv
49 Cálculos y columnas

Tabelle tickets

Feldname Tipo de datos Obligado Schlüssel Importancia profesional
ticket_number VARCHAR(32) Ja * - Feld ticket_number
title VARCHAR(255) Ja * - Feld title
description TEXT Nein - Feld description
status VARCHAR(48) Ja * - Feld status
priority VARCHAR(48) Ja * - Feld priority
category VARCHAR(48) Ja * - Feld category
channel VARCHAR(48) Ja * - Feld channel
team_id UUID Nein FK ➔ ticket_teams.id Feld team_id
assigned_user_id UUID Nein FK ➔ users.id Feld assigned_user_id
customer_id UUID Nein FK ➔ customers.id Feld customer_id
contact_name VARCHAR(255) Nein - Feld contact_name
contact_email VARCHAR(255) Nein - Feld contact_email
contact_phone VARCHAR(64) Nein - Feld contact_phone
project_id UUID Nein FK ➔ projects.id Feld project_id
work_order_id UUID Nein FK ➔ work_orders.id Feld work_order_id
contract_id UUID Nein FK ➔ contracts.id Feld contract_id
asset_id UUID Nein FK ➔ assets.id Feld asset_id
quote_id UUID Nein FK ➔ quotes.id Feld quote_id
invoice_id UUID Nein FK ➔ invoices.id Feld invoice_id
return_id UUID Nein FK ➔ return_orders.id Feld return_id
service_report_id UUID Nein FK ➔ service_reports.id Feld service_report_id
sla_policy_id UUID Nein FK ➔ ticket_sla_policies.id Feld sla_policy_id
sla_status VARCHAR(48) Ja * - Feld sla_status
response_due_at DATETIME Nein - Feld response_due_at
first_responded_at DATETIME Nein - Feld first_responded_at
resolution_due_at DATETIME Nein - Feld resolution_due_at
resolved_at DATETIME Nein - Feld resolved_at
closed_at DATETIME Nein - Feld closed_at
is_billable BOOLEAN Ja * - Feld is_billable
hourly_rate NUMERIC(14, 2) Nein - Feld hourly_rate
currency VARCHAR(3) Ja * - Feld currency
planned_hours NUMERIC(8, 2) Nein - Feld planned_hours
logged_hours NUMERIC(8, 2) Ja * - Feld logged_hours
csat_rating INTEGER Nein - Feld csat_rating
csat_comment TEXT Nein - Feld csat_comment
csat_submitted_at DATETIME Nein - Feld csat_submitted_at
resolution_summary TEXT Nein - Feld resolution_summary
tags JSONB Nein - Feld tags
custom_fields JSONB Nein - Feld custom_fields
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

🔌 Puntos de inicio (UI y API)

Art El método Punto final / camino Titel & Zweck Reacción
⚡ REST API GET /api/v1/tickets
list_tickets
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /api/v1/tickets/sla-policies
list_sla_policies
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /api/v1/tickets/stats
get_ticket_stats
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /api/v1/tickets/teams
list_teams
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /api/v1/tickets/{ticket_id}
get_ticket
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /api/v1/tickets/{ticket_id}/messages
list_ticket_messages
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /api/v1/tickets/{ticket_id}/timelogs
list_ticket_timelogs
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /portal/{slug}/tickets
tickets_page
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /portal/{slug}/tickets/{ticket_id}
ticket_detail
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /tickets
tickets_page
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /tickets/new
ticket_create_page
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API GET /tickets/{ticket_id}
ticket_detail_page
Semantic binding: inventory_only; mutation=False
 tickets
⚡ REST API PATCH /api/v1/tickets/teams/{team_id}
update_team
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets
create_ticket
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/sla-policies
create_sla_policy
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/teams
create_team
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/create-project
create_project_from_ticket
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/create-task
create_task_from_ticket
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/create-work-order
create_work_order_from_ticket
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/csat
submit_ticket_csat
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/messages
add_ticket_message
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/status
transition_ticket_status
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /api/v1/tickets/{ticket_id}/timelogs
log_ticket_time
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /portal/{slug}/tickets
ticket_create
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /portal/{slug}/tickets/{ticket_id}/abschliessen
ticket_close
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API POST /portal/{slug}/tickets/{ticket_id}/antwort
ticket_reply
Semantic binding: operator_surface; mutation=True
 tickets
⚡ REST API PUT /api/v1/tickets/{ticket_id}
update_ticket
Semantic binding: operator_surface; mutation=True
 tickets

🛡️ Regulación y cumplimiento

Dieses Modul unterliegt folgenden gesetzlichen, regulatorischen und Revisionsstandards:

  • Operaciones de servicios de ITIL
  • Supervisión por plazo de los AAE
Modulos vinculados:
➔ customers ➔ portal ➔ workorders