Wage enhancement section needs more spaces – and the ability to add additional – forgive me if it does this and I just can’t figure it out…
Any given daycare or facility may have multiple personnel at each level of certification (1,2,3). Currently the system only allows for entry of one employee of each type.
Can the system dynamically allocate additional rows for each level as required by the officer entering the information? We don’t want 5 rows for each level for instance as not all of them will be used on a regular basis. The ability to add more rows as needed per level is what is required.
Requirements
pull “Wage enhancements” section out of the “worksheets” tab, and built it its own modeling on and widget on the “Employees” tab.
Current Implementation
Expected Implementation (more or less)
Implementation
Add back-end modeling and set up some minimal UI component paths.
Add seeders for production for models that don't have an edit interface.
employee_wage_tiers Table
Columns:
id: Auto-incremented unique ID.
fiscal_period_id: Links to fiscal_periods.
tier_level: Numeric level of wage tier.
tier_label: Text label (50 chars max).
wage_rate_per_hour: Hourly wage rate.
created_at/updated_at: Timestamps.
Constraints:
Primary Key: id.
Foreign Key: fiscal_period_id.
Index:
Unique on fiscal_period_id and tier_level.
wage_enhancements Table
Columns:
id: Auto-incremented unique ID.
centre_id: Links to centres.
employee_wage_tier_id: Links to employee_wage_tiers.
employee_name: Name of the employee (100 chars max).
Relates to:
Context
Wage enhancement section needs more spaces – and the ability to add additional – forgive me if it does this and I just can’t figure it out…
Any given daycare or facility may have multiple personnel at each level of certification (1,2,3). Currently the system only allows for entry of one employee of each type.
Can the system dynamically allocate additional rows for each level as required by the officer entering the information? We don’t want 5 rows for each level for instance as not all of them will be used on a regular basis. The ability to add more rows as needed per level is what is required.
Requirements
pull “Wage enhancements” section out of the “worksheets” tab, and built it its own modeling on and widget on the “Employees” tab.
Current Implementation
Expected Implementation (more or less)
Implementation
Add back-end modeling and set up some minimal UI component paths. Add seeders for production for models that don't have an edit interface.
employee_wage_tiersTableColumns:
id: Auto-incremented unique ID.fiscal_period_id: Links tofiscal_periods.tier_level: Numeric level of wage tier.tier_label: Text label (50 chars max).wage_rate_per_hour: Hourly wage rate.created_at/updated_at: Timestamps.Constraints:
id.fiscal_period_id.Index:
fiscal_period_idandtier_level.wage_enhancementsTableColumns:
id: Auto-incremented unique ID.centre_id: Links tocentres.employee_wage_tier_id: Links toemployee_wage_tiers.employee_name: Name of the employee (100 chars max).hours_estimated: Estimated work hours.hours_actual: Actual work hours.created_at/updated_at: Timestamps.Constraints:
id.centre_idtocentres.employee_wage_tier_idtoemployee_wage_tiers.Index:
centre_idandemployee_wage_tier_id.Screenshots
Testing Instructions
dev up