Rate AI

Feature # 4108 - Option to view the audit trail at cell level within Price Inspector

Business Need

Currently to access the audit trail of any particular cell in the price inspector table, user(s) need to navigate through multiple steps: open the lane price edit page, select the audit lane option, and apply the filter on a particular field to view the audit details for that particular cell. This process is laborious and clumsy.

Providing an ability to access the cell audit details with a single click will significantly improve user efficiency and streamline navigation.

Solution

With this feature, user(s) can directly access the audit trail of any selected cell from the cell itself within the Price Inspector table. This will save time and simplify the process of accessing cell audit details.

Feature Enablement

This will be a default feature, no configuration or feature enablement is required.

Feature #3979 - Merge Currency Fields into Single Column for Excel Downloads

Business Need

Currently, when users download data from Price Inspector to Excel, RateAI generates two separate columns for each currency field—one for the value and another for the currency code. For Price Inspectors with many currency fields, this results in an excessive number of columns, making the data file unwieldy.

To enhance usability, this feature will consolidate currency fields into a single column for Excel downloads.

Solution

This feature changes how Excel files are generated when data is downloaded from Price Inspector. The currency fields will now be contained within a single column, aligning more closely with how data is displayed in Price Inspector.

Typically, users download data from Price Inspector, modify it in Excel, and then upload it back to RateAI in its internal format. As users depend on the downloaded file’s format for successful uploads, the consolidation of currency fields simplifies this process.

With this update, the currency code column will be removed, and the currency will be implicitly indicated by the cell’s formatting. This mirrors the approach already used in the inbound process for Shipper files, where the currency code is inferred from the cell format.

The system will expect the currency format to follow the same structure as the downloaded file, where a three-character currency code is used to format the cell. During data uploads, the system will inspect the cell’s format to determine the currency of the value.

If the currency cannot be inferred from the formatting, the system will block the update and log an error, enabling users to quickly identify the issue and correct it.

Feature Enablement

This will be a default feature, no configuration or feature enablement is required.

Feature # 3906 - Populate Dropdown List in Excel Download for Dropdown Data Type Fields

Business Need

Many users prefer to work with lane-level information offline in Excel and then upload the revised data. However, when users download Price Inspector data that includes a Dropdown field, the resulting Excel file doesn’t provide the valid options for that field. As a result, users may encounter errors during the upload process if they input invalid values for the Dropdown field.

Solution

To resolve this issue, RateAI will enhance the Excel download functionality by configuring Dropdown fields in Price Inspector as "List" cells within Excel.

When users download an Excel file that includes a Dropdown field (e.g., Hazmat Class), the corresponding cell will be formatted as a List.

This will ensure that users can only select valid values from the predefined list based on the Record Type field configuration, reducing the likelihood of upload errors due to invalid inputs.

Feature Enablement

This will be a default feature, no configuration or feature enablement is required.

Feature # 4271 - Enhanced Charge Code Functionality for Ad-Hoc Pricing Fields

Business Need
With the existing charge code feature, users could specify additional attributes—such as charge codes, primary bill type, and secondary bill type—for ‘standard’ pricing fields defined in the pricing template via Insights. These values would then be included in the internal format file (Excel) generated after completing the ‘Create Submit’ action. This file can be integrated into downstream systems like accounting and TMS systems. However, until now, ‘ad-hoc’ pricing fields were not supported within this functionality.

Solution
With this release, you can now manage additional attributes for ad-hoc pricing fields as well. This enhancement ensures that the same level of attribute management is available across all pricing fields, allowing a more comprehensive integration into your downstream systems.

How it works:

1. Configuration Setup
   • Reach out to your Winmore Support to enable this feature. Once set up, all ad-hoc pricing fields will be displayed in the respective workbench as a separate table.
2. Managing Additional Attributes for Ad-Hoc Pricing Fields

   • Step 1: Expand the ad-hoc pricing fields table and click on the ‘Export’ button to export the fields to an Excel file.

   • Step 2: Save the Excel file locally and enter the required details for each field—charge code, primary bill type, and secondary bill type.

   • Step 3: Re-import the updated file into the table using the ‘Import File’ button to populate these attributes in the system.

3. Final Output

   • Upon clicking on ‘Create Submit’ button in Pricing Inspector, additional attributes will now be included in the internal format file, making them available for downstream integration.

Feature Enablement

Please contact Winmore Support to turn this feature on.

Winmore Platform

Feature # 3686 - New Data Type: Date Only - Timestamp free date

Business Need

Currently, all "Date" fields in the Winmore platform include a time component, which is determined by the specific time of day a user updates the field. Other factors, like time zone, are inferred from the user's browser settings. When users view a date-time field, the system adjusts it based on the user's location and time zone. As a result, users in different time zones may see different date and time values for the same field.

For example, a user in California might see "October 30th, 2024, 11:00 PM," while a user in Paris might see "October 31st, 2024, 8:00 AM."

While there are valid use cases where date fields should include a time component and be adjusted for time zones, many cases only require the date, without time or location-based adjustments.

Solution

To address this, we are introducing a new "Date Only" field that users can select when creating record types. This new field type will not replace the existing date field but will serve as an alternative for new fields. Importantly, there is no automatic migration of existing fields to this new type; it will only apply to newly created fields.

The "Date Only" field will not be subject to time zone conversions. Although a time component is required by the backend, it will always be set to 00:00 UTC, ensuring that the date remains consistent across all time zones.

Feature Enablement

This will be a default feature, no configuration or feature enablement is required.