New Mobile Application
Mobile ‘MVP' Release
In the Summer 18' release, we’re excited to introduce our new Android and iOS mobile applications. This initial release is just the first in a series of highly-anticipated updates that we will be releasing in the coming months.
Our new mobile will deliver an improved user experience as well as unlocking many new features and benefits for both mobile and back office teams in the future.
More details on the current, upcoming and future functionality we are planning to bring to this application will be presented at summer release webinar.
Mobile ‘Early Adopter Programme’
Access to the new mobile applications will be managed on an ‘Opt-in’ basis, giving you the control to move to use the new apps in a timeframe that works for you and your organisation. We will continue to support all users of our existing mobile application.
For partners who are keen to explore migrating to the new mobile app, we have created an Early Adopters Programme (EAP) to support you in this journey. A number of partners have already expressed interest and more information will be available following the release Webinar, including details of how to sign up.
Our new mobile application gives us a fantastic platform on which to bring you some new and exciting feature capabilities. In this release, we are delivering the first version of our new mobile location tracking feature.
This will allow you to view the resource locations on the 'Route View' page within the desktop application. By visualising the location of your mobile workers in real time on a map it will allow your desktop users to track the resources against their planned route, help to improve the productivity, utilisation and safety of your remote teams.
This image is showing the current resource location on the 'Route View' page within the desktop application using data captured from the new mobile application.
Core Application Enhancements
Coordinate Improvements (Enterprise and Lite)
Our coordinate feature has been available since the Autumn 2017 release. We now support the use of location geo-coordinates against both 'sites' (customer locations) and 'resources' (operative home locations).
More precise location information will support the effectiveness of our street-level routing feature, allow for more accurate drive time calculations and support the display of locations on map views; ensuring your operatives get to exactly the right place, first time, every time.
If you haven't activated our coordinate feature on your application but you're interested in the benefits it can deliver please contact our support team who can start the enablement process.
Create Job API
Within this release, we have improved our Create Job API to include site coordinates. After the upgrade, any jobs created using our API will use the site coordinates if they are available and assign it to the job. This will allow the map view to appear on the job details page and display on the Route View page to see what appointments have been scheduled to your resources each day.
The create job process within the application already used this behaviour so this change will only be applied to the Jobs created via the API.
Modifying address fields against a site will update the address for linked jobs if the job status is within a 'Pending' or 'In Progress' status group (Blue and orange coloured status). This functionality has been expanded to include our new coordinate feature. If you change the site coordinates using the supplied option it will update open jobs (Pending and In Progress) without the need to change one of the address fields at the same time. This will allow the map to update on the job detail pages to reflect the coordinate change on the site.
API for Appointment Scheduling (Integration Optional)
Part of our integration offering is APIs to support appointment scheduling. One of our API returns resource availability from the pooled scheduler. A second API is used to schedule the appointment. Both APIs have been enhanced to provide greater flexibility over primary and secondary resource services and working areas.
This API will retrieve all available slots for a given period using a supplied job reference and a start date. This will follow the same logic as the pooled appointment screen as it will return available day division slots for resources within the team.
A new option has been created to allow users to specify if you would like to retrieve availability using resource primary or secondary services and resource working zone can be set to primary, secondary or override and use any similar to the pooled scheduler.
This API has been expanded to have two new optional fields;
Zone Criteria - This can be set to Primary, Secondary or Any. Primary and secondary working areas will be set against the resource account to determine what area the resource will cover. The 'Any' option will allow the working area check to be ignored, similar to the 'Unrestricted' option within the scheduler.
Allow Secondary - By default the API will only include resource primary services but you can override this using this option to include resource secondary services.
Oneserve Analytics (Optional)
If you are using our optional self-service analytic tool, you will have access to a new data source called 'Resource Working/Non-Working Time'. This section will allow users to report on time events applied to the Resource, Team and Calendar levels. The benefit of using this new source will be to create timesheets to see what hours your resources are working and review resource availability for the weeks coming as it can highlight who has time off.
For more details on how to use the 'Resource Working/Non-Working time' please click here
If you are not using our self-service analytics but you would like to know more information about the benefits of what our analytic tool can offer you please contact our support desk or your account manager.
An example of the data has been shown below. This report is using working/non-working time for all resources within a team for the next month. You can filter by Team, Resource Name, Date Range and Allocated Time Types. This would allow you to create a view of your resource working hours in the past or future, This could be useful for reviewing overtime shifts patterns or approving holiday requests by checking your team's availability first.
Small enhancement and fixes
Application or Service Function
Description of Enhancement or Bug Fix
Changes to Operational Practices
|Pooled Scheduler||The notification tick box on the Pooled scheduler will be selected if notifications have been configured against the work type. An issue was occuring if you unticked the notification box and then used the scheduler refresh button because the box would return to the default behaviour which could be ticked. This has been improved to prevent the refresh action changing the notification setting.||Depending on your configuration on your work types you may have appointments send notifications once they have been selected. After the upgrade your users will be able to schedule appointments using the pooled scheduler and the notifications tick box will only change if the user makes amendments manually.||
|Against job activities you can have the option to create a Purchase Order with the activity details. This process would use the activity code, description and notes to create the purchase order but this could exceed the character length allowed in the purchase order. We have increased this limit to prevent the restrictions on particular activities being used on purchase orders.||
Previously the purchase order creation would be cancelled if the activity details exceeded the character length, with the increase of the character limit users should be able to use any activities on a purchase order. More information about activity purchase orders can be found here
Enterprise - (Optional)
|Activity Purchase Order API||Part of our integration portfolio we have an activity purchase order API. The job description field has been updated so it will use the description from the latest job version instead of the original job description. This will allow users to update the job details and the most recent details will be used within the API calls.||This will only affect you if you are using our activityOrder API. If you are interested in how this API will work please contact our support desk.||Enterprise|
After running the nightly optimiser, appointments could have displayed incorrect drive times on the scheduler which will be shown with a purple box around the appointment. This could have occurred if you are using our new coordinate and optimiser functionality. The scheduler calculates drive time using site coordinates if they are available, if not it will default to postcodes. The optimiser wasn't configured to handle coordinates in the same way, therefore, it could have caused a change to drivetimes by a couple of minutes. This issue has been resolved so the optimiser will behave in the same way as the scheduler when it calculates the appointment drive time.
|After this upgrade, the optimiser will continue to run nightly as it did previously. It will now reschedule appointments using coordinates where they are present. When you open the scheduler the drive time will be calculated in the same way therefore you will not see insufficient drive times for appointments that have been moved by the optimiser.||Enterprise|
|Nightly Optimiser||The optimiser has been improved to handle Working/ Non-Working time similar to the scheduler. The optimiser will apply working/non-working time from the calendar level first, any additional time at the team level will override the calendar and time from the resource will override the team and calendar if they overlap. This behaviour has already been used by the scheduler so the optimiser will now react in the same way. For more information about how working and non-working time will be used please view this Guide||This improvement will prevent the optimiser alerts reporting on overcommitted days when resources have availability but the team or calendar have non-working time. Users don't need to make any changes to the way they are recording working/ non-working time because the optimiser will handle overlaps in the same way as the scheduler. If you are able to schedule appointments to a resource on the scheduler the optimiser will also be able to reschedule the appointment.||Enterprise|