Each time I create a new Diversion record and select a Caseworker, a Failed to Save error message appears in the top right corner of the screen. In some cases, the Caseworker name is still saved. In other cases, the Caseworker selection does not save.
My current assessment is that the Diversion module may not be handling custom Reason for Service values correctly.
Test 1 – Used a Standard Lookup Value
I created a Diversion record using a standard Reason for Service lookup option. When I added a Good or Service through the Diversion record, the same Reason for Service value auto-populated into the Good/Service record.
Result: Worked as expected.
Test 2 – Used a Custom Lookup Value
I created a Diversion record using one of our custom Reason for Serv…
In Housing Placements, the Search Ended Date field shows the latest of:
Final Follow Up
Final Attempt
Move-In Date
But Follow Ups happen, by definition, after the search has ended, so adding a Follow Up should not affect the Search Ended Date
Attestation seems not to remember whether a user attested or not.
Might be isolated to just the Hamilton instance.
The attestation pop up is very slow to load. Sometimes so slow that it won't load at all and you are stuck with a black screen. If you refresh then it loads eventually.
Might be isolated to the Hamilton instance.