1/15/2025 v2025.01

New Release Notes every three weeks!

	We are listening! Items with this label are a result of your suggestions in uInnovate. Please continue to share and support those ideas that help your business.
	Items with this label are features that may require adjustments to security or configuration and may have implications for your operations or current workflows. We recommend reading these and understanding the impact prior to updating.

Aging and Terms: At the beginning of 2024, we introduced a new ‘days’ field on the customer record. By using this field, a ‘Due Date’ could be calculated on the invoice format when using the Contract-Params-MC.SQL.rpt in laser contract formats. This ‘Due Date’ was calculated by adding the terms days to the closed date to get the due date. For example, if the terms days were 30 and the contract was closed on 1/1/2025, the due date would be 1/31/2025. We have now used that due date for aging in the accounts receivable dashboard. If the ‘Due Date’ box at the top left of this dashboard is checked, the contracts will reallocate themselves in the aging buckets based on the due date rather than the closed date. If you have the configuration turned on to ‘Set Billed Date,’ it will use the billed date plus the terms days to calculate this due date rather than the closed date. Please consult articles Elite v2024.18 Release Notes and Invoices (located in the 'Set Billed Date' section) to learn more about the Set Billed Date configuration.

Vertex Flex Fields: Two new flex fields have been added to the Vertex flex field setup. These fields are the API Link and Other ID fields from the customer record. As a reminder, flex fields can be used with either the Vertex Cloud or Vertex v2 integrations. It is an add-on feature, so please contact sales if you are interested. To learn more about Vertex flex fields, see our article Vertex Enhanced Flex Fields.

Job site/Venue Address Change: When a change is made to the address of a job site/venue, you will now be warned if the record is currently being used on a quote, reservation, or open contract and will reference the number of contracts it is used on. The warning is to notify users so that they can adjust the transactions if needed. The user can reference these in the transaction history attached to the job site/venue. For more information, please see the article Job Sites/Venue.

Job site/Venue Transaction History: We have added a transaction history grid to the job site/venue record. This will list any transaction the job site/venue is attached to and, as with other grids like it, has grouping and filtering options. For more information, please see the article Job Sites/Venue.

Logistics Tickets from Continued Contracts Updates: When created, logistics tickets on continued contracts referenced the parent contract for the entire billing cycle for a couple of things that did not make sense. For example, they would automatically be put on the truck that delivered the original contract, and they would flag the user based on the delivery dates of the original contract. As neither of those things is particularly useful on a logistics ticket that has been created months down the road, we have discontinued those behaviors.

Allowed Payment Methods: Depending on a company’s policies, not all payment methods may be acceptable. In an effort to prevent errors, you can now set the payment methods allowed both on the contract payment screen and through account payments. These configurations are located in the ‘System’ section of browser configuration. Unchecking the box next to the payment method will prevent it from being seen in the payment process. These apply company-wide. For more information, please see the article Account Payments (located under Payment Method Security).

Customer Look-Up Screens:  The customer look-up screens have been enhanced to improve look-up speeds.

Various Bug Fixes:  We implemented various changes to improve accuracy and user experience.

Mobile

These are updates for Elite users utilizing the POR One app.

Routes Refresh - Routes have been enhanced to refresh automatically to keep data current for your Drivers. When Dispatch makes a change or addition to a Route or a Stop, it will be updated on POR One whenever a driver views the Routes list page, and while they are viewing it, it will be updated at regular intervals. This will keep up-to-date information on their device while they are out on the run. To learn more about POR One Routes, see the article POR One | Deliveries & Pickups with Routes.

Stops (Routes) Workflow - The countdown timer for the Stop updates, like On The Way / Arrived / Stop Complete, has been removed. This will allow Drivers to go through their workflow more quickly with fewer inputs required. To learn more about POR One Routes, see the article POR One | Deliveries & Pickups with Routes.

Fix: Inventory Details not showing all Work Orders - There was an issue where Inventory Details was not showing all Work Orders associated with the Inventory Item that has now been resolved.

Fix: Signature Completion - Signature completion on Tasks was not validating properly and did not appear to be completed when it actually was completed. This validation is now working as expected when the signature form is filled out. 

eCommerce

These are updates that pertain to users who use the consumer portal and storefront platforms.

Basic/Advanced Users:

We added a configuration to the Admin Panel where you can set disallowing payments on quotes.

We added a field in the Admin Panel where you can provide a custom URL for the Consumer Portal.  The main goal of this is to improve the email deliverability of QuikLinks by removing the myportal.rent portion of the URL. Instead of the only option being 1234.myportal.rent or rentalstorename.myportal.rent you can now have the URL be portal.yourrentalstorename.com or myorders.yourrentalstorename.com.  

Advanced Users:

We made several enhancements to the MyRentals page-

• Separated the display of the product name and item number for ease of reading the data

• Added a status column for Out, Reserved, or Off-Rent

• Now hide action buttons for items that are Off-Rent

• Contract links go to the Contract Detail page

• Item links open the Product Detail page

We now show users an on-screen dialog when they complete an action so they know their request was enacted.

Memory Lane Monday

This is a fun corner where we republish release notes from previous sprints you may have forgotten about.

V2023.07

Default Assigned To Settings:  Two new settings have been added to the transaction area of browser configuration for setting the assigned to on a contract.  A user must have security enabled to view/edit these settings.  ‘Force Assigned To’ will force the user to select an assigned to when they hit the ‘ok’ button to save the contract if the assigned to field is blank.  This will not occur if it has been populated by the customer, jobsite, or manually.  ‘Auto Assigned To’ will automatically populate the user modifying/creating the contract as the assigned to. This will not occur if it has been populated by the customer, jobsite, or manually. Currently, this will only apply to quotes, normal contracts, and reservations.

  Delivery By Mile:  Traditionally, the delivery by mile charge has been calculated from the store in which the contract is written. However, this would be inaccurate if store 1 happened to be writing a contract for store 2.  Now, this distance will be calculated from the contract’s store to the delivery address.