Request a login and password from support@admingen.dev, naming “Employee development: custom”. Enter the supplied details on the sign-in page. The demo overview explains access and limitations.
This project uses the same domain model and prepared dataset as the generated HR example. Its difference is the purpose-built Employee · Custom workspace and calculations implemented in custom code.
What was written by hand
| Screen | What to explore |
|---|---|
| Employee overview | The selected person's profile and related information |
| Competency matrix | Required and current competency levels and calculated gaps |
| Development plan | Goals, weighted plan progress and overdue goals |
| Learning catalogue | Learning materials and a type filter |
| Assessment results | Prepared assessment results |
| Manager overview | Team summaries |
The backend custom code calculates combined data, competency gaps, progress and summaries from persistent records. These figures are not a pre-rendered presentation.
What Admingen still generates
Organization, Competencies, Development, Learning, Approvals and Assessments retain the same entity model. Standard record pages and EmployeeProfileView, PlanOverview, CourseOverview remain generated and can be compared with the custom workspace. Virtual views use one relationship hop; the workspace's deeper combined response is implemented separately.
Suggested walkthrough
- Open Employee · Custom and select an employee.
- Switch between Employee overview, Competency matrix and Development plan. Compare requirements, assessments and progress calculations.
- Explore Learning catalogue, Assessment results and Manager overview.
- Open the standard DevelopmentGoal, LearningMaterial and AssessmentResult records used by the custom summaries.
- Inspect Dashboard's model and project structure. Compare with demo4 to see where generation and hand-written development meet.
Both approaches work in one project: evolve the model through the generator and develop the specialised interface and business rules in custom zones. This example does not include every feature of a complete LMS; visitors cannot save data or actions.