I am developing an application that tracks a person's employment, wages, and how they change while within a program the person has enrolled in.
This also means there are three types of jobs:
- Jobs that ended before enrolled in the program - we only want to collect their beginning wage and ending wage here.
- Jobs that started before enrollment, but are ongoing while enrolled in the program - we want the beginning wage and then want to track any changes to their wage from the date of enrollment forward.
- Jobs that begin while in-program - similar to the last, as we want the beginning wage and any change.
My solution is by using two sets of fields:
Set 2: (repeatable, only visible for the 2nd and 3rd job type)
Date of Change
Here's the problem with this: I would have to update the "Current/Final Wage" value in Set 1 with the last "Amount" in Set 2 automatically, or validate that the user did this on their own. This feels wrong. I'd rather the design doesn't require that changing one field leads to a separate field changing automatically.
Any other suggestions on how to fix this problem?