Closed scaspers closed 6 years ago
@scaspers @YoMurphy this is what I have so far for you.
All remaining items take more work that isn't done yet.
Also, providing point 18 requires architectural change since the REST interface will have to provide some sort of mechanism for either turning on/off the filtering unanswered checklist items, or the client will have to get everything and I'll have to make CA-Portal facing customers filter.
Input on the SA view so far: ( I'll edit this as more comments come in )
All are doable. Still waiting for the dust to settle before jumping in to make sure we don't get competing requests.
For the Customer waiting and inspection complete flags: WAITING: assignment_ind Insp Complete: notifications_active
Use also in DI #102
I placed the unanswered items at the top for now because I made the DI implementation default to 0 for Unknown in my enumeration. I can reorder them to the bottom if desired (especially for those who want to check in periodically during inspection before its complete), but it will take additional work to make sure no breaking changes will occur because of it.
Also, I'm letting service writers "dog-food" the idea of only allowing expansion icons when there is something inside worth looking at. It would be only a few minutes of change to bring that over to the priority tab on the customer facing version.
Verified point 18 against current DI2 server with SA-portal and CA-portal local clients.
SA-Portal will hoist the "Unknown" state to the top, whereas this is omitted in CA-Portal. This behavior is true for both grouped and the flat list.
This is the info we would want on this report.
orderIDclientID, clientNamevehicleYear, vehicleMake, vehicleModel, vehicleLicensevehicleIDvehicleOdometervehicleEngine and vehicleTransmissionvehicleOptions