Skip to main content
Skip table of contents

06.26.05-00

R2

  1. R2 Reports is fully supported (R2-25203)

    • Removed the Beta label from R2 Reports across applicable UI areas, reflecting its stable and production-ready status.

    • The update is limited to UI only, with no impact on existing R2 Reports functionality.

  2. Added Status Date to the Asset Search (R2-25198)

    • Added visibility and search support for Status Date on Asset Search screens of Maintenance, Accounts and Warehouse.

    • Reduces the need to manually open individual asset records to verify when the asset status was last updated.

    • Improves efficiency by enabling faster identification of assets with recent status activity.

  3. Configurable Security for Warehouse Task Exit Prompts (R2-25204)

    • Added runtime security support for the “All Items are not Filled/Shipped/Returned. Do you want to exit anyway?” prompt displayed during warehouse task during Prep, Ship, Return, and Multiple Return Order close.

    • Users can now configure prompt behavior using existing F6/F7 runtime security at both Global and Path security levels.

    • When either of the Yes/No options is configured other than Full Access, the system automatically skips the prompt and processes with the accessible option, reducing unnecessary interruptions.

  4. Search and add Non-Serial Items during Order Fill Scan (R2-25206)

    • Added a new Search Non-Serial Items option in the Fill Items Scan dialog of Rental Order Prep Tasks, enabling warehouse users to quickly discover and import non-serial inventory items directly during the scan fill process.

    • Users can now search inventory using existing filters such as Category and Sub-Category, select one or multiple non-serial items, enter quantities inline, and directly feed the selected items into the Fill Items Scan dialog without manually scanning or entering item IDs.

    • The enhancement eases the warehouse fulfillment operations during prep by reducing manual effort while preserving all existing barcode, QR code, and keyboard-based scanning workflows.

  5. Audit tracking is extended for some more critical R2 configuration settings (R2-24987 / R2-24986 / R2-25010 / R2-24994 / R2-25011)

    • R2 now records changes made to Misc. Types, Custom Order Statuses, Password Setup, License Viewer, Employee License, Currency Code List, and Currency Conversion Setup.

    • Helps users to quickly track what changed, who changed it, and when, improving visibility and control over key configuration updates.

    • Audit history captures add, update, and delete actions, with records available in Configuration Change History for easier monitoring and review.

R2 API

  1. Improved API Database Connection Handling (R2-22120)

    • Updated API connection handling to prevent multiple requests from sharing the same database connection.

    • Improves API reliability and helps prevent connection-related errors, such as result set corruption during concurrent requests.

R2 Labor

  1. Enhanced Crew Email Response Handling for Security Link Scanning Compatibility (R2-24975)

    • Prevents automated email security scans from being incorrectly recorded as crew responses.

    • Adds a confirmation page so crew responses are captured only after selecting an explicit action such as Available, Not Available, Accept, or Decline.

    • Improves response accuracy and user experience by avoiding false “already responded” messages and capturing optional or default comments in Booking View Messages.

Mobile Apps

  1. Resource-Based Pay Information Visibility in LaborMate (R2-25180)

    • Allows customers to hide pay-related details such as Pay Rate and Per Diem in LaborMate for selected resource types, such as In House crew.

    • Supports configuration-based visibility by resource type, while keeping pay information available for other resources such as Freelancers.

    • Helps protect sensitive payroll-related information while still allowing R2 Labor rates to be used for internal cost evaluation.

Bugs

  1. R2: After upgrading to 06.26.02-00, continuous scanning stopped working in Transfer Orders. When users scanned an item or asset, the scanned value remained in the field and the next scan was appended to the existing value instead of replacing it. As a result, warehouse users had to manually clear the field before scanning the next item, causing operational delays. (SR-32755)

    Fix: A fix is provided to provide full value in the scan field, which is automatically selected after each scan. When users enter or scan the next item, the previous value is replaced correctly instead of being appended. This behavior now works consistently across Transfer Order Fill, Ship, and Receive, Rental Prep, Ship, and Return, Sale Prep and Ship, PO Item Receive, and Item Receive Maintenance screens.

  2. CRM: When exporting data from Opportunity Search to CSV, company names containing commas were not enclosed in quotes. As a result, commas within the company name were treated as column separators, causing data to shift into adjacent columns and leading to incorrect CSV formatting. This issue affected exports across CRM screens where company names included commas. (SR-32623)

    Fix: A fix is provided to handle fields containing special characters according to standard CSV formatting rules (RFC 4180). Fields with commas are now enclosed in double quotes, ensuring correct column alignment in the exported file. This change applies across Opportunity, Company, and related CRM export screens, and does not affect other export functionality.

  3. R2: Warehouse tasks sometimes experienced delays when reopening after closure because the related order remained locked by a null R2 user / Oracle OS user. This caused users to wait before reopening or editing Prep, Ship, Pickup, or Return tasks, especially for orders with a large number of item lines. (SR-32822, SR-32841, SR-32817)

    Fix: A fix is provided to ensure that the order locks to release within a few seconds and significantly improving warehouse task reopening performance.

  4. R2: When editing cross-site orders, users could not view or search existing Purchase Orders while purchase assigning Labor lines within the order. (SR-32050)

    Fix: The Labor PO search is updated to be searchable by PO ID, even when users edit cross-site orders from a different Launchpad site.

  5. R2 API: The API server was accumulating a high number of inactive Oracle sessions, resulting in connection buildup and performance degradation under high concurrent load. (SR-32280)

    Fix: The root cause contributing to the connection buildup has been identified and addressed to prevent connection leaks and stale connection reuse. Additional safeguards have been implemented to ensure database connections are not shared across concurrent requests. These improvements enhance API stability under high-concurrency scenarios and ensure connections are properly released back to the database.

  6. R2: When printing a Standalone Invoice using CID #3, the invoice header displayed the Order Description instead of the Standalone Invoice Description. This caused confusion because CID #3 was intended for the order description and did not support printing the invoice’s own description. (SR-32576)

    Fix: The CID Master is updated to clarify that CID #3 is for Order Description. A new CID #63 has been added to print the Standalone Invoice Description, allowing users to include the invoice-specific description in the invoice header.

  7. R2 Labor: When using a multi-job email template for Confirmation Requests, the email preview did not include all selected booking lines across multiple orders. Some selected lines were skipped, even though they appeared correctly when using the standard confirmation template. (SR-32711)

    Fix: The multi-job template logic has been updated to process all booking lines for each selected order. The system now retrieves and includes all related booking line details in the email preview, ensuring all selected lines are included when sending multi-job email Confirmation Requests.

  8. R2: Serial kits sometimes showed as Filled even when the mandatory child assets were not scanned. This caused users to assume the kit was ready to ship, but the kit could not be dispatched because it was not fully filled. (SR-29287)

    Fix: Serial kit fill validation has been corrected to ensure mandatory child asset checks are not skipped. When required child assets are not scanned, the kit now shows as Partially Filled, prompting users to scan the mandatory child assets before shipping or returning the kit.

  9. PackNShip app: The Batch Return sometimes opened a blank exception remediation screen or showed inconsistent error behavior. This made it unclear why the return failed and prevented users from knowing how to continue. (SR-32158)

    Fix: The app is now handled to display a clear message with steps to close and reopen the task or Batch Return screen to start a new session consistently in such error conditions.

  10. R2 Labor: Exported timesheets did not display the Break Hours column when break hours were configured and applied to planning order lines. As a result, break hour information was missing from the exported timesheet output. (SR-33175)

    Fix: Updated the timesheet export process to correctly include the Break Hours column when break hours are configured for planning order lines. Break hour details are now displayed properly in the exported timesheet.

  11. PackNShip app: Users without a valid R2 license received a generic “Something Went Wrong” message when accessing warehouse tasks, making it unclear that the issue was related to license validation. As a result, warehouse tasks were not displayed for unlicensed users. (R2-25162)

    Fix: Updated the PackNShip app to display a clear license validation message when users without a valid R2 license attempt to access warehouse tasks. The app now correctly informs users to contact their administrator for license access.

  12. R2 Labor: When users updated Time Zone, Planner, or Pay Policy in the Planning Order header and saved the order, the system did not record the changes in History. As a result, users could not track these header-level updates made to the planning order. (R2-25119)

    Fix: Updated the Planning Order history tracking to correctly record changes made to Time Zone, Planner, and Pay Policy fields. These updates are now properly displayed in the History section after the order is saved.

  13. R2 Hero / R2 Reports: The InvoiceType column is blank in some invoice-related report views for certain invoice types, including Summary, LR, and Deposit invoices. As a result, report output did not consistently match the InvoiceType value shown in R2 Application → Search Invoices. (R2-24886)

    Fix: The InvoiceType column is now consistently populated for Summary, LR, and Deposit invoice types in the following reporting views:

    • Invoiceview

    • REP_InvoiceDetailView

    • Rep_Syntax_CustomerInvoiceView

    • REP_InvoiceTaxDetailView

    • REP_GroshInvoiceTaxDetailView

    • Rep_InvoicePostedDetailView

    • Rep_InvoiceDetailinfoview

    • REP_InvoiceUdfDetailView

    • REP_InvoiceUdfRepView

    • REP_WorkOrderInvoiceView

    • Rep_WorkOrderInvoiceDetailView
      Invoice type labels are now aligned with what users see in Search Invoices, ensuring reports display accurate and complete invoice type information.

  14. R2 Labor: The History button was displayed in the Crew Edit → Site Pay Policy tab even though history functionality was not supported for this grid. Clicking the button opened a blank screen because the corresponding history screen and backend history data generation were not implemented. (R2-25191)

    Fix: The History button is removed from the Crew Edit → Site Pay Policy tab. Users will no longer see the unsupported History option, preventing blank screen navigation and ensuring the UI only displays supported functionality.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close