Latest Release

Mandatory Event on Orders and Event ID on Events (R2-24474/ R2-24475)

• Event on Orders and Event ID on Events can be set as mandatory in Employee Defaults.

• Applicable for Rental and Sale Orders only.

• Enforces user to link the orders to events and input the Event ID manually on creation.

Driver Profile create/edit feature is available on R2Web (R2-24163)

• The Driver Profile page is rebuilt using Java to improve supportability and maintainability.

• This update removes the dependency on the legacy VB implementation.

• The Driver Profile create/edit feature is now available in R2 Web.

Assets List API: Search assets by Additional Asset ID (R2- 24417)

• You can now search assets using Additional Asset IDs.

• Supports both single-value (=) and multi-value (IN) searches.

• Discovers assets either by primary or additional Asset IDs.

Introducing Close Order and Re-open Order APIs (R2-24407/ R2-24406)

• Close Order API: Marks specified order and related suborders as ‘Done and Invoiced’ without generating any invoices.

• Re-open Order API: Re-opens specified ‘Done and Invoiced’ order and related sub orders.

POST and PUT Order API - Event ID mandatory based on employee defaults (R2-24568)

• The Event ID attribute is now required in payload, if set as mandatory in Employee Defaults.

• Enforces user to link the orders to events.

POST and PUT Event API - Event ID mandatory based on employee defaults (R2-24570)

• The Event ID attribute is now required in payload, if set as mandatory in Employee Defaults.

EquipFinder – Added Event and Project fields for Quote and Reservation (R2-24569)

• Event and Project fields are now available for Order creation.

• These fields are required if set as mandatory in Employee Defaults.

PackNShip: Bulk Asset Update (R2-24199)

• Enables Location, Bin, Shelf, and Asset ID update along with RFID scan.

• Simplifies warehouse operations by managing asset updates in one mobile interface.

PackNShip: Scan by Additional Asset ID in Ship and Batch Return (R2-24415/ R2-24413/ R2-24414/ SR-29913)

• Allows to scan by additional asset IDs.

• Ensure duplicates are eliminated when both primary and additional asset IDs are scanned.

Search Screen Column Personalization (R2-24203)

• Allows you to customize the columns of your preference.

• Save column order, width, and visibility.

R2: The Probability value set on an order was not displayed correctly in reports generated using REP_EpicOrderHeaderView. A Probability of 70% appeared as 7.00 in R2 Hero and in custom reports using this dataset, even though it displayed correctly when using REP_OrderHeaderView. This caused inconsistent reporting results for customers relying on Epic-based datasets. (SR-29940)
Fix: The system now displays the Probability value exactly as defined on the order in both REP_OrderHeaderView and REP_EpicOrderHeaderView. Reports created in R2 and R2 Hero now show the correct Percentage value consistently.

R2 Web: When multiple item lines were selected in an order, performing a right-click in certain browsers (Safari on macOS or Windows, and intermittently on Edge) caused the system to lose the multi-selection. Instead of retaining all highlighted lines, the system cleared the selection and kept only the single line under the cursor. As a result, right-click actions applied only to one line even when the intention was to act on all selected lines. This issue occurred inconsistently and was more noticeable when using mouse. (SR-27171)
Fix: The system now preserves multi-line selection when users right-click on selected rows. Right-click drag has been disabled across all grids to prevent unintended drag detection, while normal left-click drag continues to function as before. Right-click menus behave exactly as earlier, and switching the OS primary mouse button (for left-handed users) continues to work without affecting multi-selection behavior.

R2: When you perform a Batch Return at the planned return site, the system temporarily showed negative availability in the shipping site. The issue occurred because the system updated Move-In and Move-Out quantities only after the Batch Return screen closed, which caused inconsistent availability values during the return process. (SR-28608)
Fix: The system now updates Move-In and Move-Out quantities immediately after the asset is scanned in the Return or Batch Return screen. This ensures both the shipping and returning sites show correct availability during the return process. The OUT quantity continues to update only when the return screen closes, preserving expected behavior for order line status updates.

R2: In the Equipment Usage View (EUV) and Asset Usage View (AUV), the system did not display the Scheduled Service Work Order (SWO) bar when the asset was in Out status on a rental order. As a result, assets with upcoming scheduled service work were missing the corresponding Scheduled bar in the timeline. (SR-29531)
Fix: The system now displays the Scheduled SWO bar in both EUV and AUV even when the asset is in Out status. The SWO bar is shown from the Scheduled Date/Start Date through the Due Date/End Date for both On-site and In-house SWOs. Availability values now remain consistent with R2 availability, and the updated logic prevents double booking. Additionally, the SWO tooltip now includes the SWO Location, allowing users to easily identify whether the work is On-site or In-house.

R2: When you attempted to modify the charge duration for a returned line, the system blocked the update and displayed an error stating that some invoices were posted and the new charge date could not be earlier than the last posted invoice date. This happened because the system validated the change against the maximum posted invoice date across all invoices, not the posted invoice date for the specific line being modified. (SR-29548)
Fix: We updated the validation logic, so the system now checks only the posted invoice dates associated with the specific contract line. The system retrieves the line-level posted date and applies it during charge-date modification. You can now update the charge duration for a returned line as long as the new date complies with that line’s own invoice history.

R2: When you duplicate a sales order, the system did not retain the unit price from the source order. Instead, it recalculated the price based on the item’s defined pricing, causing the duplicated order to show the Rate Card (RC) price instead of the modified unit price saved in the original order. (SR-29522)
Fix: We updated the duplication logic, so the system now copies the unit price exactly as it appears in the source order. The system no longer recalculates pricing or overwrites the unit price during duplication. Rate Card Price and Minimum Price continue to refresh as needed, but the unit price always reflects the committed value from the original order line.

R2: When you attempted to merge two customers, the system displayed an error and stopped the merge process whenever the source customer had linked CRM Opportunities or Customer Price Freeze setup. (SR-29723)
Fix: We updated the merge logic to correctly handle all dependent references for the source customer. The system now updates company and contact references in all related entities, including CRM Opportunities and Customer Price Freeze setup during the merge. The merge now completes successfully unless both customers have locking conditions that intentionally block the operation.

R2: When the Item Price Group was overridden at the Order Header level, the system failed to re-price item lines if a Disclaimer line was present on the order. In such cases, unit prices remained zero or did not update as expected, preventing correct pricing from being applied based on the selected Price Group. (SR-29721)
Fix: The system now correctly recalculates item prices when the Item Price Group is changed, even when a Disclaimer line is included on the order. Price updates are applied with no errors, and repricing behaves consistently for both scenarios — with and without a Disclaimer.

R2: When you printed an invoice created for a reservation with five-week charge duration, CID#1327 displayed the duration as “5w0d” instead of the expected “5w” in invoice prints generated using 159500UI. (SR-29857)
Fix: We updated the duration calculation logic to prevent the system from printing unnecessary day values for invoices. The CID#1327 now prints “5w” when the duration is exactly five weeks, and no trailing “0d” appears. This fix applies only to Length Of Contract-All (LOC-All) Pay Type invoices and other types.

R2: When a rental order line was linked to a purchase order, the Order Site Total Cost and Total Cost did not always reflect accurate values when multiple currencies were involved. In cases where the Order and PO currencies differed, the system sometimes used the Order’s conversion rate instead of the Purchase Order’s rate, resulting in mismatched cost calculations between the two documents. (SR-27823)
Fix: The system now correctly derives the Transaction, Site, and Base Cost values for PO-linked order lines using the Purchase Order’s currency conversion rate. This ensures that Order and PO costs remain consistent across all multi-currency scenarios, including when site or transaction currencies differ.

R2: When a labor line was permanently deleted from an R2 Order, the system triggered the deletion-notification email but the details section in the email was blank. The deleted line information — including labor details and action was not appearing in the template, making the notification unusable in case of deletions. Deletions performed from the R2 Labor module were already working correctly and continued to populate email details as expected. (SR-28865)
Fix: The system now correctly supplies all deleted labor line details for R2 Order deletions so that they populate properly in the email notification. To display the deleted line’s description, customers must ensure their email template includes the hashtag for Previous Description, which will now receive the appropriate value when a line is permanently deleted.

R2: The system did not prompt you to cancel the linked Purchase Order (PO) line when you deleted a Reserved equipment line that contained a PO reference. Because the prompt did not appear, the PO link remained active, and the line’s cost continued to show the original PO amount (for example, 500) even though the rental order line had been deleted. This behavior created inconsistent financial data and left orphaned PO references. (SR-29077)
Fix: The system now prompts you to confirm PO cancellation whenever you delete a Reserved line that has an associated PO link. When you confirm, the system cancels or delinks the PO line as expected and recalculates the rental-order cost to zero. This update aligns the workflow with other deletion actions—such as “Not Available” or deleting a P-Assign line—and ensures PO links and costs remain accurate whenever a Reserved line is removed.

R2: The system failed to correctly copy and paste packages that included nested subpackages when any child item inside the package was inactive. When you pasted such a package, the inactive child item caused the package index to break. All packages following the inactive item were pasted as standalone items, and their children appeared outside the intended hierarchy. This resulted in misplaced child packages and an incorrect line structure during package copy/paste operations. (SR-29692)
Fix: The system now correctly skips inactive child items during package copy and paste without disrupting the nested package index. The updated logic handles failures cleanly by displaying an error message that lists all inactive or failed items while preserving the correct hierarchy for all other child packages and items. These improvements ensure accurate copy/paste behavior in both rental orders and transfer orders, with all valid packages and children retaining their proper structure even when some items are inactive.

R2: When viewing the details of a Master Bill Invoice from the Master Bill Invoice Search screen—especially those linked to many Proforma Invoices—the Master Bill Details grid previously took a long time to refresh and display data. (SR-29380)
Fix: We have optimized the grid’s performance, and it now loads significantly faster.

R2 Labor: When a crew member responded to a confirmation request (Accept/Decline), the planner continued to receive email notifications even if the request had already become invalid — for example, after changes in event work times (EWT) that caused previously sent requests to expire. This resulted in planners receiving unnecessary or misleading emails for jobs that were no longer actionable. (SR-30066, SR-29480)
Fix: The system now validates each job request before processing a crew response. If all requested jobs are invalid, no email is sent to the planner. If a request includes both valid and invalid jobs, the system ignores the invalid ones while continuing to process valid responses and notifying the planner only for those valid jobs.

R2 Labor: When you changed the start and end times for a booking line in the Whiteboard, the system did not repopulate the Duration field after tabbing out of the time fields. (SR-28865)
Fix: We corrected the behavior so the system now populates the Duration field correctly whenever you modify start or end times in the Whiteboard.

R2: The Thunderbolt icon (Booking Line Details from Labor Planning) was disabled for ‘Done & Invoiced’ orders, and in Read-Only mode of orders, preventing users from viewing booking line details on such orders. (R2-24418)
Fix: Updated the order screen behavior to keep the Thunderbolt icon enabled for all non-editable states, including ‘Done & Invoiced’, and Read-Only (in-process or being edited by another user) so that one can always view Booking Line Details. All transactional actions inside the Booking Line Details screen (editing, tagging, right-click menus, save operations, etc.) remain disabled in these scenarios.

PackNShip: Scanning an Additional Asset ID did not display the item description in the Scanned List, showing “Item not found” even though the asset was valid. (R2-24413)
Fix: Enhanced support in the PackNShip app to correctly recognize assets scanned using either the Primary Asset ID or the Additional Asset ID. The system now retrieves and displays the correct item description in the Scanned List across Ship, Batch Return, and Asset Update screens. This ensures consistent identification of assets and resolves scenarios where additional asset IDs previously returned no description..

PackNShip: Duplicate scans were not correctly detected in the Scanned Items list, when scanning both Primary and Additional Asset IDs of the same asset or same Additional Asset ID multiple times, causing the Scanned List to show duplicates instead of consolidating them. (R2-24414/SR-29913)
Fix: Updated the PackNShip app to properly identify assets scanned using either Primary or Additional Asset ID. When both IDs refer to the same asset, the system now removes duplicates automatically when the user opens the Scanned Items list. This ensures correct scan counts and prevents false duplicate detection messages. Behavior is consistently applied across Ship, Batch Return, and Asset Update screens. Know more..

PackNShip: “Item not found” entries were duplicated in the Scanned Items list, even when the same invalid item ID was scanned multiple times. (R2-24574)
Fix: Updated the PackNShip app to automatically remove duplicate “item not found” records when the Scanned Items list is opened. Once an ID is identified as invalid, subsequent scans of the same text no longer create additional entries. This ensures a clean and accurate list for both Batch Return and Ship workflows and aligns behavior with how valid serial/non-serial items are handled.

PackNShip / Ship API: The system did not allow shipping an item using its Additional Asset ID. When the item was attempted to ship using the Additional Asset ID returned “Item not found” message in both the Ship API and the PackNShip app. (R2-24415)
Fix: The shipping workflow is corrected now updates the order line as Shipped whether you provide the Primary Asset ID or an Additional Asset ID. Shipping now works reliably via both API and PackNShip for Primary and Additional Asset IDs across Rentals, Sales and Transfer Orders.

LaborMate: Attachments coming from R2-Labor were visible in the mobile app, but tapping any file did nothing — no preview opened and no action was triggered, preventing you from viewing PDFs, images, and other linked documents. (R2-24573)
Fix: The attachment-open workflow is now corrected. Attachments open reliably through the default native device apps.

R2: When creating a Service Work Order (SWO) from Return Order or other modules, the SWO’s billing and shipping addresses shared the address reference of the customer contact. As a result, updating the address on the SWO unintentionally updated the customer contact’s master address. (R2-24484)
Fix: The system now creates a separate copy of the contact address for every SWO. Any address changes made within an SWO now apply only to that SWO, without affecting customer contact or other orders. This ensures SWO-specific address integrity and prevents unintended updates.

R2: When generating event orders, there was a problem where the system sometimes stored extra address information in the background, even if no shipping address was actually provided. This could lead to confusion and incorrect links between orders and addresses. (R2-24487)
Fix: Now, the system only saves shipping address details if they are entered. Any old, unnecessary address links have also been cleaned up. Updating a shipping address for such an order now works as expected and does not affect other customer or contact information.

R2: When generating an E-pool Operations Order, the system was incorrectly sharing the Site Address and Intra-company Contact Address with the Ops Order. As a result, updating the billing or shipping address on the Ops Order unintentionally modified the Site A address or the intra-company contact’s master address. (R2-24486)
Fix: The system now clones both the Site Address and the Intra-company Contact Address when creating an E-pool Ops Order. Any updates made to billing or shipping addresses within the Ops Order apply only to that order and no longer affect the original site or intra-company records. This ensures clean separation between Ops Orders and master data.

R2: After a customer merge, the billing address for orders linked to the source customer-contact was overwritten with the target customer-contact’s billing address irrespective of whether they are Done or Open. Additionally, the updated orders and the contact master record ended up sharing the same address reference, so any changes to an order’s billing address were reflected on the contact master’s address as well. (R2-24488)
Fix: The customer-merge logic now clones and applies the merged customer’s billing address only to Open orders. Billing addresses for completed or invoiced orders remain unchanged. This ensures that updates to order addresses do not affect the contact master record, preserving data integrity across customer, contact, and order records after a merge.

R2: The Close Order function did not ignore the LR (Lost/Repair) invoice and hence did not mark it as Done or Invoiced though other required conditions are met. (R2-24496)
Fix: The Close Order function has been updated so LR invoices are not treated as system invoices. The system now correctly allows orders with LR invoices to be closed without restriction as long as other required conditions are met.

R2: Quote orders created with ‘Pay At’ as ‘Rent’ were changing to Reservation when reopened through Accounts > Search Orders > Re-open Order function. This caused incorrect order type conversion during Re-open Order workflow. (R2-24495)
Fix: The system now does not action on an order that is already in an open state. An appropriate error message is shown instead, ensuring that Quote orders remain as Quote and their type no longer changes unintentionally when actioned through Accounts > Search Orders > Re-open Order function.

R2 Labor: Timesheet export previously failed for orders containing a very large number of Estimated Work Time (EWT) records, such as those spanning multiple years. This issue prevented users from exporting timesheets for long-duration orders. (R2-24394)
Fix: The export process has been enhanced to support orders with extensive EWT records. Timesheet export now completes successfully, regardless of the number or duration of EWT entries.

CRM: The Value column filter in the Opportunity grid was not working. Entering a numeric filter (e.g., 1000) did not update the results, and the grid continued to display all records. (R2-24481)
Fix: The filtering logic for currency fields is corrected. The Value column now correctly applies all filter conditions—Equals, Not Equals, In Range, Before/After, and others—across Opportunity, Activity Manager, and Company entities.

EquipFinder: Mandatory Project validation was not triggered during Quote/Reservation creation. (R2-23506)
Fix: Updated the EquipFinder app ensuring that the Project mandatory setting in Employee Defaults is applied. The app now displays the accurate validation message “Project is mandatory. (Fault Code: 1187)” instead of a generic error.