Documentation | My Retail Pro

Updated: July 20, 2020 11:51am

1.10.0.888 What's New in this Release

This page has information about new features and functionality added in Prism 1.10.0.888.

Feature	Description
Serial/Lot Number Enhancements	This release includes key enhancements to the serial and lot numbers feature in Prism. Key Changes Validation of serial and lot numbers Ability to change Serial Type and Lot Type (partial or full control) Add/Edit/Remove numbers in Prism inventory New preferences to handle lot numbers past the expiration date Grid formats to include serial/lot number fields
Connection Manager	This release included a new Connection Manager area in Admin Console for configuring replication. Please note that the Connection Manager introduced in 1.10.0.888 has been superceded by the new combined Technician's Toolkit and Connection Manager functionality.
Image Server	DevTrack ID#12601 Beginning with this release, retailers can centrally manage customer and item images by selecting the server where the image files are stored. Previously, images were specific to each Prism server and could not be mapped to a different server. Now, images can always be pulled from the same central repository, ensuring consistency among images across the retailer's stores.
Proxy Command Line Parameters	DevTrack ID#11977 New command line parameters have been added to PrismProxy.exe to allow users to launch the Proxy for a server other than the server specified in the registry for that proxy port. -prismserver:[PrismServerName] (the name of the server) -prismport:[port#] (the port to use to connect to the server) Example: PrismProxy -port:8080 -prismserver:xsn-win764-em64 -prismport:443
Restrict Tenders by User Group	DevTrack ID #11679 This release includes a new set of permissions that restrict the use of tenders by user group. There are separate give/take/return permissions for each tender type. Previously, there was no way to restrict tenders for individual user groups. These new permissions give retailers greater control over the tendering process. You can set these permissions at the Global, Subsidiary, or Store level.
Store Assignments enforced	DevTrack ID#12070 A key security requirement for many retailers is to restrict the store locations where individual employees can make transactions. Beginning with this release, store assignments from Retail Pro 9 are enforced in Prism. This means that to create a transaction for a store in Prism, the user must be assigned to the store where the transaction is being created. Employees are assigned to stores in Retail Pro 9. The store assignments are replicated to Prism during initialization. If a user encounters a store assignment error in Prism when trying to make a transaction, make sure the employee is assigned to the correct stores in Retail Pro 9.
Prompt for Decimal Qty preference	DevTrack ID#14176 A new preference enables retailers to control whether or not a prompt is displayed when a user lists a decimal quantity item on a transaction. The new preference is located in Preferences & Settings > Transactions > General. If selected, when a user lists a decimal quantity item on a transaction, a prompt will be displayed to enter a decimal quantity. The user must enter the desired quantity. If not selected, no prompt is displayed when a user lists a decimal quantity item on a transaction. The quantity defaults to "1". This gives retailers the ability to bypass the prompt, if desired. This preference is especially useful for retailers who have plugins that need to suppress the display of prompts like the decimal quantity prompt (shown below). Enter Quantity prompt
Print Non-Currency Tenders	DevTrack #11074 Beginning with this release, users can select which non-currency tenders will be printed on Z-Out reports. This option has been available in Retail Pro 9 preferences but previously was not available in Prism. This meant that all credit and debit (and other tenders) transactions were listed in the Z-Out report, producing extremely long reports. Now, by clearing a tender, retailers can prevent the individual transaction from printing on the report. Preferences & Settings > Reports > X/Z-Out: Print Non-currency Tenders By default, all tenders are selected. Clear the individual tenders that you don't want to print.
Copy Customer	DevTrack ID# 13958 You can now create a new customer record by copying an existing customer. This can speed up the customer creation process. Simply copy an existing customer and make any needed changes for the new customer. This can often be faster than adding a new customer from scratch. Fields that are not copied: SID, Customer ID, Store Credit, Charge Balance, AR Flag, Loyalty Balances, system-based dates, Customer statistics, Active status, customer image.
New Customer Required Fields	DevTrack ID #14405 This release includes a new preference that allows retailers to pick the specific customer fields that require an entry when a user adds a new customer. The New Customer Required Fields preference is in Admin Console > Preferences & Settings > Customers > General. Select the check box for each field that will require an entry when creating a new customer record. If any of the selected fields are left blank when creating a new customer, Prism will display an alert explaining which fields must be completed to save the record. By default, First Name and Last Name are selected. The following fields are available for selection as required fields for new customer records. Address 1 - Address 6 Address Location Type Postal Code Customer ID Customer Image Email First Name (default) Last Name (default) Info 1-2 Mark 1-2 Notes Phone
Translations for Customizations	DevTrack ID# 11897 Retailers can easily implement translations for their third-party UI customizations by making simple edits to a copy of the appropriate language-specific .json file. Previously, third-party developers had to implement their own custom solutions for implementing translations for plugins. Now, the developer simply has to type (or copy/paste) the desired translation text next to the base (native) text and save the file to the \locale folder with -custom appended to the file name. When loading the page, Prism will check if a -custom version exists and load the -custom version instead. This change provides developers with an easy-to-implement standard for handling translations. For example, if the file was named en-us.json, then name the file en-us-custom.json
Availability checking for slips	DevTrack ID#12555 Note: Changes in Prism 1.11.0 resulted in this preference being moved to a new area in preferences: Preferences & Settings > System > Documents Retailers can now have Prism perform availability checking on slips. This enables retailers to verify the quantity listed on an out slip is actually on-hand in the source store's inventory. If the quantity specified on the slip exceeds the current OH Qty in Inventory, Prism will display a warning. In most cases, stores want to transfer excess inventory. By enabling the Availability Checking preference, retailers will be alerted whenever the quantity on an out slip exceeds the current OH Qty.
Promotions Sort Order setting	DevTrack ID #13697 A new "Sort Order" option has been added to two areas of Promotions: Sale Item Validation and BOGO Discount Reward. The available values vary slightly Sale Item Validation has a dropdown setting for "Sort Order". The available values are Highest (default) and Lowest. The Sort Order setting determines how a discount will be applied when multiple items on a receipt are eligible for the promotion. This setting determines which applicable items are validated first, sorted by Price. Note: This may affect which items are discounted by an Item Discount reward. Sort Order dropdown for Sale Item validation rules:
ClaimatStartup setting for cash drawers	DevTrack ID# 14138 Current Proxy functionality allows multiple proxies to access the same cash drawer on a POS workstation. A new option has been introduced. Now the Cash Drawer plugin (OPOSCshDrwr.DLL) will read an additional optional field from the OPOSConf.ini file, called ClaimAtStartup. Example: [CshDrwr1] LDN=A798-1 ClaimTimeout=10 Actv=1 ClaimAtStartup=1 If this value is 1, the Proxy claims the cash drawer at proxy startup time, and holds it until the proxy terminates. This allows faster response to drawer open and status requests. If this value is 0, or the field is not present (as in the field for current users), the Proxy claims the cash drawer at each drawer open or status request and releases it again when the action is complete. This allows multiple proxies to access the same cash drawer, if required. Note: You must manually edit the OPOSConf.ini file (under the CASH DRAWER section) to include this option and parameter.

Previous

Next

Search Documentation