Eventi

use Escalated\Laravel\Events\TicketCreated;

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

Eventi disponibili

• TicketCreated -- Nuovo ticket inviato
• TicketStatusChanged -- Transizione di stato
• TicketPriorityChanged -- Priorità aggiornata
• TicketAssigned -- Agente assegnato al ticket
• TicketUnassigned -- Agente rimosso dal ticket
• ReplyCreated -- Risposta pubblica aggiunta
• InternalNoteAdded -- Nota interna dell'agente
• TicketUpdated -- Metadati del ticket modificati
• TicketReopened -- Ticket riportato allo stato attivo
• DepartmentChanged -- Dipartimento riassegnato
• TagAddedToTicket -- Tag applicato al ticket
• TagRemovedFromTicket -- Tag rimosso dal ticket
• SlaWarning -- Ticket in avvicinamento alla scadenza SLA
• SlaBreached -- Scadenza SLA superata
• TicketEscalated -- Ticket sottoposto a escalation dalla regola
• TicketResolved -- Ticket contrassegnato come risolto
• TicketClosed -- Ticket chiuso

Gli eventi vengono inviati tramite ActiveSupport::Notifications. Sottoscrivi con ActiveSupport::Notifications.subscribe("escalated.ticket_created").

Gli eventi vengono inviati tramite i signal di Django. Collegati con escalated.signals.ticket_created.connect(handler).

Gli eventi vengono inviati tramite l'event emitter di AdonisJS. Sottoscrivi con emitter.on('escalated:ticket:created', handler).

Filament utilizza gli stessi eventi Laravel di escalated-laravel. Ascoltali esattamente come faresti con il pacchetto Laravel standard.

Gli eventi vengono inviati tramite gli action hook di WordPress. Usa add_action('escalated_ticket_created', $callback) per ascoltare gli eventi del ciclo di vita dei ticket.

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.