add toolCount to ServiceAssignment model and settings page. #187
Comments
DaveLuhman
added a commit
that referenced
this issue
May 18, 2024
Subject: Enhance Service Assignment with Tool Count Added 'toolCount' field to ServiceAssignment model for better resource tracking, enforcing a minimum value of 0 to ensure data integrity. Updated the enum values within the ServiceAssignment Schema to more accurately reflect the types of jobsites, changing 'Contract Job' and 'Service Job' to 'Contract Jobsite' and 'Service Jobsite,' respectively. This change clarifies the nature of the assignments in the system. Service assignment fetch operation is now more performance-efficient by using `.lean()` with the query to speed up data retrieval, beneficial for large datasets. Furthermore, the 'toolCount' field is now displayed in the service assignments settings view, with a visual emphasis on counts greater than zero, improving the user interface for site administrators by allowing quick identification of resource allocations per assignment. This integration offers a detailed insight into the resource distribution across different service assignments, facilitating better planning and resource management. Resolves: add toolCount to ServiceAssignment model and settings page. #187
Merged
Merged
DaveLuhman
added a commit
that referenced
this issue
May 18, 2024
Subject: Enhance Service Assignment with Tool Count Added 'toolCount' field to ServiceAssignment model for better resource tracking, enforcing a minimum value of 0 to ensure data integrity. Updated the enum values within the ServiceAssignment Schema to more accurately reflect the types of jobsites, changing 'Contract Job' and 'Service Job' to 'Contract Jobsite' and 'Service Jobsite,' respectively. This change clarifies the nature of the assignments in the system. Service assignment fetch operation is now more performance-efficient by using `.lean()` with the query to speed up data retrieval, beneficial for large datasets. Furthermore, the 'toolCount' field is now displayed in the service assignments settings view, with a visual emphasis on counts greater than zero, improving the user interface for site administrators by allowing quick identification of resource allocations per assignment. This integration offers a detailed insight into the resource distribution across different service assignments, facilitating better planning and resource management. Resolves: add toolCount to ServiceAssignment model and settings page. #187
DaveLuhman
added a commit
that referenced
this issue
May 18, 2024
* toolCountChanges Subject: Enhance Service Assignment with Tool Count Added 'toolCount' field to ServiceAssignment model for better resource tracking, enforcing a minimum value of 0 to ensure data integrity. Updated the enum values within the ServiceAssignment Schema to more accurately reflect the types of jobsites, changing 'Contract Job' and 'Service Job' to 'Contract Jobsite' and 'Service Jobsite,' respectively. This change clarifies the nature of the assignments in the system. Service assignment fetch operation is now more performance-efficient by using `.lean()` with the query to speed up data retrieval, beneficial for large datasets. Furthermore, the 'toolCount' field is now displayed in the service assignments settings view, with a visual emphasis on counts greater than zero, improving the user interface for site administrators by allowing quick identification of resource allocations per assignment. This integration offers a detailed insight into the resource distribution across different service assignments, facilitating better planning and resource management. Resolves: add toolCount to ServiceAssignment model and settings page. #187 * missed local env var
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem:
Service assignments can be moved from active to inactive without having cleared all tools from the job. With the job marked as inactive, users won't know to go search under inactive jobsites to find the missing tools.
Solution:
added toolCount property to ServiceAssignment model, then scriptedly calculate the total number of tools for each SA once. This will run at the end of the tool import job so we start with good numbers, but will have to be done manually for any existing DB to get it up to snuff.
The text was updated successfully, but these errors were encountered: