October sees a much shorter release cycle than normal, partly because September’s was late in the month and we are trying to get ahead. This also means that the release will better sync with our monthly newsletter.
We have now completely finished the new engineer messaging capability – this enables the back office team to send out messages to individuals or groups of engineers, and to track who has read the messages. See Chris’s video announcement for a flavour of what it does, and let us know if you’d like us to enable this for you for free.
We’ve turned on the new layout themes for a few contractors in their test system to play with and the feedback is very positive, if you want to see it in action then just get in touch and Chris or Tim can turn it on in a couple of mouse clicks. Carrying on the concept we’ve revisited the supplier invoice entry screen to see if we can make it flow better and allow for easier adding of extra lines. This started off as a customer request to exactly match their legacy accounts system’s invoice entry layout, but has grown into a new way that we think will make the screen easier for everyone to use. We can turn this on in your test system too if you’d like to see it and have a play with it.
New Features
- New supplier / sub-contractor invoice entry screen with popup line entry
- Find Job Report now has the same bulk change functionality as the Job Requiring Action Report
- Finished the backoffice screens for managing the sending of messages from the back office to mobile app
- When there is only one price for a part, we now update the part price when the supplier price changes
- Phone calls made from the mobile app will be logged in the job history to be displayed in the back office system
- The Job Cost Report now shows the order number when broken down by job number
Changes For A Single Contractor
- Added completion date to invoice layout
- New timesheet layout including weekend overtime calculations, automatic deductions for travel and lunch, capped holidays, and a new summary section
- Fixed duplicate notes appearing on a timesheet and changed wrapping of long notes
Platform Improvements
- New page to show all automated tasks (cronjobs) on the live systems to allow implementation/support team to preempt automated tasks
- Fixed some small formatting, layout problems, and icons in the new back office UI
- Added some additional logging to the mobile app to track engineers who are aborting the sync connections
- Improved the logging of system option changes so we can better track support team changes and ignore developer test changes
- Removed the default ability for the Epix support team to edit system users to prevent social engineering attacks and clarify the responsibilities of contractors to maintain the permissions and access limits of their own staff
- Added a system option to control the management of users and allow full control of users by Epix during the implementation phase until training is complete and responsibility can be effectively passed to the contractor. This includes warning on internal mirrors to highlight systems with the ability to edit users turned on, and logging of changes to the system option
Bug Fixes
- Copied original attachment filename to the cloned attachments so downloads work better
- Fixed variable name passed from the bulk change job screen for a single job
- Asset livesearch is not affected by the hidden site livesearch when cw_show_address is off
- Fixed a bug where you couldn’t edit rates on a sales line if the line was delivered which was supposed to only affect invoiced lines
- Fixed the cancel overlay button not working in system user edit screen
- Prevent race condition when passing purchase invoices that seemingly allowed multiple users to pass the same invoice multiple times leaving the invoice in an inconsistent state relative to export batches and reporting
- Fixed multiple problems on both ACR and Building Maintenance flavours of MARKUS when clearing asset specific charge addresses
- Ensured all interfaces receiving variation approval use the correct VAR_REJECTED status label to define status progression from a rejected update
