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
Build Wage Enhancements widget as a multi-tiered table. Its very slow with 36 entries (1252ms), so we will likely need to switch to a "tier" selection + paginated table for production usage. Or I'm doing something vue render heresy that is easily avoidable ...
Fixes https://yg-hpw.atlassian.net/browse/ELCC-28
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
Build Wage Enhancements widget as a multi-tiered table. Its very slow with 36 entries (1252ms), so we will likely need to switch to a "tier" selection + paginated table for production usage. Or I'm doing something vue render heresy that is easily avoidable ...
Screenshots
Testing Instructions
dev up