Skip to main content
Repair360 Back Office 4.2.5

What’s New in Repair360 Back Office version 4.2.5

A
Written by Allie Ray
Updated over a week ago

Parts ordering enhancements

We have added a new ‘Parts Management’ setting called ‘Parts Auto Ordering on Approval’ that defines if parts must be ordered from parts providers automatically once the parts are approved.

When users approve parts (and the new setting is ON) or when users click the ‘Order’ button in the shopping cart (and the new setting is either ON or OFF), they need to confirm ordering.

We have also made the following changes:

  • The ‘Close’ button has been renamed to ‘Save and Close’

  • The ‘Go To Approval’ button has been renamed to ‘Approve’ and moved to the bottom

  • The ‘Order’ button is disabled if none of the services is mapped and approved.

New payment methods for invoice payments

We have added the following payment methods to the ‘Payment for Invoice#’ view:

  • Credit Card (w/o processing) means that the payment is made by a credit card but the actual credit card processing occurs outside the system, users can also enter the customer’s name on card, confirmation number, and authorization code.

  • Side Note means that the payment is applied to the customer’s loan, users can also enter a loan number for reference.

Preventing duplicate service contracts

Now users cannot create multiple service contracts with the same number so when they create or edit a service contract and enter a number that already exists in the system, they see the appropriate warning message and cannot proceed until they change the service contract number.

Service request audit log enhancements

We have made the following changes to the service request ‘Audit Log’ view:

  • The ‘Date’ column shows the date and time of the Back Office application time zone

  • The ‘User’ column shows the name of the Back Office user, mobile app user, or that the change was made automatically (i.e. by the “system user”, workflow, etc.)

  • The ‘Notes’ column shows the following changes:

    • Adding and deleting services

    • Editing service price, quantity, notes

    • Accepting and rejecting service requests

    • Actions made by the mobile app user

Did this answer your question?