Closed ddgriffin closed 10 years ago
OR
Hey Bethany! Just wanted to add a little more context here. The comments above were my initial thoughts on how this might work - but if you can think of a better way, by all means, go for it!
One thing to keep in mind is that we'll likely end up wanting to have the "Close Applications" button turn into a "Re-open Applications" button after it's been closed, with the effect of reversing the change and allowing applications again. I don't know if this is true, but in my head it seems like it would be easier to set a field value back and forth between true and false, rather than transition the state forward and back between "accepted" (ie. open for applications) and "filled" (closed for applications). We definitely see more errors around state changes in general, probably because we also have a lot of logic hinging on the state.
Done and Done!
We need a "close applications" button for makers who have set a high number of apprenticeships and then decide that they have enough apprentices without "filling" their quota