Skip to main content
Skip table of contents

Latest Release

(06.25.09-00)

R2
  1. Retire multiple assets efficiently via scan or batch upload (R2-24110)

  2. Transportation Schedule, Driver, Vehicle, and Trailer Availability Gantt views are available in R2Web (R2-21475)

    • These views have been modernized using Java technology, replacing the legacy VB-based system and enabling access across all platforms. Currently, the Driver creation and editing functionality still resides in the VB system, but it will be migrated to Java in upcoming releases.

  3. REP_PRODUCTDETAILVIEW - Added new column ‘isActive’ (R2-24181)

  4. REP_ORDERPRODUCTDETAILVIEW - Added two new columns (R2-24173)

    • ActualShippedDate: Displays the actual dispatched date for Out and Sold items.

    • AssetInventoryGL: Displays the dispatched asset’s Inventory GL code ID.

Labor
  1. Access 'Settings' from Profile (R2-24146)

    • The 'Settings' option is accessible directly from the Profile section.

    • This feature is restricted to Administrators only, reinforcing role-based security.

CRM
  1. Edit Call logs in Opportunity (R2-24107)

    • Helps maintain accurate and up-to-date information.

API
  1. Transfer Fill API enhancements (R2-21967/R2-21916)

    • Filling Out, Filled and Other Site assets based on Force Fill configurations.

    • Filling Lost and Missing assets considering the Auto Return Missing/Lost configuration.

  2. Batch Return API: Restricted return within a Transfer Order (R2-24152)

    • Receiving only if the asset belongs to a Transfer Order

Mobile Apps
  1. PackNShip: Force Fill In, Filled, Out, Missing and Lost assets in Transfer Orders (R2-23625)

    • Filling Out, Filled and Other Site assets based on Force Fill configurations.

    • Filling Lost and Missing assets considering the Auto Return Missing/Lost configuration.

Bugs
  1. R2: Emails were not being sent when using OAuth 2.0 authentication setup. (SR-27753)
    Fix: This issue has been resolved, and emails now send successfully when using OAuth 2.0 authentication setup.

The issue was present in versions 06.25.04-00 to 06.25.08-00.

  1. R2: The Equipment Usage View (EUV) was showing the wrong number of records and missing bars when the "Quantity" checkbox was selected, and assets were assigned to different shelves. (SR-28377)
    Fix: The display has been corrected. The EUV now shows the correct number of records and bars, regardless of shelf assignments.

  2. R2: Duplicate filled lines appeared on orders after opening and closing the Order Fill screen multiple times, when those lines are linked to transfers. (SR-28216, SR-28456)
    Fix: The system now prevents duplicate filled lines from being created during these actions.

The issue existed only when specific sequence of actions involved and order lines are linked to transfers, not otherwise.

  1. R2: The "Do not release order on system crash" option was previously available in the Configuration module. However, it was redundant, not linked to any functional feature, and potentially misleading. (SR-24483, SR-6425)
    Fix: This option has now been removed from the Configuration module.

  2. R2: The EUV grid previously displayed the time-bar for Sub-rent POs based on the Required Date, even though the bar itself was drawn from Receive From Vendor Date to Return To Vendor Date. This mismatch caused the time-bar to disappear whenever the EUV date filter did not align with the Required Date. (SR-28088)

    Fix: The EUV grid now displays the time-bar for Sub-rent POs based on the Receive From Vendor Date to Return To Vendor Date, ensuring that any Sub-rent PO within the selected EUV duration is consistently displayed.

  3. R2: Master Bill (MB) invoices displayed incorrect amounts when package child items had a quantity of zero. In such cases, revenue was not allocated correctly to child lines, which led to mismatched MB amounts and discounts. (SR-27980)

    Fix: The revenue allocation logic for NS-Kit (package) items has been updated.

    • If some child items have quantity = 0, revenue is now distributed across child items with non-zero quantities.

    • If all child items have quantity = 0, revenue is assigned to the first child item.
      This ensures that MB invoice amounts and discounts are calculated correctly.

  4. R2: Voiding a Voucher while its linked PO was open in another session caused the system to hang without showing any message. (SR-27759)

    Fix: The system now prevents the Void operation in such cases and displays a clear error message indicating which PO(s) are currently in use. This ensures that users are informed immediately, and the system no longer hangs.

  5. R2: When invoicing a main order while its sub-order was open, the system displayed a confusing technical error message referring to “periodic invoices,” which did not match the order configuration. (SR-27940)

    Fix: The system now shows a clear and user-friendly error message when a sub-order is locked, specifying which sub-order(s) are in use and by which user. This removes the misleading technical details and improves usability.

  6. R2: When cancelling or editing orders linked to a Return Transfer that was open in another session, the system allowed invalid operations (e.g., cancelling the parent transfer, failing to close dialogs, or leaving links active) instead of showing proper lock messages. (SR-27898)

    Fix: The system now validates Return Transfer locks consistently.

    • If a Return Transfer is open in another session, operations like editing dates, cancelling lines, or cancelling the parent transfer are blocked.

    • Clear error messages are displayed (e.g., “Return Transfer Order [ID] is in use by [User]”), and dialogs close automatically where required.
      This ensures data integrity and prevents lingering order links after cancellations.

  7. R2: Non-serial items could not be shipped directly from the Ship Order screen using the Scan and Ship Item/Container option, returning an error even though the item was valid. (R2-24253)

    Fix: The system now correctly handles non-serial items in the shipping task. Ship scans work for both serial and non-serial items without error, and existing functionality for serial items remains unaffected.

  8. R2: Receiving an Inventory Purchase Order was blocked if the Product ID had been modified after the PO was created. (R2-24084)

    Fix: The system now allows receiving items on Inventory POs even after Product IDs are changed, including for linked POs and batch receive operations.

  9. R2: In Purchase Order and Warehouse modules, searches using Whole Field on Employee/Contact Name did not return results when Middle Name or Last Name was not present. (R2-24102, R2-24105)

    Fix: Searches by Employee/Contact Name now work correctly across the following access points:

    • Purchase Order

      • View → Purchase Orders (Pending Approver(s), Created By, Vendor-Site)

      • Invoicing → View/Search Purchase Orders (Created By)

      • Warehouse → Sub Rental POs (Created By)

      • PO Item Search (Created By)

      • Voucher → Import PO (Created By)

      • Order → Availability → On Order (PO) (Created By, Vendor Name)

      • Service Work Order → View → Purchase Orders (Created By, Vendor-Site)

    • Warehouse

      • Search (Customer/Vendor, Assigned To)

      • Assign (Customer, Sales Person, Assign To)

      • Overdue (Billing Contact)

      • Ship Orders / Return Orders / Fill Order / Pick Order (Contact Name, Billing Contact Name)

      • Ship Order → Pickup Order (Created By)

      • Transfer Order (Client Name, Company Name)

      • Receive (Vendor Name, Employee Name)

      • Transportation Logistics (Driver, Customer, Assigned To)

  10. R2: The Order Product Detail report, based on REP_ORDERPRODUCTDETAILVIEW, was taking unusually long to execute and caused delays in loading results. (SR-26884)

    Fix: The report has been optimized and now executes much faster, while continuing to return accurate results.

  11. R2: The Contact report, based on REP_CONTACTVIEW, was taking unusually long to execute and caused delays in loading results. (SR-26884)

    Fix: The report has been optimized and now executes much faster, while continuing to return accurate results.

  12. R2: Product IDs containing special characters (such as ; , : ' " < > / \ | ? *) could not be retrieved through R2 APIs. (SR-27670)

    Fix: To prevent such issues, the system now restricts the use of these reserved characters in the Product ID field for all new entries and future modifications.

    • Existing Product IDs with these characters will remain unchanged and continue to work as-is.

    • Going forward, new Product IDs or edits will not allow these restricted characters.

    Restricted Characters:

    • Semicolon (;)

    • Comma (,)

    • Colon (:)

    • Single Quote (')

    • Double Quote (")

    • Less than / Greater than (< >)

    • Forward Slash (/)

    • Backslash (\)

    • Pipe (|)

    • Question Mark (?)

    • Asterisk (*)

  13. R2: In the Equipment Usage View (EUV), product descriptions previously displayed in the native language even when the Launchpad language was set differently. (SR-27253)

    Fix: Multi-language support has now been implemented for EUV and other graphical screens (AUV, APV, ATV). The following fields now respect the Launchpad language setting:

    • Product Description (EUV → LHS, header & line records)

    • Company Name (EUV → RHS → Tooltip & Toolbar → From)

    • Vendor Name (EUV → RHS → Tooltip)

    • Ship to Address (EUV → RHS → Tooltip)

  14. R2: The canned report “Missing/Lost/Damaged” previously ran slowly and caused high CPU usage during multiple concurrent sessions. (SR-23995)

    Fix: Report execution has been optimized by fetching languageId efficiently and refactoring nested sub-queries. Data accuracy is maintained, and report performance is significantly improved.

  15. R2: When reducing the package header quantity, child lines whose quantity became zero (typically lines split due to availability shortage when the package quantity was increased) were retained with no status, causing confusion and requiring manual cleanup. (SR-28381)

    Fix: The system now automatically removes any child line whose quantity becomes zero during a package quantity reduction, while retaining lines that were already zero in the original definition or manually set. Increasing the package quantity continues to update existing zero-quantity lines rather than creating new ones.

  16. R2 Web: The Cover Letter Setup button in Configuration was incorrectly enabled in the R2 web interface, even though it relies on desktop-only functionality. (R2-24209)

    Fix: The button is now disabled in R2 Web while remaining enabled in the desktop application.

  17. R2 & Labor: The caption Assign Dates was inconsistent with labor planning terminology. (R2-24177)

    Fix: The caption has been updated to Assign Dates (EWT) across relevant R2 and R2 Labor screens, ensuring consistency in menus, tooltips, and grid actions.

  18. Labor: In R2Labor, the email template preview for Send Confirmation and Send Availability Request sometimes failed to display correctly when switching between templates. (SR-27586)

    Fix: The issue has been resolved, and template previews now consistently open and display as expected.

  19. Labor: In the Update Lines screen of Labor Planning, fields Status, Pay Policy, and Unit were incorrectly marked as mandatory, leading to confusion in multi-line updates. (R2-24171)

    Fix: The mandatory indicators for these fields have been removed. Functional validation will continue to be handled appropriately without misleading markers.

  20. Labor: In the Update Lines screen of Labor Planning, updating the Rate field did not reflect changes on booking lines. (R2-24166)

    Fix: The Rate field now correctly updates single and multiple booking lines when applied, provided the Rate is not locked.

  21. Labor: In the Labor module, the right-panel email forms (e.g., Send Message, Send Availability, Send Confirmation, Communicate to UBA/Resource, Crew Availability Request) showed fields misaligned/horizontally aligned when the panel was expanded. (R2-24149)

    Fix: The form fields now remain properly aligned in a vertical layout, regardless of panel width.

  22.  PackNShip app: In the PackNShip app, when Bulk Submit was OFF during batch return, each scan split the order line into multiple lines, unlike expected behavior in R2. (R2-24112)

    Fix: The app now keeps the session open and syncs only on screen exit, timeout, or when Bulk Submit is turned ON, preventing unnecessary line splits.

     

JavaScript errors detected

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

If this problem persists, please contact our support.