How cresusjpt/habilite works
This Yii2 application appears to manage internal habilitation requests: users submit requests, which are assigned approval levels and processed through validation and signature steps. The sampled controllers and models support that workflow, alongside user/service administration and PDF generation. The README describes the project as a Material Design Yii2 template rather than documenting these business capabilities; relationships below rely on the sampled source and SOURCE INDEX, so unsampled controllers and integrations are represented cautiously.
Main entry points: Demande.php Habilitation request · NiveauController.php Approval handling · Utilisateur.php User identity · Niveau.php Approval level
Components 21
Request workflow
- Request handling
controllers/DemandeController.php - Habilitation request
models/Demande.php - Approval handling
controllers/NiveauController.php - Approval level
models/Niveau.php - Request state
models/EtatDemande.php - Electronic signature
models/Signature.php - Validation rules
models/Valider.php - Notifications
models/Notification.php
Users and access
- User handling
controllers/UtilisateurController.php - User identity
models/Utilisateur.php - Profiles
models/Profil.php - User profiles
models/UserProfil.php
Reference data
- Habilitation catalog
models/Habilitation.php - Service catalog
models/Service.php - Application parameters
models/SysParam.php
Document output
- PDF utilities
controllers/PDFUtils.php - jsPDF entry
web/jsPDF/main.js - jsPDF core
web/jsPDF/jspdf.js - Canvas rendering
web/jsPDF/plugins/context2d.js
Application runtime
- Application database
config/db.php
Other components
- User
Connections 27
- User → Request handling: submits request
- Request handling → Habilitation request: saves request
controllers/DemandeController.php - Request handling → Approval level: creates levels
controllers/DemandeController.php - Request handling → Habilitation catalog: loads habilitation
controllers/DemandeController.php - Habilitation request → Habilitation catalog: references
models/Demande.php - Habilitation request → User identity: references requester
models/Demande.php - Habilitation request → Approval level: has approval levels
models/Demande.php - Approval handling → Habilitation request: loads request
controllers/NiveauController.php - Approval handling → Approval level: processes level
controllers/NiveauController.php - Approval handling → Request state: checks state
controllers/NiveauController.php - Approval handling → Notifications: uses notifications
controllers/NiveauController.php - Approval handling → Electronic signature: uses signature
controllers/NiveauController.php - Approval handling → Service catalog: loads service
controllers/NiveauController.php - Approval level → Request state: references state
models/Niveau.php - Approval level → Habilitation request: references request
models/Niveau.php - Habilitation catalog → Habilitation request: has requests
models/Habilitation.php - Habilitation catalog → Validation rules: has validation rules
models/Habilitation.php - Service catalog → Validation rules: has validation rules
models/Service.php - User handling → User identity: manages users
- User identity → Service catalog: references service
models/Utilisateur.php - User identity → Electronic signature: has signatures
models/Utilisateur.php - User identity → Profiles: references profiles
models/Profil.php - Profiles → User profiles: uses assignments
models/Profil.php - PDF utilities → Habilitation request: reads request
controllers/PDFUtils.php - PDF utilities → Electronic signature: reads signature
controllers/PDFUtils.php - jsPDF entry → jsPDF core: imports core
web/jsPDF/main.js - jsPDF entry → Canvas rendering: imports plugin
web/jsPDF/main.js