11/28/2022 v2022.16

 

 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.

 We recommend reading these and understanding the impact prior to updating. These features may require adjustments to security or configuration and may have implications for your operations or current workflows.

Operator record: Some of y'all may have been getting confused when updating Stores or Security Groups for an Operator. Like maybe your changes were not getting saved. The fact is, changes made to those 'related objects' are getting saved as you change them. But it still seemed odd because that Submit button was sitting there - grayed out. So now when you are in the 'modify' state there will be a 'Done' button displayed when viewing the related objects. You can make changes and select that Done button. This will push you back over to the Operator record where you can then select the Submit button which sets the record back to a 'read only' state. It's just a better flow.

 Customer record - browser: One of our beloved Quality Assurance team members kept wanting to add a defect for the Customer record because the 'expire date' fields did not do anything when the date was today or earlier. We had to keep saying that it's not a defect if there is no code to actually do that. It was, however, a great uInnovate idea. See, we even implement uInnovate ideas that come from our fellow 'pointers'. All of the 'expire dates' will now show a yellow warning message when in a 'read only' state and the date is today or earlier. And, because we like to have fun, we are also showing a Happy Birthday message if the customer's birthdate is today.

Payment Import: We updated some logic in this process recently that made old Mappings' no longer work as expected. But they were still sitting there in the list of Mappings. We have added an 'Inactive' option to permanently hide them. That's right - once you set to Inactive that Mapping will no longer be available. If you have some 'old' mappings in your list, now you can hide them.

 Public API - Alias and Barcode: This work was done to support a customer that required to be able to search against QR codes from POR One where there were codes in both Barcode and Alias fields. We were going to do it eventually - this just moved us along a little sooner.

Special Rate Label: Within the contract, when the user right clicks and selects ‘Set Special Rate’, a label has been added to show what level of special rate is being used (If any). It will read ‘Special Rate Type: Manual’, etc. This is useful for understanding what has been set on the contract to derive the rate before any changes are made.

Image Resizing: Previously, when images were copied into Point of Rental (on item files for example), the images were resized. This was great for disk space and uniformity of images, but not so great for image resolution on websites. Moving forward, any new images copied into the program will retain their original size and resolution. If an image is over 4MB (the max size for any single picture uploaded to the web through MakeWeb), the user will be notified, but allowed to proceed.

 Default Payment Type for Cash Customers: By popular demand, we are now giving our users the ability to set a default payment type for cash customers. This setting is found in the System container of the browser configurations and can be set on a per store basis for cash, check, or credit card. Once defined, this payment type will automatically be selected in the payment screen for any cash customer contract with no previous payments. If there has been a previous payment, it will default to the payment method of the previous payment as it always has. Not only will this streamline taking payments, but will help prevent mistakes (from example, for those locations that only take credit cards).

API Endpoints: For those users connecting to our API endpoints, CreatedDateTime and UpdatedDateTime have been added for Transactions and Item Files. They will display when the record was created and when it was last modified, respectively.

Subrental Contract Links: In the past, when a contract with a linked subrental was continuation billed, we prematurely set the contract link in the next contract with the corresponding next contract in the subrental continuation cycle in anticipation of that being the next step. However, we are now only updating the contract link when the subrental is actually continued. Otherwise, the previous subrental contract in the cycle will be left linked. We did this to make it easier to track oversights and to eliminate confusion that could be caused by contract numbers that do not actually exist yet.

Quantity Overlap Store Selector from an Item: The quantity overlap screen (Item Record>Analysis>Quantity Compare Analysis>Quantity Compare) from the item record has been enhanced with a store selector. This is useful so that data from each store can easily be analyzed instead of on the company as a whole.

eSign Error Messaging: We have enhanced some of the messaging around certain ensign errors to indicate whether the issue lies with the PDF or the eSign server itself. This will help get those cases resolved in an efficient manner.

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

 Discount Codes: Users now have the ability to mark discount codes inactive. This will remove the discount code on customers and their future contracts, but leave it on already existing contracts.

 Credit POs: Invoice information from the original purchase order will no longer be carried over to any credit po created off of it.

 Dynamic Sales Items: Users can now utilize the item record type of Rental-Dynamic Quantity for sales items. Simply add sales items only to the package items, and the item will calculate the quantity of the package based on the sales item quantities.