Events

use Escalated\Laravel\Events\TicketCreated;

Event::listen(TicketCreated::class, function ($event) {
    // $event->ticket
});

Verfügbare Events

• TicketCreated -- Neues Ticket eingereicht
• TicketStatusChanged -- Statusübergang
• TicketPriorityChanged -- Priorität aktualisiert
• TicketAssigned -- Agent dem Ticket zugewiesen
• TicketUnassigned -- Agent vom Ticket entfernt
• ReplyCreated -- Öffentliche Antwort hinzugefügt
• InternalNoteAdded -- Interne Agenten-Notiz
• TicketUpdated -- Ticket-Metadaten geändert
• TicketReopened -- Ticket in aktiven Zustand zurückversetzt
• DepartmentChanged -- Abteilung neu zugewiesen
• TagAddedToTicket -- Tag auf Ticket angewendet
• TagRemovedFromTicket -- Tag vom Ticket entfernt
• SlaWarning -- Ticket nähert sich der SLA-Frist
• SlaBreached -- SLA-Frist überschritten
• TicketEscalated -- Ticket durch Regel eskaliert
• TicketResolved -- Ticket als gelöst markiert
• TicketClosed -- Ticket geschlossen

Events werden über ActiveSupport::Notifications ausgelöst. Abonnieren Sie mit ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Events werden über Django-Signale ausgelöst. Verbinden Sie mit escalated.signals.ticket_created.connect(handler).

Events werden über den AdonisJS Event Emitter ausgelöst. Abonnieren Sie mit emitter.on('escalated:ticket:created', handler).

Filament verwendet dieselben Laravel-Events von escalated-laravel. Hören Sie auf diese genauso wie beim Standard-Laravel-Paket.

Events werden über WordPress-Action-Hooks ausgelöst. Verwenden Sie add_action('escalated_ticket_created', $callback), um auf Ticket-Lebenszyklus-Events zu hören.

Events are dispatched server-side through your backend's native event system. The Flutter package does not implement a client-side event bus.

Reactive Data

The package uses Riverpod providers that automatically refresh data when mutations occur. When a user creates a ticket, adds a reply, or changes a status, the relevant providers invalidate and re-fetch automatically.

// Ticket list stays up-to-date after creating a new ticket
final tickets = ref.watch(ticketListProvider);

// Replies refresh after posting
final replies = ref.watch(ticketRepliesProvider(ticketId));

No manual event listeners or refresh logic is needed — the provider system handles cache invalidation for you.

Note: If you need to react to server-side events (e.g., real-time agent replies), configure push notifications through your backend and handle them at the platform level.

Events are dispatched server-side through your backend's native event system. The React Native package does not implement a client-side event bus.

Reactive Data

The package uses React Query, which automatically handles cache invalidation when mutations succeed. When a user creates a ticket, adds a reply, or changes a status, the relevant queries re-fetch automatically.

import { useCreateTicket, useTickets } from '@escalated-dev/escalated-react-native';

function TicketListScreen() {
  const { data: tickets } = useTickets();
  const createTicket = useCreateTicket(); // invalidates ticket list query on success

  return (
    // Ticket list stays current — no manual refresh needed
  );
}

No manual event listeners or refresh logic is needed — React Query handles cache invalidation for you.

Note: If you need to react to server-side events (e.g., real-time agent replies), configure push notifications through your backend and handle them at the platform level.