2.5.3.2059 What's New

2.5.3.20259 What's New PDF

1. Introduction
This topic has information about new features and functionality in Prism 2.5.3.2059.

2. New Client

• 2.1 View/Edit Customer Details at POS
• 2.2 Disbursements
• 2.3 EFT - Adyen Cloud Terminal API Integration
• 2.4 EFT - "Access Plugin Config" permission in Legacy Client
• 2.5 General System - User Session Details via Help Button
• 2.6 General System - Improved Grids
• 2.7 General System - Set Location (Multi Store)
• 2.8 Send Sale
• 2.9 Wishlists
• 2.10 X-Out Reports
• 2.11 Z-Out Reports

3. Legacy Client

• 3.1 Database - Oracle Patch Installer
• 3.2 Database - Clean up Central Gift Card Rollback Tables
• 3.3 Data Import - MAX_INVENTORY_LOOKUPCACHE_CNT
• 3.4 General System - Standardize Monetary and Quantity Values
• 3.5 General System - Grid Formats (Legacy) preferences
• 3.6 Inventory - Base and Comparison Price on Price Tags
• 3.7 Inventory - On-Hand Qty is now Future On-Hand Qty
• 3.8 PI - Display Ext. Cost of PI Scanned Qty, Discrepancy Qty
• 3.9 POS - Filter Transaction Lookup by Cashier, Associate
• 3.10 POS - Show/Hide Transaction Lookup Filters
• 3.11 POS - Tender and Card Discounts
• 3,12 POS - "Edit Customer Details on Finalized Transaction" permission
• 3.13 Purchasing - Default Bill To store for Purchase Orders
• 3.14 Receiving - Allow Reference POs on Voucher Items
• 3.15 Replication - Prevent Excessive Replication of POs, TOs
• 3.16 Services - USEMEMORYCACHE in PrismLogging.ini
• 3.17 Tech Tookit - Clear Redis Cache    
• 3.18 Tech Toolkit - Auto Update Event Logs and Alerts
• 3.19 Tech Toolkit - Disable Audit

4. API Methods

• ClearCache
• GetRefPOsOnVoucher
• GetVouchersRefOnPO
• CleanUpCentralGiftCardRB

5. Database Table Changes

• CUSTOMER_WISH_LIST table added
• New TYPE value added to TENDER table
• PO_NO, PO_SID for Voucher Items, MULTI_PO_REF for Vouchers
• Tables to support new improved grids

2. New Client
2.1 View/Edit Customer Details at POS
DevTrack ID#30346
Users can view/edit customer information on a transaction (in progress or updated). This enables Associates at POS to verify and update address, phone, email and other customer information. 
1.    Use Customer Lookup to enter the customer on the transaction.
2.    Press the "Details" button (Customer Lookup tab).
Transaction form (Customer Lookup tab):
 
3.    Customer details (read-only) are displayed (pulled from server). To edit customer information, press the Customer Module button. 
  
4.    The customer record is displayed. Edit as needed and save the changes.
5.    Click the red ‘X' to close the customer record. 
6.    Click the red arrow to exit customer details and return to the transaction.

Notes

• Edits to the customer record are applied to the current and future transactions. Edits are NOT applied to previous transactions.
• If a customer is added through lookup and then customer details are modified, that value is only saved to the document, not to the customer.
• When a customer is added through lookup, the sid is added as the bt_cuid. The customer name in the lookup value only displays if a customer sid is present in the bt_cuid field of the document. This is the true Bill To Customer that any discounts or price levels are derived from. Otherwise, customer name will be blank. 
• If there is no customer on the document, the data may be populated by customer data entered into tender-requirement inputs in the tender modal.
• A user may also just add customer information directly to the document without adding a customer through lookup..

2.2 Disbursements
DevTrack ID#29962
Disbursements, which enable merchants to record a variety of cash drawer actions, are now available in the new client:

Disbursement Type	Notes
Cash Drop	Cash removed from the drawer to a safe or to the bank for deposit
Paid In	Cash received from other sources than normal sales (e.g. money found on the floor).
Paid Out	Cash paid out for miscellaneous expenses (e.g., lunch) and fees.
Drawer Open	Manual opening of a cash drawer (i.e., not triggered by receipt printer). This disbursement type is only available if a cash drawer is connected and correctly configured.

New Disbursement
Press the Disbursements button on the Retail Pro menu. 
Press the Add button. 
Select a disbursement type. (Note: The Open Drawer disbursement type is only available if a cash drawer is connected and configured.) 

 

On the Disbursement screen, the Cashier is set to the currently logged-in user. Change if needed.
Press the Add Tender button.
Select a Currency. 
Type the Amount. 
If the selected currency is a foreign currency, the Amount is converted to the Base Currency Value.
 
Press Print/Update or Update Only.

2.3 EFT - Adyen Cloud Terminal API Integration
DevTrack ID #29721

Adyen Plugin users can now choose from two API integration methods for connecting with PED devices: Local Terminal API or Cloud Terminal API. Each is explained below:
Local Terminal API:

• This is the API Prism has used for the legacy client Adyen Plugins and the new client prior to 2.5.3.
• Payment requests are made directly to the PED's IP Address. Requests are encrypted using the Key Identifier, Key Passphrase, and Key Version defined in the Adyen Portal. 
• The Prism Workstation must have network connection directly to the PED and the PED must have an internet connection.

Cloud Terminal API:

• This integration method is newly available in Prism's Adyen Plugin for the New Client in 2.5.3.
• The Prism Workstation AND the PED must both have internet access, but the PED can be on a separate network than the Workstation.
• Payment requests are encrypted via SSL, so the key passphrase and manual encryption/ decryption are no longer needed. Instead of using ‘Username/Password' for authentication, the Cloud API uses an API Key.
• Adyen Provides Documentation for how to generate API Keys here: https://docs.adyen.com/development-resources/api-credentials/.
• You must specify the Adyen Cloud Server you are using.
• The user must give the API credential the following role (at minimum): "Cloud Device Api role."

Log out, Log back in after configuration changes
After making any changes to the Adyen configuration, log out of the Prism app, then log back in.
Adyen Configuration Screen UI Changes
The Adyen Configuration screen now includes an API Configuration section. In the Integration Mode field, select Cloud or Local. When using the cloud integration method, the configuration screen includes a field for entering the required API key.
Note: This information is current at time of release; however, it is subject to change by Adyen.
Adyen Configuration screen (Cloud integration mode):

2.4 EFT - "Access Plugin Config" permission in Legacy Client
DevTrack ID#29705
The PLUGINS - ACCESS PLUGIN CONFIGURATION permission (Store Operations > Employees > Group Management) controls the ability of users to access the EFT Plugin configuration screens in the Prism app/new client. 
This permission is enforced whenever a user clicks any of the EFT configuration buttons (Adyen, Genius, Nayax) in the new client. 

2.5 General System - User Session Details via Help Button
DevTrack ID #29722
Prism App users can easily access user session information via the Help button. The session information includes Controller, Subsidiary, Store and workstation information as well as preference settings.
Having easy access to user session details is useful for technicians during troubleshooting. For example, when troubleshooting Android devices technicians would previously have to plug the Android device into a machine with Android Debug Bridge (ADB) installed to view session details. 
Display User Session Details
Press the Help button on the top toolbar.
 
Tap the User Session tab. 
User session details:

Option	Notes
Session	Base Currency, Country, Server, Subsidiary, Store, Workstation and other information.
Preferences	Information about current preference settings.
Permissions	List of permissions and whether each permission is set to ALLOW or DENY.
License Info	Licensing information for this node. Last Sync Date, Max Sites and Seats.

2.6 General System - Improved Grids
[#29749 to #29816]
The Prism new client now includes high-performance, feature-rich, customizable data grids. This section has an overview of the key features of the new grids.
Reference: See the Prism App User Guide for information about using the new grids to search for and view records.
Key features:

• Quick Filter
• Advanced Filter ("Search By")
• Column Filter
• Auto Filter
• Set Location (change sub/store)
• Add/remove columns
• Adjust column width
• Reposition columns
• Replication
• Security:

Sample grid (transactions):

POS Item Grids

• The POS item grids in the New Client have been modernized. 
• Items are displayed on white cards with black text and grey buttons.
• Qty and Price are now buttons instead of Input fields. Pressing these brings up a field the user can then type in.
• Serial and Lot numbers are now displayed in the center of Serial and Lot Number items rather than the bottom.
• Item Type is now displayed in brackets to the left of Description1 of the item. (O) for all order types, (S) for sale items, (R) for returns, (V) for voids.
• Item Details can now be accessed by clicking the text on an item at POS.
• The Item's width scales with the window size and/or screen size.

 2.7 Set Location (Multi-Store)
DevTrack ID#29194
You can change subsidiary/store in Customer Lookup, Transaction Lookup and Disbursements. When you do, the subsidiary/store are changed until logout. When the same user logs back in, the New Client will return to the location set in the Legacy Client Admin Console for that New Client install.
Press the gear icon. Select "Set Location."
 
Select a Store (or Sub and Store).
Save the changes.

2.8 POS - Send Sale
DevTrack ID #29193
Users can now create and fulfill send sale transactions in the new client. A send sale enables a customer to pay for an item at one location (Selling Store) and pick up the item at a different location (Fulfilling Store). A common use case is when an item is unavailable at the store where the customer is currently shopping but is available at a different store. The user pays for item (s) at the selling store and picks up the items at the fulfilling store (or arranges shipping). 
Note: Currently, closing a Send Sale is only available at the Fulfilment Store.
Server Address Requirement:
Only stores that have a hostname (or IP Address) in the Server Address field of the Store record are available for selection when doing a Send Sale. The server address used for Send Sale and the server address used for data replication (Connection Manager) must follow the same address resolution pattern — meaning either both should use IP Address or both should use hostname. We recommend using hostname.

New Send Sale
List the item(s) and customer (customer required).
Select the item.
Select Send Sale from the Item Menu.
 
Select a fulfillment store.
 
Save the record and tender the transaction. The take amount will become an order deposit used to tender and close the order at the fulfillment store. 

Fulfill Send Sale
Use Transaction Lookup to find and display the order. 
Select Fulfill on the Transaction Menu.
 
Adjust the Fill Qty. (The Filled checkbox will update when all quantities for the order are met.)
 
The available deposit amount is shown.
 
A prompt asks if you want to close the filled order.
Press the check mark.

2.9 POS - Wishlists
DevTrack ID#30036
A wishlist is a list of desired items that a customer or the customer's family and friends can reference when making a purchase.
This can be:

• Items that a customer likes but is not ready to buy yet.
• Gift ideas to share with loved ones ahead of a birthday, holiday or other life event (to avoid unneeded or unwanted gifts).

Associates at POS can easily access and select items from a wishlist. Selling an item from a wishlist reduces the item quantity on the wishlist. 
Differences between a Wishlist and a Registry Order
The Wishlist feature is similar to the "registry order" feature in legacy Retail Pro 8 and 9 but with more flexibility.

• A wishlist is not a specific order type like a registry; a wishlist is simply a saved list of items for a specific customer. 
• Registries are typically used for specific life events, like weddings and baby showers. Wishlists can also be used for life events but can be used for other purposes as well.

Limitations
Decimal quantity items cannot be added to a wishlist.

Permissions

Permission	Notes
CUSTOMERS - ACCESS WISHLISTS	Allows access to wishlists.
CUSTOMERS - MANAGE WISHLISTS	Allows management of wishlists (create, edit, delete).

New Wishlist
Find and display the desired customer record.
Press the Wishlist button (top of screen). 
 
Press New Wishlist.
 
Enter a name for the Wishlist (maximum 30 characters).
 
Use Item Lookup to search for and add items to the wishlist. 
Save the wishlist.

Add Wishlist Items to Transaction
Start a new transaction.
On the Transaction Menu, press "Add Items from Wishlist."
 
A modal displays options for finding the desired wishlist.
If a customer is entered on the document, press Use Document Customer.
Otherwise, use Customer Lookup to find and select a customer, or scan a QR Code.
 
Select the desired wishlist.
The Qty and Doc Qty of each wishlist item is listed.
The default Doc Qty is "1." Click the Qty button to adjust the Doc Qty.
Click Add to add the item to the transaction.

Click the red X to close the screen and return to the transaction. 
Transaction with item added from wishlist:
 
Tender the transaction and update.
When you update the transaction, the wishlist item quantity is reduced.

Print Wishlist using "Customer Wish List" Design
When you print a wishlist using the default "Customer Wish List" print design, the printout will include a QR Code element that makes it easy to look up a wishlist at POS.
New Client - QR Code Lookup
When the user prints a wishlist using the"Customer Wish List" print design, the Customer SID and Wish List Name are embedded in the QR Code. 
When looking up a wishlist at POS, the user can choose the "Scan QR Code" option and scan the code (requires QR code scanner). Prism uses the Customer SID and Wish List Name embedded within the QR code to display the correct wishlist.

2.10 Reports - X-Out Reports
DevTrack ID #29941
Select X-Out from the Retail Pro menu.

The X-Out filter screen has options for setting a date range, filtering by Subsidiary, Installation (controller), Store, Workstation, or Cashier.
Adjust the filter settings as needed.
Press the Print button. If you need to save an X-Out report, you can save the printed copy as a PDF.

X-Out Report filter with Print button enabled:

Save Defaults
Press Save Defaults to save the current settings as the default. The next time you launch X-Out, the settings will be entered.

Revert Defaults
If you have made changes to the X-Out filter settings and want to return the filter to its original default settings, press Revert Defaults.  

2.11 Reports - Z-Out Reports 
DevTrack ID #29256, 29890
Z-Out reports record each day's sales totals and any over/short amounts. Users enter counts of currency and verify non-currency tenders (e.g., signed credit card receipts and checks). When the report is reconciled, Prism compares the user-entered amounts with the amounts recorded by the system and notes any over/short amounts. 
Configure Z-Out reports in the legacy client (Admin Console > Node Preferences > Reporting > General). 
Select Z-Out from the Retail Pro menu.
 
When counting each currency, users can enter a Total Amount or enter counts for individual denominations.
Sample Count Currencies screen:
  
Non-currency tenders (credit card, debit card, check, etc.) must be matched; however, you can configure legacy client preferences to "Auto Match" non-currency tenders.

The Reconciliation screen shows the total over/short amount.

Replication of Grid Layouts
Use the following resources to replicate grid data:

resource	Notes
uiarea	Replicates the UI_AREA table. The UI_AREA table stores a list of UI areas (e.g., Point of Sale, Customers, X-Out, Z-Out, Promotions) and the sort order for each.
uicomponent	Replicates the UI_COMPONENT table. The UI_COMPONENT table stores a list of UI component names (e.g., Nayax, Genius, Adyen) and each component's configuration
uilayout	Replicates the UI_LAYOUT table. The UI_LAYOUT table stores a list of layout names.
uilayoutpage	Replicates the UI_LAYOUT_PAGE table. The UI_LAYOUT_PAGE table references the UI_AREA, UI_LAYOUT, and UI_PAGE tables.
uipage	Replicates the UI_PAGE table. The UI_PAGE table stores page configuration and references the UI_AREA table

NEW CLIENT - MANAGE GRID LAYOUTS permission
Merchants can control the ability to work with grid layouts via the NEW CLIENT - MANAGE GRID LAYOUTS permission. To add, edit, or delete grid layouts, users must belong to a group with the NEW CLIENT - MANAGE GRID LAYOUTS permission.

3. Legacy Client

3.1 Database - Oracle Patch Installer
DevTrack ID#29836
Use the Retail Pro Oracle Patch Installer to apply patches to Prism and Retail Pro 9 Oracle databases. This installer will install the 64-bit DB Bundle Patches as well as the 64-bit Oracle OPatch utility for the Oracle 12c or Oracle 19c database. 
This patch installer replaces previous patch installers.
This installer expands and improves the original Prism Oracle 12c patch installer by:

• Now supporting both 12c and 19c Bundle Patch installations.
• Adding the ability to install an OPatch update file, which previously had to be done manually prior to installing a DB patch when a new OPatch version was required for the new DB patch installation.
• Configuring itself for 19c or 12c based on system data gathered at startup, with no action needed by the user to choose the database version.

Oracle Database Patch Installer UI (19c):
 
Reference: See the Retail Pro Oracle Patch Installer topic 

3.2 Database - Clean up Central Gift Card Rollback Tables
DevTrack ID #29278

An API call (CleanUpCentralGiftCardRB) has been added to clear orphaned Central Gift Cards from the rollback tables (central_gift_card_txn_rb, central_gift_card_rb) when the transactions are older than 48 hours.
On the system acting as the Centrals Server, create a Tech Toolkit Scheduler task to execute the call.
Action End Point (URL): 
http:///api/common?action=CleanUpCentralGiftCardRB
Action Payload:
   {"data":[{} ]}

This POST action will return a succes response as follows:
{
    "name": "cleanupcentralgiftcardrb",
    "metatype": "Action",
    "comment": "Clean Up Central Gift Card RollBack tables",
    "translationid": null,
    "errors": null,
    "data": [
        {
            "status": 0,
            "errmsg": null
        }
    ]
}
Check Pending Transactions
Before using the "CleanUpCentralGiftCardRB" API method, check Pending Transactions. If there are any Pending Transactions with central gift card tenders that you can handle via Pending Transactions, that is the preferred method. For example, you can update the transaction or delete the central gift card tenders and cancel the transaction. 
Transactions less than 48 hours old are preserved
As part of the changes for #29278, the system will not delete an uncompleted transaction unless it is greater than 48 hours old. This ensures no records are deleted for a transaction in progress. 

3.3 Data Import - MAX_INVENTORY_LOOKUP_CACHE_CNT
DevTrack ID #30156
A new setting for the Tech Toolkit service helps prevent 'out-of- memory' errors during data import. Previously import relied solely on caching for speed, but now there is a setting in the PrismTechToolkit.ini to limit how much can be cached (to prevent an out of memory condition). The default value for MAX_INVENTORY_LOOKUPCACHE_CNT=7000000 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. [Data Import]
MAX_INVENTORY_LOOKUPCACHE_CNT=7000000
IN_PROGRESS=false

3.4 Grid Formats (Legacy)
This release includes changes to Grid Formats preferences that allow users to define grids for both the legacy and new client.
The old GRID FORMATS preferences have been renamed GRID FORMATS (Legacy) in Admin Console > Node Preferences.
GRID FORMATS has been changed to set default grid layout formats for lookups in the new client.
This enables merchants to select which saved layout will be the default grid layout for each lookup area in the new client. You can set the preference at the desired level (Subsidiary, Store, Workstation).
Navigate to Admin Console > Node Preferences > Grid Formats. 
Select a saved layout from the dropdown for individual areas as needed.
Save the changes.
Notes:

• Only layouts defined and "saved to file" in the new client are available for selection.
• The grid layouts are specific to each area. For example, you 
• The "Default" selection in the dropdown refers to the new client default layouts.

3.5 General System - Standardization of Monetary, Quantity Values
DevTrack ID #29986, 29989, 29993
This release includes code changes that standardize the handling of monetary and quantity values in Prism. These changes give merchants clear upper boundaries for item price, cost, quantity and other key values. 
Monetary Values - Maximum 99,999,999.9999 or NUMBER (8,4)
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, etc.) are generally allowed to be larger as long as they do not violate database limits. If a field is calculated and there are also manual changes, a manual change is limited to 8,4 but the system is allowed to calculate a higher value.
This includes:

• Tax fields on POS documents (Tax Amount and Tax 2 Amount)
• Price fields in Inventory (Price, Price with Tax)
• Cost fields in Inventory (Cost, Order Cost, Vendor List Cost)
• Currency fields

Enforced in the following areas: Inventory, POS documents, back-office documents (POs, ASNs, vouchers, TOs, slips, memos), auto tools. 

Z-Out Reports - Maximum 9,999,999,999.9999 or NUMBER (10,4)
Because of the nature of Z-Out reports and the large numbers involved, the maximum is a 10-digit whole number and 4-digit decimal (9,999,999,999.9999).

Quantity Values - Maximum 9,999,999.999 or NUMBER (7,3)
All quantity values have been configured for a maximum of a 7-digit whole number and 3-digit decimal (9,999,999.999). In addition, Company Qty cannot exceed a 7-digit whole number.
Enforced in the following areas: Inventory, POS documents, back-office documents (POs, ASNs, vouchers, TOs, slips, memos), auto tools.

No of Decimals Displayed in UI  - Max 4
In Admin Console > Node Preferences > Language & Locale, users can define the number of decimals for various settings. This preference determines the number of decimals displayed in the UI and that are available for data entry, NOT the number of decimals stored in the database. As part of the changes for this CCU, the maximum for this preference is 4. 
If you previously entered a value greater than 4 for this preference, the old value (e.g. tax decimals = 6) will continue to be consumed by the system but may generate unexpected problems. We recommend that you manually change the preference to a maximum of 4.
Node Preferences > Language & Locale > Numbers & Currency: No of Decimals:
 

Decimal Type	Notes
Tax	The number of digits that will be displayed to the right of the decimal point when displaying item tax amounts. (total tax amounts follow the "Price" setting)
Price	The number of digits that will be displayed to the right of the decimal point when displaying item prices and values expressed as amounts. This includes Fee Amount, Shipping Amount, and SPIF. In addition, total tax amounts follow this setting.
Cost	The number of digits that will be displayed to the right of the decimal point when displaying cost amounts.
Number	The number of digits that will be displayed to the right of the decimal point when displaying quantity and non-monetary values (e.g., Discount %, Margin %).
Currency	The number of digits that will be displayed to the right of the decimal point when displaying currency amounts on the Tender screen and on X-Out and Z-Out reports.

Item Quantity Decimal Display
For item quantity decimals, Prism will use the lower of the following:
Inventory > Item Details > Qty Decimals: [0 to 3, default=0]
Node Preferences > Language & Locale > No of Decimals: Number [0 to 4, default=2]
This means that by default, Prism will not display any item quantity decimals.  

Tax Decimal Display
When tax totals are displayed (e.g., Transaction Details), the number of tax decimals displayed follows the "No of Decimals - Price" setting; the tax amount is rounded if needed. At the item level the "No of Decimals - Tax" setting is followed.
Example - Base Currency US Dollar
In Admin Console > Node Preferences > Language & Locale, the number of Price Decimals is set to "2," and the number of Tax Decimals is set to "4."
At the Item level, Tax Amount extends to four decimal places. You can see this in Item Details - Taxes tab.
At the transaction level, only the two most significant places are displayed. You can see this in Transaction Details - Taxes tab.

3.6 General System - Base and Comparison Price on Merchandise Tags
DevTrack ID #22191
Merchants can now print both the Base Price (e.g., MSRP) and Comparison Price (e.g., discounted price) on price tags. This enables customers to easily see the difference between the pre- and post-markdown price when looking at merchandise. 
Phase 2 (future) will extend the Base and Comparison price levels to POS  Transactions and Receipt designs.
To use this feature, you must set up price levels in Node Preferences > Merchandise > Pricing > Price Levels and then assign the price levels to the appropriate subsidiary, store, and/or workstation records. Note: If a sub/store/ws does not have a Base Price Level assigned, then the Active Price Level in Node Preferences > Merchandise > Pricing > Price Levels will be used.
Sample 2.5.3.x Subsidiary record with Base Price Level/Comparison Price Level:
 
Adding Base Price and Comparison Price to Document Designs
In Document Designer, select Merchandise Tags in the Area dropdown.
Select the desired tag type (e.g., Normal Basic).
Click Edit.  
Sample Doc Design with Active Store Base Price, Comparison Price elements highlighted: 

About the Comparison Price
The Comparison Price Level is used only for printing inventory prices. If no Comparison Price Level is assigned for a store, only the Base Price Level (or Active Price Level in preferences) will be printed even if the design includes both elements.

3.7 General System - Show/Hide Lookup Filters
DevTrack ID#29366
You can hide/show the filters in Transaction Lookup and other areas. This change enables merchants to use the entire screen area when viewing lookup results.
Click the left-pointing arrow to hide the filters.
 
Click the right-pointing arrow to show the filters.

3.8 PI - Display Extended Cost of PI Scanned Qty, Discrepancy Qty
DevTrack ID##25901
You can customize Physical Inventory document designs to display Extended Cost for Scanned Qty, Discrepancy Qty, etc.
1.   Launch Document Designer and log in.
2.   Select Physical Inventory (or Physical Inventory Zone) in the Area dropdown.
3.   Select the desired PI design and click Edit.
4.   The "COST" field is in PI_ZONE_ITEM portion of the dataset. 
5.   Add the "COST" element to the desired area of the design.
6.   Double-click the element to display a text editor. Add the appropriate text. Click OK to save.
Below are usage examples:
Cost of scanned:
[FormatCost(*)]
Cost of discrepancies: 
[FormatCost(*)]
Click OK to save the changes.
Document Designer text editor:

 3.9 POS - Filter Transaction Lookup by Cashier, Associate
DevTrack ID#28427
Cashier and Associate are available filter elements in Transaction Lookup. This enables users to easily filter and sort transactions by these fields. 
Cashier and Associate added to Transaction Lookup filter:

3.10 Show/Hide Transaction Filters
You can hide/show the filters in Transaction Lookup. This change enables merchants to use the entire screen area when viewing lookup results. This functionality was previously available only in Inventory Item Lookup.

• Click the left-pointing arrow to hide the filters. 
• Click the right-pointing arrow to show the filters.

3.11 POS - Tender and Card Discounts
DevTrack ID#28828

The Tender Discount feature enables merchants to define discounts for:

• Specific tenders (e.g., Cash)
• Specific credit card types (e.g., cards issues by a certain bank or institution)

A common use case for this feature is to offer a discount for paying cash or for using the merchant's preferred card.
Limitations

• Not compatible with Nayax EFT.
• Not compatible with Accounting Link.
• Not compatible with foreign currency; Base currency only.
• Over-tenders are prevented. The maximum allowed take amount is the amount due.
• Cannot spread tender and card discounts.

Configuration
For tenders, define a Discount Percentage in Admin Console > Node Preferences > Transactions > Tenders > Requirements. You can define a Discount % for each tender type EXCEPT credit cards.
Node Preferences > Transactions > Tenders > Requirements

For credit cards, define a Discount % for individual card types in Node Preferences > Transactions > Tenders > EFT.
For returns, Tender discount refunds work only when the preference "Restrict return tenders to original sale tenders" is turned ON. This preference is in Admin Console > Node Preferences > Transactions > General.

POS - Main Tender and Discount Tender Records
On a POS transaction, if the taken tender or card has a discount %, the discount is applied and two tenders are listed: the main tender and the discount tender.
Sample Tender screen with discount tender:
 
Using a Tender (or Card) Discount for Partial Payment (Split Tender)
It may be the case that the customer only wants to pay for part of the total using the preferred tender (or card). For example, the customer may have available store credit or soon-to-expire loyalty points. Or maybe the discount tender can only be used up to a certain amount. In these cases, the tender discount amount is proportional to the Take Amount.

Returns
Tender discount refunds work only when the preference "Restrict return tenders to original sale tenders" is turned ON.
On the return, only the actual tendered amount is returned, not the tender discount amount.

Tender Discount Notes

• Transaction tender discount will subtract from Total.
• Transaction tender discounts will not reduce tax amounts.
• Referenced return of items will return original tenders with associated tender discounts.
• Removing tenders will remove associated tender discounts.
• Tender discounts will affect order items.

3.12 POS - EDIT CUSTOMER DETAILS ON FINALIZED TRANSACTION permission
DevTrack ID#28628
The POS - EDIT CUSTOMER DETAILS ON FINALIZED TRANSACTION permission controls the ability to apply customer record changes to the current document. 
This permission is checked when a user makes changes to a customer record from a finalized transaction and returns to the current document. This permission is separate from the CUSTOMERS - EDIT CUSTOMER permission. This means that when working from a finalized transaction, the ability to edit customer details and the ability to apply those edits to the current document are controlled by separate permissions. (Note: Previously, the permission was called POS - EDIT FORMER CUSTOMER.)

3.13 Purchasing - Default Bill To store for Purchase Orders
DevTrack ID#27125
You can set a default Bill To Store for purchase orders via a new "Default Bill To Store" preference in Admin Console > Node Preferences > Purchasing > Purchase Orders.
Setting a default Bill To Store helps ensure the correct store is entered when a user creates a new PO. Previously, the Bill To store defaulted to the Ship To store. However, when billing runs through the HQ, this required changing the Bill To store on every PO, something that is easy for employees to forget. 
Admin Console > Node Preferences > Purchasing > Purchase Orders:

The "Default Bill To Store" preference can be enabled at the Subsidiary and Store level. All purchase orders created at that Sub/Store will default to the selected store but can be changed by users who have the PURCHASING - CHANGE STORE permission assigned.
Prism will populate the Bill To store when:

• A user manually creates a PO.
• A user generates a PO from a sales order.
• Auto Purchasing auto-generates a PO.

If the default location is unavailable (i.e., the store is set to Inactive), Prism will use the current user's session default.

3.14 Receiving - Allow Reference POs on Voucher Items
DevTrack ID #28405, 28190
The "Allow reference POs on Voucher Items" preference, when enabled, allows different voucher items to reference different purchase orders (POs). When the voucher is updated, all the referenced POs are updated. Previously, users could select items from more than one PO; however, only the PO entered in the header would be updated.
Sample Use Case
A merchant sells handmade shoes that are made abroad. An order of 15 to 20 cases of these custom shoes can take up to a year to fill. The factory makes shoes one run at a time, and it may take months for the factory to get to a given shoe type. When the merchant finally receives a shipment from the factory, it might have items from multiple purchase orders. This feature enables merchants to select which PO to reference for individual voucher items. 
Admin Console > Node Preferences > Purchasing > Vouchers:
 
Note: Default = disabled
Workflow
Start a new voucher.
In the Reference PO No field, click the Search icon and then search for and select a purchase order. Click the PO Items button. Select the items and quantities to add to this voucher. 
Alternatively, list the item by scanning or typing the UPC. Then, in the Reference PO No field, type the PO number and press .
Note: Users cannot directly edit the PO Number field in the voucher item list.
 

PO Number is appended to end of Grid
When the Allow Reference POs on Voucher Items preference is enabled, the PO Number field is appended to the end of the voucher item grid. You cannot change its position or remove it via grid formats preferences.
Adding Items via Basic or Advanced Item Lookup
Items added through Basic or Advanced Item Lookup take on the PO Number entered in the voucher header, if there is one.
Navigate between Referenced POs and Vouchers
The following UI elements have been added:

• A "Referenced PO" button has been added to the voucher user interface. Clicking the button displays a list of purchase orders referenced on the voucher. The user can select and view a purchase order from the list.
• A "Referenced Voucher" button has been added to the Purchase Order user interface. Clicking the button displays a list of vouchers that reference the PO. This enables a user to select and view a voucher that references the PO. 

Voucher with Referenced PO button:
 
Sample Referenced PO list:
 
If you click "Go to Purchase Order" (or "Go to Voucher"), you will navigate away from the current document, so a confirmation is displayed. Click Yes to proceed.

After viewing a referenced PO or voucher, click the "Back" button on the browser navigation bar to return to the original document.

3.15 Replication - Prevent Excessive Replication of POs, TOs
DevTrack ID #30132
Functionality for purchase orders (POs) and transfer orders (TOs) has been extended to prevent excessive replication of these documents. 
Cancelling a PO or TO that has already been saved will revert all changes back to the last saved state. Previously editing one of these documents triggered a replication event. Now the document is only replicated once the changes are saved. This prevents excess replication traffic.
As part of this change, POs and TOs have new flags:

• STATUS flag in PO table: Pending=0, Completed=1, Work in Progress=2
• DOC_STATUS flag in TORD table: None=0, Changed=1, Cancelled=2, Normal=3, Completed=4

When a user clicks the Edit button on a PO or TO, the document is put into the "Work in Progress" (PO) or "Changed" (TO) state. When user clicks the Save button, the document is put into "Completed" (PO) or "Normal" (TO) state. 

• If the document is in the "Work in Progress" (PO) or "Changed" (TO) state, the document won't be replicated. 
• If the document is in the "Completed" (PO and TO) or "Normal" (TO) state, the document will be replicated. 

Clicking the Cancel button will undo the current changes and restore the document to its last saved state.

3.16 Services - USEMEMORYCACHE in PrismLogging.ini
DevTrack ID#29090
USEMEMORYCACHE (PrismLogging.ini) determines whether services will use memory caching for user sessions. This is important because user session information is included in each request made by a service. The user session information determines things like permissions and preferences for the user. By default, USEMEMORYCACHE is set to True for each individual Prism service. 

• When set to True, the service will fetch user session information from the shared cache.
• When set to False, the service will ask the licensing service for a copy of the user session each time it makes a request (resulting in unnecessary overhead).

Time-to-live (TTL) for data in the shared cache is 30 minutes.

 3.17 Tech Toolkit - Clear Redis Cache
DevTrack ID#29723
Prism uses the Redis service to cache certain key data. To clear the cache, navigate to Tech Toolkit > Data Utilities and select Redis Cache Tools.
Click Clear Redis Cache to clear all cached data.

3.18 Tech Toolkit - Auto Update Event Logs and Alerts
DevTrack ID #29185
Events are now generated whenever the Auto Update process starts and when it is completed. You can also configure alerts so that users receive a message when the event occurs. This enables technicians to receive notification of successful auto updates. 
Tech Toolkit > Data Utilities > Event Logs:

3.19 Disable Audit
DevTrack ID #22863
Tech Toolkit contains a new Data Utilities tool for Prism Oracle installations. It is called Oracle DB Operations. The option to 'Disable Audit' disables Oracle database auditing (for Oracle 12c and 19c). By default, auditing is enabled when you install the Prism Oracle database. The Disable Audit feature will disable auditing by changing the Oracle ADUIT_TRAIL parameter from the default ‘db' to ‘none.'

Important! Because the process takes a long time and the user is not notified when it is finished, it is recommended that auditing be disabled at the end of the day when system use is not required.

To disable audit:
Log in to Tech Toolkit.
Select Oracle DB Operations from the Data Utilities menu. 
Press or click ‘Disable Audit.'  
When selected, after a few minutes the user will be logged out of TTK. Log in will continue to fail for some time after this point while the DB and all Prism services are restarted. 
Note: The TTK option will always show an active 'Disable Audit' button as TTK has no direct method of knowing the state of Oracle auditing. If the button is selected again the user will be logged out of TTK but can immediately log back in.

4. API Methods and Database Table Changes 
API Methods
Clearcache (#29723)
Clears the Redis cache. (This method is called when a user clicks the "Clear Redis Cache" button in Prism Tech Toolkit > Data Utilities > Redis Tools.)
Param: CachePrefix 
CachePrefix acts as a filter (case-sensitive) for the cache keys to remove, * can be added to the beginning and or end of the phrase. (Default: * which clears all)
http:///api/common?action=clearcache

GetRefPOsOnVoucher (#28190)
GetRefPOsOnVoucher accepts voucher_sid as a parameter and returns the list of all purchase orders referenced on the voucher.
http:///api/backoffice/receiving/7530592830001016136/?action=GetRefPOsOnVoucher

GetVouchersRefOnPO (#28190)
GetVouchersRefOnPO accepts a po_sid as a parameter and returns the voucher that referenced the PO. 
http:///api/backoffice/purchaseorder/752937128000125486/?action=GetVouchersRefOnPO

CleanUpCentralGiftCardRB (#29278)
Removes orphaned central gift card purchase attempts from the central_gift_card_rb and central_gift_card_txn_rb tables.
http:///api/common?action=CleanUpCentralGiftCardRB
 
Database Changes
CUSTOMER_WISH_LIST table (#30036)
The CUSTOMER_WISH_LIST table stores a wish list of items for a specific customer. 
In addition, the following wish list columns are added to the DOCUMENT_ITEM table: WISH_LIST_SID, WISH_LIST_CUST_SID, WISH_LIST_WL_NAME, INVN_ITEM_UID

New TYPE value added to TENDER table (#28828)
As part of the Tender (and Card) Discounts feature, a new value is added to the TENDER_TYPE column in the DOCUMENT table - 29=Tender discount
When a tender has a discount percentage defined, the Take Amount is split into two separate tenders: the original tender and the tender discount tender (TYPE=29).

PO_NO, PO_SID fields for Voucher Items, MULTI_PO_REF flag for Vouchers (#28405)
As part of the "Allow Reference PO on Voucher Items" feature, the PO_NO and PO_SID columns are added to the VOU_ITEM table. These columns enable different voucher items to reference different POs. The MultiPORef flag in the VOUCHER table is set to true when a voucher references multiple POs. When this flag is set, the server will process these vouchers differently and update each referenced PO.

Tables to support AG Grids
Various tables have been added to the database to support the improved grids in 2.5.3. 
UI_AREA: Stores the SORT_ORDER for individual areas.
UI_COMPONENT: Stores the CONFIG_NAME, COMPONENT_NAME, CONFIG (clob) of UI components.
UI_LAYOUT:  Stores the LAYOUT_NAME.
UI_LAYOUT_PAGE: Refers to AREA, LAYOUT, and PAGE_SID tables.
UI_PAGE: Refers to AREA table.

Status flags for POs and TOs (#30132)
As part of the changes to reduce excessive replication of purchase orders and transfer orders, the following flags are added:

• STATUS flag in PO table: Pending=0, Completed=1, Work in Progress=2, 
• DOC_STATUS flag in TORD table: None=0, Changed=1, Cancelled=2, Normal=3, Completed=4