Latest Release
(06.25.11-00)
Predefined Descriptive, Blank & Subtotal Lines in Section Configuration (R2-24389)
You can configure descriptive, blank, and subtotal lines directly within the section definition.
This enables you to create pre-built, structured sections that guide salespersons during order entry.
When a section is added to an order, the predefined lines appear automatically, ensuring consistency and saving time.
Open Order and Close Order Options in Order Edit Window (R2-24404/ R2-24405)
You can now open or close orders directly from the Order Edit window, without navigating to Order Search.
Optimizes your workflow by reducing clicks and simplifying order status management.
Maintains synchronization between main and sub-order statuses automatically.
Enhances efficiency and control while ensuring all system validations remain intact.
Find option in Retire Assets screen (R2-24257)
Added a Find icon on Bulk Retire Assets and View Scan Exception screens for quick text search.
Improves usability and speeds up bulk validation.
Enhanced Auto PO Creation – Consolidated by Vendor/Resource (R2-24271)
Enables automatic consolidation of Purchase Orders during booking confirmations.
Merges multiple booking lines into a single PO based on vendor and resource logic.
Improves accuracy, audit tracking, and PO visibility while reducing duplicates.
Flexible In / Out Time Format in Timesheet Export (R2-24293)
Timesheet Export file is enhanced to provide flexible time format while entering Actual In / Out times.Allows you to enter time in multiple formats (e.g., 3a, 3:15p, 1315, 23:30).
Automatically converts inputs to match your time format (12-hour or 24-hour).
Supports flexible spacing and case (e.g., 3 a, 3A, 3pm, 3 p).
Gracefully handles invalid or incomplete inputs.
Timesheet exports are now generated in the .xlsm format instead of .xlsx. This change enables the use of macros, which provide greater flexibility and automation when working with timesheets.
When you open the exported file, macros are disabled by default. To enable and run macros, select Enable Content on the security warning bar.
Labor Module is Migrated to 64-bit Architecture (R2-23195)
The R2 Labor application has been migrated to a 64-bit architecture to improve performance, scalability, and long-term compatibility.Enables higher memory access (up to 8 TB vs. 4 GB in 32-bit).
Delivers better performance and processing efficiency.
Enhances scalability for growing workloads.
Ensures future readiness with modern platform support.
Introducing Shelves API (R2-24288/ R2-24287/ R2-24286/ R2-24285)
GET: Retrieve all shelves
GET by ID: Retrieve details of a specific shelf ID
POST: Create a new shelf
PUT: Update existing shelf details
Saved User Views for Filters and Sorting (R2-23360)
Introduced User View management to save and restore preferred filters and sort order across sessions.
Supports saved views per entity (Activity Manager, Customer, Opportunity) for improved personalization and efficiency.
Ensures persistent filter and sort states, retaining user configurations after reload or re-login.
R2: In the Order Warehouse Change History screen, searching by Employee returned results only when a single character (e.g., “M”) was entered. Searches using multiple characters or full names (e.g., “Matthew”) returned no records. (SR-29119)
Fix: The search logic has been corrected to handle full or partial name inputs consistently. The system now retrieves all matching records regardless of case or character length, ensuring that users can search by complete or partial employee names across all Change History views — including Order → Item, Order → Labor, and Warehouse.R2: The Sell Price field was still visible in the Asset edit screen and appeared in API responses, even though it was no longer used, leading to confusion during asset maintenance and integration processes. (SR-29076)
Fix: The Sell Price field has been fully deprecated. It is now removed from the Asset edit screen, excluded from the Get Asset by ID and Update Asset (PUT) APIs, and marked as “deprecated” in the Swagger documentation. Any value provided for this field in API requests is ignored, and it is no longer referenced in data conversion.R2: In the Order print form, when using Component Type 116, the field alignment options (Left, Center, Right) were not applied correctly — both the field headers and their corresponding values always defaulted to left alignment in print outputs. (SR-29080)
Fix: The alignment logic was corrected to retrieve and apply the selected alignment from the form configuration. Alignment settings now work properly for both field headers and their values in portrait and landscape orientations.R2: When the Item Price Group or Labor Price Group was changed at the Order Header level, the system did not record these updates in the Order Header History. Additionally, the resulting price updates on Item or Labor lines — triggered by the updated Price Group and its associated Rate Card — were not captured in the Order Line Change History, making it difficult to trace pricing adjustments and their origin. (SR-27917)
Fix: The system now logs all changes to the Item Price Group and Labor Price Group in the Order Header History, and records corresponding price updates on affected lines in the Order Line Change History. This provides complete traceability of pricing changes driven by rate card selections at the order level.R2: The Order Item List search for Product ID and Description was case-sensitive, requiring users to enter exact letter casing (e.g., uppercase or lowercase) to retrieve matching records. This made it difficult to locate items efficiently. (SR-29556)
Fix: The search functionality in the Order Item List has been enhanced to be case-insensitive for both Product ID and Description fields. Users can now find matching items regardless of text casing, ensuring a smoother and more consistent search experience.R2: When users marked an asset as Not Available, the system incorrectly displayed a message indicating that a Service Work Order (SWO) already existed, even when none was present. This caused confusion and prevented users from immediately updating the asset’s availability. (SR-29539)
Fix: The system now correctly validates the presence of active SWOs before displaying the prompt. If no SCHEDULED or ESTIMATE SWO exists, the asset is marked as Not Available immediately without any warning. This ensures accurate availability updates and removes unnecessary user intervention.R2: When using the Alt + K hotkey, the system incorrectly opened the Pick Order screen instead of the intended Print PickList window. This occurred when the Group Icons option was enabled under Configuration → Themes, causing the shortcut mapping to behave inconsistently. (SR-29417)
Fix: The shortcut for Pick Order has been reassigned to Ctrl + K, ensuring that Alt + K consistently opens the Print PickList window. The hotkey functions now work as expected, regardless of the Group Icons configuration.R2: When printing invoices using forms 153000UI, 153100UI, or 153200UI, sub-order details were missing if the invoice was printed from a site different from where the order was created. This led to incomplete or inconsistent invoice outputs across sites. (SR-28432)
Fix: The invoice print process for forms 153000UI, 153100UI, and 153200UI has been made site-independent. It now correctly includes sub-order details in all cases, ensuring complete and accurate invoice prints across all sites.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 Sub Order was linked to a Main Order associated with a Master Bill (MB), the system incorrectly referred to the Sub Order’s own MB setup while calculating discounts for Service Charge, Damage Waiver, and Consumables, instead of inheriting the MB configuration from the Main Order. This caused inconsistent MB discount values and billing discrepancies between the Main and Sub Orders. (SR-29512)
Fix: The system now ensures that the Sub Order always inherits the Master Billing setup from its Main Order. Any discount calculation for Service Charge, Damage Waiver, and Consumables is now derived directly from the Main Order’s MB configuration, regardless of the “Default Main Order to Sub Order” flag setting.
Labor: In the Communicate → UBA process, the Excel attachment sent with each company-specific email did not include bookings assigned with free-form resources — i.e., resource names entered manually as text rather than selected from existing crew profiles. As a result, such manually entered resource bookings were missing from company-wise communication even when they were part of assigned or confirmed bookings. (SR-29326)
Fix: The UBA communication process now includes bookings assigned with free-form resources, with all relevant booking details reflected in the company-specific Excel and email for all applicable statuses — Assigned, Confirmed, Re-confirm, and Re-confirmed.
Additionally, the Excel attachment has been refined as follows:
The “Report To” column has been removed as it was redundant.
The “Reporting Address” column has been renamed to “Reporting Instructions.”
R2: In the Voucher → Resource Import process, timesheet lines associated with booking lines of free-form resources — i.e., resource names entered manually as text rather than selected from existing crew profiles — were not appearing in the import list. As a result, approved timesheets for these manually entered resource bookings could not be vouchered, preventing payment processing for such bookings. (SR-29326)
Fix: The system now supports vouchering for free-form resources in the same way as for standard crew profiles. The import process now includes all eligible timesheets based on the following rules:
Resource Types Considered: Timesheet lines linked to booking lines classified as Freelancer, Broker, Pay Agent, Union, or Blank are eligible for vouchering. In-House type timesheet lines are excluded.
Approval Requirement: Only timesheet lines marked as Approved after internal review can be processed for vouchering.
Merging Logic: When a timesheet has multiple lines for the same resource (e.g., across different days or pay rates), all such lines belonging to the same booking line are automatically merged into a single voucher line for simplified payment processing.
Status Handling:
When a voucher is saved, the linked timesheet lines are marked as Paid and Closed.
If a line is removed from a voucher, the corresponding timesheet line status reverts from Paid/Closed back to Approved.
R2: In the Voucher → Resource Import process, timesheet lines associated with booking lines of free-form resources — i.e., resource names entered manually as text rather than selected from existing crew profiles — were not appearing in the import list. As a result, approved timesheets for these manually entered resource bookings could not be vouchered, preventing payment processing for such bookings. (SR-29326)
Fix: The system now supports vouchering for free-form resources in the same way as for standard crew profiles. The import process now includes all eligible timesheets based on the following rules:
Resource Types Considered: Timesheet lines linked to booking lines classified as Freelancer, Broker, Pay Agent, Union, or Blank are eligible for vouchering. In-House type timesheet lines are excluded.
Approval Requirement: Only timesheet lines marked as Approved after internal review can be processed for vouchering.
Merging Logic: When a timesheet has multiple lines for the same resource (e.g., across different days or pay rates), all such lines belonging to the same booking line are automatically merged into a single voucher line for simplified payment processing.
Status Handling:
When a voucher is saved, the linked timesheet lines are marked as Paid and Closed.
If a line is removed from a voucher, the corresponding timesheet line status reverts from Paid/Closed back to Approved.
Labor: With Auto PO creation feature enabled, when a booking line included a manually entered free-form resource name (i.e., not linked to an existing resource profile) but had a company assigned (Union/Broker/Pay Agent/Freelancer types), the system did not generate a Purchase Order (PO) automatically upon confirmation. (SR-29326)
Fix: The PO creation process has been enhanced to support booking lines assigned with free-form resources. The system now correctly references the company tagged on the booking line, ensuring automatic PO generation even when the resource is not linked to a resource profile.
Additional logic has been implemented to handle free-form resource scenarios consistently:
For Freelancer resource types, one PO is created per booking line when the free-form resource name is entered.
For other resource types, booking lines with the same vendor are consolidated into a single PO. Booking lines with blank resource type on booking lines are treated as Broker type.
Once a PO is created for a free-form resource line, the company field cannot be modified.
Updating a free-form resource name retains the existing PO and adds a note to the PO line capturing the name change.
Changing the resource type from Freelancer to Broker after PO creation does not merge the PO with other Broker POs — it remains as a standalone record.
Clearing a resource voids the PO line and cancels the PO if it contains no other valid lines.
This update ensures auto PO creation functions consistently for both standard and free-form resource bookings, maintaining integrity between labor booking and purchasing workflows.
R2: In sales orders, when the configuration “Default Charge Start to Bill Date in Sales Order” was set to False, orders with a blank Bill Date did not display the Amount and Profit Margin values. (SR-29880)
Fix: The system now correctly displays the Amount and Profit Margin values even when the Bill Date field is left blank.
R2/Labor: When the Prep Time was changed at the order header level from R2, the system incorrectly set related booking lines to Re-confirm status on the Labor Planning Order, even though their line-level dates had not changed. This issue occurred when the following configuration settings were applied:
Configuration → General → Split Labor Line by Qty = False
Configuration → Pricing / Billing → Labor Cost Based On = Prep Date
(SR-27799)
Fix: The system now updates booking line statuses only when actual line-level dates are modified. Changing the header-level Prep Time no longer triggers a Re-confirm status under the above configuration settings.
R2: Item availability did not update correctly in certain multi-user and post-receipt scenarios during Transfer Order processing. When one user opened a Transfer Order already in use by another, the system allowed access in read-only mode correctly; however, it caused inconsistencies in item availability for items modified in the active (read-write) session. Additionally, after the transfer was received at the destination site, the T-In and T-Out quantities continued to display instead of clearing as expected. (SR-27734)
Fix: The system now correctly handles item availability and concurrency for Transfer Orders, ensuring consistent and accurate stock updates without causing availability issues.
R2: When reopening orders using the Open Order(s) function, only the selected order was being reopened, while its associated sub-orders remained closed. This caused inconsistencies between main and sub-order statuses, as the Close Order(s) function correctly closed both the main and all related sub-orders. (R2-24408)
Fix: The Open Order(s) functionality has been enhanced to align with the close behavior. When a main order is reopened, all its sub-orders are automatically reopened as well. Similarly, reopening any sub-order now reopens its main order and all other sub-orders under the same main order.
This update ensures consistent synchronization of order status across main and sub-orders during both open and close operations.
PackNShip app: The date-based search filters in the task lists (Prep, Ship, and Return/Receive) did not clearly represent how date conditions were being applied. Users found it difficult to interpret whether tasks were being filtered for a specific day or up to a certain date, leading to confusion in locating tasks. (R2-24401)
Fix: The date filter display has been enhanced for better clarity and consistency with the app’s existing search logic:
The app now displays the “=” symbol when Yesterday, Tomorrow, or Custom Date is selected.
The app displays the “<=” symbol when Today is selected.
These symbols now align with the app’s search behavior — “=” indicates filters for the exact date, while “<=” indicates tasks up to and including the current date.
This update improves clarity for users by making the filter condition visually match the system’s actual search interpretation.
PackNShip app: The date-based search filters in the task lists (Prep, Ship, and Return/Receive) did not clearly represent how date conditions were being applied. Users found it difficult to interpret whether tasks were being filtered for a specific day or up to a certain date, leading to confusion in locating tasks. (R2-24401)
Fix: The date filter display has been enhanced for better clarity and consistency with the app’s existing search logic:
The app now displays the “=” symbol when Yesterday, Tomorrow, or Custom Date is selected.
The app displays the “<=” symbol when Today is selected.
These symbols now align with the app’s search behavior — “=” indicates filters for the exact date, while “<=” indicates tasks up to and including the current date.
This update improves clarity for users by making the filter condition visually match the system’s actual search interpretation.
PackNShip app: The Bin and Shelf values displayed in the warehouse task details (Prep/Fill, Ship, and Return screens) were too small and appeared in a faint grey color, making them difficult to read—especially under low-contrast or dark mode settings. (R2-24399)
Fix: The display of Bin and Shelf information has been reformatted for better legibility:
The font size has been increased to match that of the Description and Product ID fields.
The Shelf and Bin values now appear on separate lines, in italic style, and with a darker text shade (brighter in dark mode) for improved readability.
These enhancements apply across Prep, Ship, and Return/Receive task screens for all item types — serial, non-serial, and kit items.
This update ensures the Bin/Shelf details remain consistently visible and easy to read in both light and dark display modes.
R2: Users were unable to void vouchers that had inventory tagged but were not linked to a purchase order (PO). (R2-24380)
Fix: The system now allows voiding of vouchers with inventory items regardless of whether a PO is linked or not.
R2: When using the Open Order(s) and Close Order(s) actions, the system behaved inconsistently depending on the View Sub-Orders flag and which order was selected. Specifically:
When View Sub-Orders was true, the Close Order(s) action correctly closed both the main and sub-orders. However, the Open Order(s) action reopened both only when the main order was selected, not when a sub-order was selected.
When View Sub-Orders was false, both actions affected only the selected order, leaving the related order (main or sub) unchanged.
As a result, reopening from a sub-order or when the flag was off did not restore the full main–sub order linkage. (R2-24409)
Fix: The system now reopens both main and sub-orders together, regardless of whether the View Sub-Orders flag is enabled or which order (main or sub) is selected.
After reopening, both orders return to their original active state, ensuring consistent handling between the Open Order(s) and Close Order(s) actions.Labor: In the Planning Order Header, the Comments screen did not display a scrollbar when lengthy text was entered, preventing users from viewing or editing the complete content. Additionally, related Planning Order screens such as Rating and Header Comments failed to load properly. (R2-24387)
Fix: The system now displays a vertical scrollbar in the Planning Order Header Comments screen when the entered text exceeds the visible area, allowing users to scroll, add, and edit long comments seamlessly.
Additionally, the Rating and Header Comments screens in the Planning Order module have been corrected to load properly.R2: The SalesCost value in the Rep_InvoiceView report was calculated incorrectly for sales order lines that were linked to purchase orders and subsequently split. The issue resulted in an overstated SalesCost value in the report compared to the expected cost derived from the linked purchase order line. (R2-24255)
Fix: The system now accurately calculates the total cost for Purchase Order–linked sell items, including split cases, based on the formula:
Total Cost = Order Line Quantity × PO Line Unit Price
For example, if the PO Line Unit Price is 100 and the Order Line Quantity is 2, the Total Cost will now correctly display as 200.