Feature/panales operaciones refactoring - #45
Merged
Conversation
- Updated role names: Químico -> Jefe de Sede - Updated permission matrix with correct access levels per role - Added M3_PRODUCTOS read access for Jefe de Sede - Added CATEGORIAS read access for Técnico - Added M10_REPORTES for Técnico - Renumbered RF-01 to RF-36 to fill gaps - Added RF-21: global patient listing - Added RF-22: auto-generate recipe number - Added RF-31: role hierarchy validation - Added RF-32: permission assignment via checkboxes - Added RF-33-RF-36: category and user management - Added ID format reference table - Updated credentials to match new ID format
…ission inserts to DELETE+INSERT
- UsuarioRepository: add countMovimientosByUsuario, countAtencionesByUsuario, delete - GestionarUsuarioUseCase: add eliminarUsuario with history check - UserAdapter: add eliminarUsuario method - UsuarioController: add delete button (fas-trash) and handleDeleteUser - If user has history (movimientos or atenciones): show warning to use deactivate - If user has no history: delete physically - users-view.fxml: column width 120px to fit 4 buttons
- PacienteController: fix handleDelete to show NO_HISTORY warning instead of silently soft-deleting; separate desactivarPaciente() from eliminarPaciente(); fix handleToggleBlock to call desactivarPaciente() not eliminarPaciente() - GestionarPacienteUseCase: eliminarPaciente() now returns NO_HISTORY when patient has atencion history (no silent soft-delete); add desactivarPaciente() - PacienteAdapter: add desactivarPaciente() method - UsuarioController: add confirmation dialog before hard delete - SedeController: add delete button (fas-trash) to actions column with confirmation dialog and NO_HISTORY warning - SedeAdapter/SedeRepository/JdbcSedeRepository: add eliminarSede() with 4-way history check (usuarios, lotes, movimientos, atenciones) - add RF-26 (user deletion), detail RF-29/RF-30 (PDF columns exported) - fix RF-05/RF-17/RF-20/RF-36 descriptions: explain physical vs logical delete pattern clearly for Word documentation
…ontext - Changed the default growth message from "N/A" to "Sin datos suficientes" for better clarity when insufficient data is available in the report generation process.
…zation - Updated ID formats for Paciente, Lote, Atención, and Detalle de Atención to include additional digits for consistency. - Introduced new entities: Movimiento for inventory tracking, with sample data for both current and previous months. - Corrected SQL syntax in dbdiagram.md for role table definition. - Enhanced REQUERIMIENTOS.md to reflect updated ID formats and new entity definitions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.