6/16/25 - Schedule Map Pin Updates, Filter Portal Requests, Franchise Owner, and Fixes

The items mentioned below will be available on or after June 16, 2025. To see these new features, please perform a hard refresh in your browser and update your mobile app to the latest version (9.4.47). Here's how to Get the Latest Version of ServiceCore.


Schedule Map Pin Updates

We have updated the Schedule Map pins with a new white border. Also we've updated how pins look when selecting them with the lasso tool. You'll now see the map pins have a new blue border as they are selected. 

 

image (2).png

 


Filter Portal Requests by Division

For customers on the Pro Plan, you can now filter portal requests by division directly from the Portal Requests page. This update makes it easier to organize and review incoming requests across different parts of your business. 


Franchise Owner Role

We have added a new role for Franchise Owners. This new role will allow you to set a tailored set of permissions specific to this level of user. You can find and assign this new role under User Management Settings.


Inventory Table on Rental Details Page

We have added an Inventory Details table to the Rental Details page. You will no longer need to look into your jobs associated with a Rental to see what Products and Items are currently on site. This table will show a count of bulk units, the count of units of itemized products and the specific units that were selected upon delivery.  Just like the Inventory table on the Job Details page, if a serial number is not selected then "Unknown Serial Number" will display in the table. 


Clear unit location when completing a Pick Up Job

We have updated pickup jobs to remove the GPS coordinates from an itemized unit when that unit is selected on a pick up job. This will prevent the unit from showing up on a map at the previous job site after being picked up.


Fixes 

Dashboard Income Chart Label: The "Estimates" section on the Income pie chart was previously mislabeled as "Invoices". This has now been corrected.

Was this article helpful?
0 out of 0 found this helpful