In an effort to continuously improve our platform, we are planning several deployments for the month of September across both of our clusters. Please see the Dates and Features below for each of these deployments.
On September 9th, 2023 in our North American Cluster, we will be releasing below features/enhancement/bug fixes and performance improvement in a single deployment.
Ref # |
Features |
Practical Change |
Users |
1 |
Database design for formula re-architecture & pusher changes |
This set of enhancements is aimed at refining the formula handling architecture within the Winmore platform to address existing limitations such that formula evaluation takes place at "insert/update" instead of "select". We have mainly moved the formula calculation from "select" query to the "insert/update" queries. Hence the formula results will be calculated at each insert/update operation & the results will be saved in the table. We have implemented this formula calculation using DB triggers. Thus any update operation such as lane edit, batch update, formula update, or blackout will take some time to complete. But the loading time will be much faster as we are not calculating the formula during loading. Furthermore, the new centralized codebase minimizes redundancy, making maintenance seamless and contributing to a more streamlined user experience. |
Readily available for RateAI Users |
2 |
Skip exchange rate file upload if there is only a single currency per lane in bid Currency Conversion |
Today, the system asks for an exchange rate file even when the shipper requested currency and the currency in the PI table are the same, leading to unnecessary errors and delays. This feature aims to improve the system's currency processing. With this update, the system now intelligently recognizes this scenario and eliminates the need for an exchange rate file if all involved currencies are the same. No currency conversion shall be needed in this case. |
Readily available for RateAI Users |
3 |
Notifications for Batch update process in PI (Price Inspector) |
This enhancement is to notify the users about the batch update in PI. When a backend process(updation) is being done in a crane sheet/PI, the user/users in that crane sheet/PI should be informed/updated about the same. The current system doesn’t show these notifications completely. |
RateAI Users with Formula Rearchitecture enabled |
4 |
Manual re-calculation for formulas in a record and associated related records |
This is an option for the users to recompute formulas for their records. The formulas updated in the studio will not be updated to all the records, this option will update the formulas for that specific record. The 'Recompute Formulas' option is automatically enabled for all customers that have Formula Rearchitecture enabled. |
RateAI Users with Formula Rearchitecture enabled |
5 |
Allow exchange rate to be defined between any two currencies |
In the current system, all exchange rates need to be set up based on USD. With the new update, we're removing this restriction. We can now set up exchange rates directly between any two currencies, without needing to go through USD as a middle step. If the exact exchange rate you required isn't readily available, the system will try to derive the exchange rate from the available rates. Direct rates from source currencies of operands to the formula target field currencies are expected. If such rates are missing the system will show it as #Value. Users can generate the possible combinations of exchange rates using enrichment configured in the layout from the old set of exchange rates. If only USD to GBP & USD to INR rates are available in the exchange rate table, it will generate GBP to USD & INR to USD rate (inversion) and GBP to INR rate & INR to GBP rate (triangulation). |
RateAI Users with the Rules Engine Support feature flag enabled
Enrichment steps described below for RateAI Admin Users |
6 |
Update exchange rate enrichment based on the target currency list |
The enrichment created to derive exchange rates derived all possible combinations of sources and targets in the exchange rates file. This resulted in the insertion of a large number of exchange rates in the table causing performance issues. This feature aims to update the exchange rate enrichment to generate exchange rates in which the target currency is present in the currency list. With this change, the target currencies involved in the formulas are taken into account and only the relevant exchange rates are derived as opposed to all possible combinations. |
RateAI Users with the Rules Engine Support feature flag enabled |
7.a. |
RateAI bug fix - Segment currency |
This is a bug fix addressing the issue that segment currency is not correctly getting referred to other rate fields in the same segment. Resolution of an issue that affected the accurate referencing of segment currency for other fields in the same segment. The system now considers the use of 2-3 headers above the predicted headers from the shipper file for segment prediction during the mapping process. |
RateAI Users |
7.b. |
RateAI bug fix - Incorrect dropdown value updates |
This is a bug fix related to incorrect dropdown value updates during internal imports and the appearance of blank pages when applying Blackout/Gray-out rules. We have identified and fixed the issue where wrong dropdown values were being updated to the PI table after internal imports. Additionally, applying Blackout/Gray-out rules was causing blank pages to appear. Users will also no longer encounter blank pages when utilizing Blackout/Gray-out rules with this fix. | RateAI Users |
7.c. | RateAI bug fix - Some mapping getting stuck | This is a fix for a bug that impacted the mapping and file uploads. For a specific file, users were encountering issues where file uploads would become stuck during the process, and the overall mapping and upload performance was notably slow. This issue has been effectively resolved and addressed now. | RateAI Users |
7.d. | RateAI bug fix - Shipper Blackout not being identified | We have resolved the bug related to shipper blackout cells not being accurately identified for specific files. The issue was caused by an inconsistency in background color representation, where the 'WHITE' and 'BLACK' colors were not functioning as expected due to system color-dependant cell behavior. The issue is addressed by handling these cells based on their actual background color, ensuring proper identification of shipper blackout cells | RateAI Users with 'Shipper-Blackout' flag enabled |
8 | RateAI bug fix - Business Rules |
Ensure that for business rules, the currency and numeral fields have a decimal precision of 2 digits. Currently, for any calculations on fields involving numbers or currency in the business rules, we don’t limit the number of decimal points. The feature is aimed at limiting the decimal precision to 2 digits. |
Readily available for all Customers using Business Rules (RateAI) |
9 |
Type-ahead with dropdown for single and multi select dropdown fields in record layouts |
The dropdown fields within a record can be edited. Instead of the current slide-out method used to display dropdown options, this new feature introduces a type-ahead field that presents the available options directly within the dropdown interface, thus replacing the slide-out approach. This new type-ahead feature for dropdowns will be accessible across all active record layouts.
|
All Users - Contact Winmore Customer Service to take advantage of this enhancement, if desired |
Further to point #5, we describe the steps to Configure the Exchange Rate Enrichment (for Admin Users only):
- After logging in to the application go to Studio → Extensions then find from the listed extensions the lanetix/rules-engine extension.
- Click on the New link
- Enter a unique name for the script (e.g. Exchange Rate Rule Engine)
- Select the parent record type (Bid/Tender) as the record.
- Configure the script with the proper parameter values based on the sample config provided below.
- Configure the extension button in the parent record layout/workflow tasks.
Sample Configuration:
{
"conditions": [
{
"functionName": "exchangeRate",
"targetRecordType": "exchange_rate"
}
],
"record": "parent_record_type"
}
Comments
0 comments
Article is closed for comments.