Documentation Index
Fetch the complete documentation index at: https://mintlify.com/DanielRivera03/SistemaBancario/llms.txt
Use this file to discover all available pages before exploring further.
CashMan H.A. provides two complementary communication layers: a structured internal messaging system that lets any user send and receive messages within the platform, and an automated notification system that fires database triggers whenever noteworthy events occur. Additionally, all roles have access to a bug report / ticketing system to surface platform issues to the administration team. Together these tools keep all five roles — Administrator, Presidency, Management, Customer Service, and Client — informed without relying on external email for internal coordination.
Internal Messaging
All five roles have full access to the messaging module. Messages are composed with a subject and body, addressed to any registered user, and delivered to the recipient’s inbox within the platform.
mensajeria Table Fields
| Column | Description |
|---|
idmensajeria | Unique message identifier |
idusuarios | Sender’s user ID |
idusuariodestinatario | Recipient’s user ID |
nombre | Sender’s display name |
asunto | Message subject |
detalle | Message body |
fecha | Timestamp of when the message was sent |
Messaging Operations
| Operation | Model Method | Stored Procedure |
|---|
| Send a new message | EnvioNuevosMensajes_MensajeriaInternaCashmanHa() | RegistroNuevosMensajesUsuarios_MensajeriaCashManHa |
| View inbox | ConsultarMensajesBandejaEntradaUsuarios() | ConsultaMensajesBandejaEntradaUsuariosCashmanHa |
| View message detail | ConsultarDetallesMensajesBandejaEntradaUsuarios() | ConsultarDetallesMensajesBandejaEntradaUsuariosCashmanHa |
| Get recipient list | ConsultarListadoUsuariosCompleto_MensajeriaCashmanHa() | ConsultaNombresCompletos_EnviarMensajeriaNuevaUsuariosCashManHa |
| Hide / archive message | OcultarMensajes_MensajeriaInternaCashmanHa() | OcultarMensajesRecibidos_MensajeriaInternaUsuariosCashManHa |
// Example — send a new internal message
$objGestiones->setIdUsuarioDestinatarioMensajeria($_POST['destinatario']);
$objGestiones->setAsuntoMensajeria($_POST['asunto']);
$objGestiones->setDetalleMensajeria($_POST['detalle']);
$resultado = $objGestiones->EnvioNuevosMensajes_MensajeriaInternaCashmanHa();
Automated Notifications
The notification system is event-driven and requires no manual intervention. Notifications are generated automatically by a database trigger whenever a new internal message is delivered.
Trigger: EnvioNotificacionNuevosMensajesUsuarios
This trigger fires AFTER INSERT on the mensajeria table and inserts a corresponding row into the notificaciones table for the recipient. This ensures that every new message also creates a real-time notification visible in the platform toolbar.
Notification Operations
| Operation | Model Method | Stored Procedure |
|---|
| View full notifications list | MostrarListadoNotificacionesRecibidasUsuarios() | ConsultarNotificacionesRecibidasUsuarios |
| Toolbar (trimmed) notifications | MostrarListadoNotificacionesRecortadaRecibidasUsuarios() | ConsultaNotificacionesRecortada_BarraHerramientasPlataforma |
| Dismiss a notification | OcultarMisNotificacionesUsuarios() | OcultarNotificacionesRecibidasUsuarios |
ConsultaNotificacionesRecortada_BarraHerramientasPlataforma) returns a limited, trimmed set of the most recent notifications — suited for display in the top navigation bar without overwhelming the UI. The full list query returns the complete notification history for the current user.
// Fetch trimmed notifications for the toolbar badge
$resultado = $objGestiones->MostrarListadoNotificacionesRecortadaRecibidasUsuarios();
Bug Reports & Support Tickets
Any authenticated user across all five roles can submit a platform issue report. These tickets are managed by the Administration team and can be updated as issues are investigated and resolved.
| Column | Description |
|---|
idreporte | Unique ticket identifier |
nombre | Issue title / short description |
descripcion | Detailed issue description |
estado | Ticket state: open or closed |
empleadogestionando | Admin or staff member currently managing the ticket |
Ticket Operations
| Operation | Model Method | Stored Procedure |
|---|
| Submit a new ticket | RegistroFallosPlataforma_TicketsUsuarios() | RegistroReportesFallosPlataforma |
| List all tickets (admin) | ConsultaTicketsReportesFallosPlataforma() | ConsultaCompleta_ReportesFallosPlataforma |
| View single ticket | ConsultaEspecificaTicketsReportesFallosPlataforma() | ConsultaEspecifica_ReportesFallosPlataforma |
| Update ticket | ActualizacionFallosPlataforma_TicketsUsuarios() | ActualizacionTicketsReportesFallosPlataforma |
// Submit a new bug report
$objGestiones->setNombreReportePlataforma($_POST['nombre']);
$objGestiones->setDescripcionReportePlataforma($_POST['descripcion']);
$resultado = $objGestiones->RegistroFallosPlataforma_TicketsUsuarios();
Use the single ticket view (ConsultaEspecificaTicketsReportesFallosPlataforma) when building a ticket detail page — it fetches all fields including empleadogestionando and estado, so the UI can show assignment and resolution status without querying the full list.