Prism 2.5.2.1554 CCU Release Notes
Prism 2.5.2.1554 CCU Release Notes PDF
This topic includes information related to the Prism 2.5.2.1554 CCU Release.
NOTES
- Windows 10 and 11 users: Launch the Proxy using the Run as Administrator option.
- Clear the cache before trying to log in.
- Oracle 19c upgrade requires more memory and other resources than 12c. Read the RP Prism Oracle 19c Upgrade document before running the Oracle 19c upgrade.
- The Prism App (Windows and Android) performs the same functions handled by the Prism Proxy. Do not use the Prism Proxy when using the Prism App.
- Versions of MySQL 8.x up to version 8.0.34 have been verified to work with Prism. Versions of MySQL after 8.0.34 have not been verified to work with Prism.
FIXES (1 ISSUE)
The following list outlines key issues that have been addressed with this release. This list is not intended to reflect all possible fixes done during the given period, but those that are deemed important for review and specific to this release.
| Issue ID | Title/Description | Build Found | Solution |
|---|---|---|---|
| Point of Sale - Tenders | |||
| 30493 | Central Gift Cards require an expiration date | 2.5.2.1553 | Centrals Gift Cards no longer require an expiration date. |
Previously released CCUs included in this release:
2.5.2.1553
| Issue ID | Title/Description | Build Found | Solution |
|---|---|---|---|
| EFT - General | |||
| 25120 | Allow debit card refunds using tokens | 2.3 | This release adds the ability for Genius EFT users to perform Referenced Refunds (aka 'Token Refunds' or 'Refund by Reference') against Debit Cards. Previously, this was only allowed against Credit Cards. When a return references a previous Sales transaction, besides the item and any CC tender tokens, Prism will also return debit authorization tokens. Both the Credit and Debit tender buttons will show EFT tenders (credit or debit) that can be referenced if the user wants to return against the original card. |
2.5.2.1549
| Issue ID | Title/Description | Build Found | Solution |
|---|---|---|---|
| Data Migration Tool | |||
| 30156 | The INVN_SBS_ITEM sid lookup step fails, causing the import of DOCUMENT_ITEM to fail. | 2.5.2 | Imports have been enhanced to help prevent 'out-of- memory' errors. Previously import relied solely on caching for speed, but now there is a setting in the TechToolkit.ini to limit how much can be cached (to prevent an out of memory condition). The default value for MAX_INVENTORY_LOOKUPCACHE_CNT=8000000 which should be sufficient for most imports. This value can be lowered to prevent import caching from consuming too much memory. When the specified limit is reached, caching will be disabled and lookup operations will use direct SQL queries. This will prevent an out-of-memory condition but will impair import performance. |
| 30134 | FLAG_ID field length exceeded when a large number of options (UDF_VAL entries) are part of the V9-to-Prism migration. | 2.5.2.1515 | Code was changed to allow the import of a large number of Inventory UDF options. |
2.5.2.1548
| Issue ID | Title/Description | Build Found | Solution |
|---|---|---|---|
| Point of Sale - Tenders | |||
| 30088 | Subsidiary dropdown on lookups shows blank on load if current subsidiary is on second page of results | 2.5.2 | When there are a large number of subsidiaries, Prism now correctly consumes assigned subsidiaries. When changing subsidiaries, most areas have paging controls to accommodate a larger number. |
2.5.2.1538
| Issue ID | Title/Description | Build Found | Solution |
|---|---|---|---|
| General System | |||
| 29921 | AutoUpdate.exe needs to be installed by the Prism installer | 2.5.2.1513 | AutoUpdate.exe is now installed along with Prism Server. |
| Inventory | |||
| 29989 | Price in inventory allows a 10-digit number before the decimal place. | 2.5.2.1515 | All price and cost fields which allow manual data entry have been configured for a maximum of an 8-digit whole number and 4-digit decimal. Fields which are calculated by the system (e.g., ext price, total cost) are generally allowed to be larger as long as they do not violate database limits. If a field is calculated and also has manual changes, a manual change is limited to 8,4 but the system is allowed to calculate a higher value. See the "About Standardization of Monetary, Quantity Values" note. |
| 29987 | UDF values disappear from item after editing style-level attributes on a sibling item.Value too large error when adding items to POs, slips or vouchers when using VAT and the price is 9 digits or more. | 2.5.2.1515 | Now Prism only sends edited invn_extend records in the style save payload. If the user changes these UDFs on the style edit field, it will overwrite the items. Changing values in the style grid will no longer cause UDFs to be overwritten for style items. |
| 29986 | Item price with tax cannot be set above 9,999,999. | 2.5.2.1515 | See the Solution notes for #29989 |
| Purchasing | |||
| 29993 |
Value too large error when adding items to POs, slips or vouchers when using VAT and the price is 9 digits or more. |
2.5.2.1515 | See the Solution notes for #29989 |
| 29659 | PO and voucher cost is rounding to 4 decimals when set to use 6 decimals. | 2.5.1.22 | Due to system constraints, Node Preferences > Language & Locale: 'No of Decimals' will be limited to 4. If you previously entered a value greater than 4 for this preference (e.g. tax decimals = 6), Prism will continue to consume the old setting; however, there may be unexpected problems. We recommend that you manually change the preference to a maximum of 4 decimal places for each category. |