Assessment Processor - Save Points to the Nearest Hundredth
When assigning points to a Subtotal in an Assessment Processor, the logic rounds point values to the nearest tenth (ie: if a point value of 3.75 is assigned, the system rounds the value up to 3.8 when the screen is saved).
There are 2 HUD CoCs in our implementation that are creating new Coordinated Entry Assessments, both of which are assigning a percentage of points based on clients' responses to the assessment questions. This results in point values that need to be rounded to the nearest hundredth.
Without the ability to assign point values to the nearest hundredth, our implementation will need to rely on calculations in Looker to assign the point values requested by these CoCs. This will put an additional burden on already complex Coordinated Entry reports in Looker.
Please update the logic so that point values rounded to the nearest hundredth can be assigned in an Assessment Processor.
-
Jennifer Allen commented
This. This is the piece every community should be paying attention to. Without the ability to assign point values to the nearest hundredth, our implementation will need to rely on calculations in Looker to assign the point values requested by these CoCs. This will put an additional burden on already complex Coordinated Entry reports in Looker.
-
Meghan Morrow commented
This this critical for communities and their CE process.