Updated: September 9, 2022 7:21am What's New

The following new features and functionality were added in Prism

Feature Description
Apache Upgrade

This is a reference to the required upgrade of Apache from 2.4.12 to 2.4.25, required for the 1.9.5. release. A more recent upgrade to Apache 2.4.27 is required for Prism 1.12

Required 9.40 version error message DevTrack ID#11768
When attempting to install DRS over any V9 version older than, the user will see a message informing that "Retail Pro v9 is not sufficiently current to support Prism DRS. Recommended version is 9.40 or newer." This new prompt helps avoid confusion about why the Prism installation is failing
Option to not display merchandise images

DevTrack ID#13211
This release includes a new "None" option for the Display Merchandise Images preference. Each time an item with an assigned image is entered on a transaction, it adds a certain amount of overhead to the transaction because the image file must be fetched from the server. When "None" is selected, Prism will skip image file requests, helping to improve performance.

Tender Rounding

DevTrack ID #12675
This release of Prism includes the ability to round tenders. Tender rounding enables retailers to automatically round amounts up or down, based on the desired multiple (e.g. 0.05, 0.1, or 1.0). The ability to round tenders is especially important in places such as Australia and New Zealand where pennies are not used. In these types of environments, although the item prices are typically already rounded to the proper multiple, it is possible for a discount, decimal quantity item, or other POS event to produce a total that is not a multiple of the lowest denomination. The tender rounding feature ensures that these amounts are rounded up or down to the desired multiple.  In addition, retailers can selectively enable/disable rounding for individual tenders. Tender rounding can be set at the Corp, SBS and, or store level.

Transaction Lookup by Date Type

DevTrack ID# 11738
The Transaction Lookup dialog enables retailers to find specific transactions by searching using a variety of criteria, including date range. Beginning with this release, the Transaction Lookup dialog includes a Date Type dropdown that enables users to select a specific date field to use for the date range filter. The user's Date Type selection is applied to the date range specified in the From Date/To Date filter. The available selections for the Date Type dropdown are:

  • Created Date (default)
  • Ordered Date
  • Ship Date
  • Cancel Date


Access Pending Transaction permission

DevTrack ID #12677
Beginning with this release, Prism includes a security permission that controls the ability of employees to access the Pending Transactions area. Pending transactions are those transactions that were exited before completion (e.g. when the browser is closed unexpectedly), or that were placed on hold. Users go into Pending Transactions to either complete or discard a transaction.
Previously, a permission to control users' ability to discard a document was available, but this new permission provides retailers with even tighter control and security. Now, only managers or other authorized users will be able to access the Pending Transactions area.

Prompt to enter decimal quantity

DevTrack ID #12378
Beginning with this release, when a user lists a decimal-quantity item on a document, a prompt will be displayed so the user can enter the desired decimal quantity for the document. Previously, the user would have to list the item and then go into Item Details to specify the desired quantity. The number of decimals available is based on the value of the Qty Decimals field in the item record in Inventory. The default quantity is 1. The prompt will display the number of decimal places configured in preferences (Preferences & Settings > Regional Settings). Enter the desired quantity in the dialog.
Note: The Enter Quantity dialog is only displayed for decimal quantity items.

Require customer for manual discounts

DevTrack ID#12162
This release includes a new preference that enables retailers to require a customer be entered on a transaction in order to apply a manual discount. To access the preference, go to the Admin Console, select Preferences & Settings > Transactions > General. The preference is titled "Require Customer for Manual Discounts". When enabled, manual discounts will be prevented if a customer is not entered on the transaction. The preference does not affect any system generated discounts; this requirement is only in effect when the preference is enabled and there are manual discounts.
This preference is especially useful for retailers who have transactions that include customers as well as transactions that don't include customers. By selecting the preferences, retailers can be sure that any manual discounts can be directly tied to a specific customer. This can help to prevent fraudulent discounts given by employees.


Item Details in Advanced Item Lookup

DevTrack ID #8243
Beginning with this release, the Advanced Item Lookup screen includes an Item Details button. Including the Item Details button on the lookup screen enables users to check item-level information before adding an item to a document.  For example, a user might want to check user-defined fields to verify the item is the desired item. When using Advanced Item Lookup, highlight an item in the search results, and then click the Item Details button for the selected item.


Edit Item Qty UI change This release includes a change in how users modify the item quantity of individual items on the main transaction form. . Previously, the interface included separate Qty + and Qty - buttons for adding or decreasing the selected item's quantity. Now, users will see a single button labeled "Quantity". When a user selects an item and clicks the Quantity button, a text box is enabled for entering the desired quantity for the item. Clicking the buttons would increase or decrease the previously to enter a quantity of 10, a user would have to navigate to Item Details or click the Plus button repeatedly. Now, the user can simply click the Quantity button and type "10" or whatever the desired quantity is. By default, items are listed with a quantity of one.
Price+VAT in item display fields

DevTrack ID#13784
Beginning with this release, when looking up items on a transaction, the Item Lookup screen that displays the search results now includes the Price (Price + Tax) field. This change makes it easier for Associates to select the correct item for the transaction. Previously, the item information on the Item Lookup screen did not include Price. The Item Lookup screen is displayed when a user types item lookup information on a transaction and the search results include multiple items.


OPOS Printer support

DevTrack ID #1954, 13627
This release includes support for OPOS (Object Linking and Embedding for Retail POS) printers. OPOS is a point of sale device standard for Microsoft Windows operating systems. Previously, OPOS printers were not supported with RP Prism. As part of this change, RPI has created new document designs that are specially designed for printing on OPOS printers. Users can configure OPOS printers using the same basic steps as with other printers.


B+S Receipt Designs

DevTrack ID#13503
This release includes changes to B+S EFT Plugin receipt designs that make it easier for users to configure receipt designs. B+S receipt designs now include special text block fields (EFTDataBSCust for the customer copy, EFTDataBSMer for the merchant copy) instead of individual EFT fields. Each text block field holds all the required EFT fields (EFTData0-EFTData9) that are returned to the Verifone VX-20 during authorization. As long as the text block fields are included in the design, retailers can be sure that all the required EFT fields will be included in the printed document. The predefined receipt designs for B+S have been updated to include these new text block fields.

Original store information on document designs DevTrack ID #13527
You can add original store information to document designs, if desired. Including the original store information enables retailers to know where the original transaction occurred and can make it easier to verify the return. The following fields are available for doc designs: orig_document_number, orig_store_number, orig_subsidiary_number.
Clearing the Visible Flag
You can clear the visible flag for these fields so that they are not visible on the printed document. These fields are only populated for return items that reference an original receipt
Email default designs

DevTrack ID#13600
Beginning with this release, Prism users can select separate print and email designs when printing/emailing documents. In addition, you can assign a default email design for individual document types in Prism preferences. This change enables retailers to use designs optimized for email when emailing receipts and other documents.

Z-Out Open Register for iOS devices

DevTrack ID#12720
This release includes a new limited Open Register functionality for iOS smartphone users who use the Portrait layout. This enables iOS smartphone users to use structured Z-Out reports, which require both register open and register close. Previously, the Portrait layout made it difficult to open a register, so users were restricted to using unstructured reports, which only require a close.

View Order Dates

DevTrack ID #11738
When working with orders (via the Order Details button), users can now click an Order Dates button to display a pop-up showing each date field associated with the order:

  • Ordered Date: "Ordered Date" is automatically populated with the current date/time when the document is created.  The value is editable.
  • Ship Date: "Ship Date" is null by default and can be edited.
  • Cancel Date: "Cancel Date" is null by default and can be edited.
Choose tender when returning order deposits

DevTrack ID #11739
Beginning with this release, when closing an order, Associates can choose the tender to use for the return. Previously, when closing an order, the unused deposit amount was automatically credited to the customer's Store Credit balance. This change gives retailers greater flexibility when it comes to handling unused deposits on closed orders. For example, if a customer cancels the order in person at a store, the retailer could choose to issue a cash refund.

Customer UDF6-15

DevTrack ID#12643
Beginning with this release, the Customer Search grid can include Customer UDF6 through Customer UDF 15 fields. These user-defined fields enable retailers to create custom fields for storing whatever customer information the retailer desires. Previously only the Customer UDF 1 through Customer UDF 5 fields were available in the Customer Search grid. In the Prism Admin Console, select Preferences & Settings > Grid Formats. Select Customer Search in the "Select a grid to configure" dropdown. Scroll down to the UDF fields and move the desired UDF fields from the Available list to the Selected list. Save the changes. You can define separate grid format options for Allow Search By and Show Columns. The Allow Search By selections determine which fields can be used to enter search criteria when looking up customers. The Show Columns determine which columns can be included in the Search Results display.

Individual Card Types on Z-Out Reports

DevTrack ID #12298
Beginning with this release, Z-Out reports include the Card Type field. Including this field on Z-Out reports provides greater details for retailers and enables them to reconcile a drawer by credit card type. To see the breakdown by card type, use Z-Out Lookup to find the report. Select the report in the list and then click the Print button. In the Print dialog, select a print design if necessary and then click the Preview button. Scroll down to the All Card section. Immediately following the All Cards section is a breakdown of sales by each card type taken during the report period.

Tax Rule, Tax Code added to Tax prefs

Prism has a limited set of Tax Area settings. Beginning with this release, the Tax Rules table in Taxes > Tax Areas preferences includes the following additional details:
Rule Name: The Rule Name column lists each tax rule defined for the selected Tax Area. The actual tax rate for the rule is not displayed in Prism. Tax rates for individual tax rules are defined in Retail Pro 9 Preferences (Local Preferences > Taxes > General).
Tax Code: Each tax rule is only applied to items that are assigned the tax code for the rule. Items that are assigned the specified Tax Code will be charged the tax rate assigned to the tax rule.
Previously, the Tax Rules table only had the VAT Margin check box. Adding the Rule Name and Tax Code columns provide additional context about which tax areas have rules that use VAT Margin.