What's New in 1.14.7.1292

PDF

This topic has information about new features and functionality added to Prism in 1.14.7

Apache Upgrade to 2.4.43
Prism 1.14.7 requires an upgrade to Apache 2.4.43. You must upgrade Apache before installing the Prism 1.14.7 update.

1. If you have installed additional web-based applications that use the Prism Apache server, then before uninstalling the current Apache backup the httpd.conf file from the Apache\Conf directory and any custom modules that are in the Apache directories
2. Uninstall Apache 2.24.27 (used with Prism 1.14.6 and earlier versions).
3. Restart the computer. Delete any registry keys associated with the old Apache.
4. Launch the Autorun.exe for 1.14.7 and install Apache 2.4.43.
5. After installing the new Apache restore any missing modules in the Apache directories and manually apply any missing elements from the backed-up copy of the httpd.conf file to the new httpd.conf file.

MySQL 8.0 Support
Prism 1.14.7 is compatible with MySQL versions 5.7 and 8.0. When you install the Prism server (MySQL version), the system verifies that you have the correct MySQL version (either 5.7 or 8.0) installed. Support for MySQL 5.7 ends in 2023; therefore, this documentation focuses on MySQL 8.0.
Requirements
Copy MySQL 5.70 32-bit files to local machine: The user must copy the MySQL 5.70 32-bit files to the local machine and enter the path to the files when installing the Prism Server (MySQL version). This requirement is the same as before.
Use Legacy Authentication: MySQL 8.0 offers users two authentication methods: a newer method that uses strong password encryption and a legacy method that is less secure but offers compatibility with MySQL 5.x. When installing MySQL 8.0, be sure to select "Use Legacy Authentication Method (retain MySQL 5.x Compatibility)".
Turn off Binary Logging: MySQL 8.0 enables binary logging by default and that can take up a lot of space. We recommend that you disable binary logging by editing the my.ini file and comment out the "log-bin" section by placing the "#" character at the front of the line.

Web-Based Tech Toolkit
DevTrack ID #17420
The Tech Toolkit is a special area of Prism for performing database maintenance and other technical tasks. Previously the toolkit was available as a separate .exe that was typically launched from a shortcut on the user's desktop. Beginning with 1.14.7, the Tech Toolkit (except for the "Rename Host Computer" feature) is accessed via a web browser. This makes it easier for technicians to access any server in the enterprise to perform needed tasks.
Launch Tech Toolkit:
Point your web browser to /TTK.
Example: myhost.mydomain.com/TTK
Most functions in the Tech Toolkit require administrator-level privileges so log in using an admin-level username and password (default = sysadmin/sysadmin).
 
The top of the screen has a set of tabs for navigating the toolkit.
 
Refer to the following table for information about the areas available from the top menu:

Area	Description
System	System information. This enables you to quickly verify the operating system, installed components and other system information.
Services	Log Viewer. This enables you to easily view log files. Log files are scattered in different areas of the program. Using the Log Viewer provides a convenient single viewpoint.
Scheduler	Scheduler. Schedule tasks to run at regular times.
Logs	Log Viewer. This enables you to easily view log files. Log files are scattered in different areas of the program. Using the Log Viewer provides a convenient single viewpoint.
Data Injection	In this area, data from external sources can be added to the Prism database. Currently, this area is only used to inject postal codes for US and Canada into the database as part of the ZIP Code Lookup feature.

On the left side, a list of the enterprise's servers is displayed. Click the hamburger icon to access options for adding servers, leaving, rejoining, etc.

Regional Inventory
DevTrack ID #16063
Prism's Regional Inventory feature provides an effective solution for retailers who need to balance central versus local control of Inventory. When using Regional Inventory, certain key item information is under the control of a "master" subsidiary. This typically includes information like UPC, Price and Cost that enables item sales to be tracked accurately. Other item information (e.g. Description 1 and Description 2), can be edited at the "child" subsidiaries so that descriptions are in the local language.

1. Designate one or more Subsidiaries as masters by editing the Subsidiary record and selecting the Master checkbox.
2. In Admin Console > Global Preferences > Corporate Regions > General, add one or more corporate regions and assign subsidiaries. Select the master.
3. Configure Regional Inventory options. The options selected here are the key fields that will be controlled by the Master subsidiary. Fields that are not selected or not in this list can be edited at child subsidiaries (e.g. Description 1 and Description 2).
4. In the Inventory record of items that will be under regional control, select the Regional Inventory checkbox.

Store Qty filter for Inventory Lookup
DevTrack ID#19142
Users can search Inventory for items that have a certain Store Qty. This enables retailers to verify inventory quantities at the store level. The Store Qty filter element is only available in the Inventory area. It is not available when searching for Inventory items on documents (transactions, purchase orders, etc.).

• The Store Qty column is displayed by default in Inventory Lookup grids.
• The Store Qty filter elements is not displayed by default in the Search By drop-down of Inventory Lookup; you must add it in grid formats.

To add or remove Store Qty from the Search By drop-down:
Navigate to Admin Console > Node Preferences > Grid Formats. Select Inventory Lookup in the "Select a grid to configure" drop-down. In the Allow Search By area, move the Store Qty element from the "Available" list to the "Selected" list. Use the arrow buttons to move the element to the desired position in the list.
To add or remove Store Qty as a column in Inventory Search Results:
In the Show Columns area, the Store Qty element is included by default in the Selected and Default Visible lists. This means Store Qty is already included in Inventory Lookup grids. Use the arrow buttons to move the element to the desired position in the list.
 After adding the Store Qty element to the list of "Allow Search By" fields and saving the changes, Store Qty will be available in the drop-down list when choosing a "Search By" element in Inventory Lookup.
Enter a quantity range.
Click the Search button. Items with a Store OH Qty within the range are displayed.
The Store Qty column in the grid shows each item's current OH Qty in the store.

Log Override
DevTrack ID #17564
A user can now enable Log Override for any permission that is set to Override. Each time an override occurs for a permission that is configured to Log Override, the date/time, the permission and both users involved will be recorded to an audit_override_log table. Note: If the permission is not set to Override, checking the Log Override checkbox has no effect.

Logging Enhancements
DevTrack ID #19591
Various enhancements have been made to Prism logging. Users can view logs in the Logs area of the web-based Tech Toolkit.
To access logs, click the Logs tab on the Tech Toolkit menu.
A separate log in is required to view logs. The default username/password is "loguser/loguser". After successful login you will see a list of available log areas.
PrismLogging.ini
Configuration settings for log files are stored in the PrismLogging.ini file. The PrismLogging.ini file is in the …\ProgramData\RetailPro\Server\Conf folder. PrismLogging.ini has a [global] section and can have sections for each Prism service. The settings defined in the [global] section apply to all services.
You can change global log configuration settings in the Services > Prism Stack area of the toolkit.
You can change log configuration settings for individual Prism services in the Services area of the toolkit. When you save the changes, the PrismLogging.ini file is automatically updated. A new section is added to the PrismLogging.ini file for the service with the key-value pair.
Example of service-specific setting in PrismLogging.ini:
[PrismMQ]
FORCELOGINFO=true
RetainXLogs=12
[PrismCommon]
LOGLEVEL=3
RetainXLogs=15

Round Loyalty Points Preference
DevTrack ID #18404
This preference is especially useful for retailers who use a relatively small multiplier for the "Earn" rate of Total-Based loyalty programs. This preference only applies to Total-based loyalty programs.
0: (default) ROUNDS Total-based points earnings to nearest whole $ (up or down)
None: ROUNDS Total-based points earnings UP to the whole $
1, 2, 3, 4: ROUNDS Total-based points earnings to the specified number of significant digits

Dynamic Loading of JavaScript, HTML files for EFT
DevTrack ID#19999
Now, when a user selects an EFT Provider (Cayan, Adyen or B+S) in Admin Console > Node Preferences > Transactions > Tender > EFT Server Configuration, Prism will automatically load the correct version of the customizations.js and customizations.html files. Previously, users had to navigate to the \ProgramData\RetailPro\Server\WebClient folder and manually edit the files using a text editor. Automatically loading the correct version of the .js and .html files simplifies the EFT setup process.

Multi-Proxy Support for Adyen
DevTrack ID #18772
Changes have been made to the Adyen configuration file (Adyen.ini) to support multiple Prism Proxies on a single workstation.
Basic Steps
1.    Determine how many devices will need to connect to the workstation where theProxy is installed. Each iOS device requires its own instance of the Proxy running on a separate port. When installing the Prism Proxy, users specify the number of instances the port numbers.
2.    Edit the Adyen configuration file (Adyen.ini) to include the list of ports (instead of a single port). Update the Adyen.ini file with new KEY names i.e., IPPort(old) with IPPortList(new) and AsyncPort(old) with AsyncPortList(new).
Here's an example of the relevant section of the Adyen.ini configuration file.
[Customization]
IPAddress=127.0.0.1
IPPortList=5551,5553
AsyncPortList=5552,5554
The above example will allow two proxies to use the Adyen customization with two different Adyen devices. The first device will receive synchronous transaction commands on port 5551 and asynchronous cancellation commands on port 5552; the second device will do the same on ports 5553 and 5554. The configuration requires that both lists (IPPortList and AsyncPortList) have the same number of ports.

Gift Receipt Print Preferences
DevTrack ID#19984
Gift receipt print preferences are now found under the POS Transactions node. Previously, gift receipts had their own node in Print Preferences. Print preferences enable you to customize the print/update process by selecting a default action and other options.

1. Navigate to Admin Console > Node Preferences > Hardware > Print Preferences.
2. Click POS Transactions.
3. Select the Gift Receipt sub-area.
4. Select a Default Action.
5. Select other options as needed and save the changes.

 Permissions for Printing Documents and Barcode Tags
DevTrack ID #17293
You can set group permissions for printing documents and barcode tags. This provides added security by enabling you to control which employees can print documents and barcode tags. Previously, most printing tasks were not controlled by permissions. The one exception was the reprinting of an already updated receipt, which is already controlled by a security permission.
The following table lists the new permissions. As part of this change, the permission called POS - Print Held was removed.

Permission	Description
Adj Memos - Print Held	Allow group members to print held adjustment memos.
Adj Memos - Print Updated	Allow group members to print already updated adjustment memos.
ASN - Print	Allow group members to print ASNs
ASN - Print Held	Allow group members to print held ASNs.
Disbursements - Print Updated	Allow group members to print updated disbursements.
Merchandise - Print Tags	Allow group members to print merchandise price tags.
POS - Print Held	Allow group members to print held receipts.
POS - Print Updated	Allow group members to print updated receipts.
Transfer Order - Print Held	Allow group members to print held transfer orders.
Transfer Slip - Print Held	Allow group members to print held transfer slips.
Transfer Slip - Print Updated	Allow group members to print already updated transfer slips.
Vouchers - Print Held	Allow group members to print held vouchers.
Vouchers - Print Updated	Allow group members to print updated POS receipts.

Change SBS/Store (Multi-SBS, Multi-Store)
Prism records the Subsidiary and Store of all documents or records created in the system. By default, this is the Subsidiary and Store entered in the workstation record of the current logged-in user's workstation. The MultiStore/MultiSBS feature enables retailers to create documents and records for any location (any SBS or combination of SBS/Store) while staying logged in at the same default location (as set in Admin Console for that workstation). In previous versions of Prism, the only way to create a document for a different Subsidiary and/or Store was to go into the Workstation record, edit the workstation's Default Subsidiary and/or Default Store, log out and then log back in and create the document. After the document or record was complete, the user would have to change the workstation assigning back to the original location.

• The location change is set on a per document basis and remains in effect until the doc is updated or canceled. Once Updated/Canceled, the location reverts to the default location as set in the workstation record in the Admin Console.
• The ability to create documents and records for other locations is limited by various factors including the employee's permissions and Store Assignments.
• The ability to change location only applies to New records of the datatypes described above/below. The ability to change location is locked for updated records.

Change Fulfilling Store of Customer Order
DevTrack ID #16366
You can fulfill an order at a different store than where the order was created. This enables a customer to order an item at one location and then pay for and pick up the item at a different location (e.g. the store in the customer's own hometown). This is especially useful if the item is difficult to transport. Previously, orders had to be fulfilled at the store where the order was created.
Limitations:

• The user must have the POS > CHANGE ORDER FULFILLMENT STORE permission.
• The only stores available for selection are those to which the Associate is assigned in Store Assignments.
• All order items on the document must be set to the same fulfillment store.
• If any of the order items have been fulfilled (or partially fulfilled), the Change Fulfillment Store button is disabled.

To fulfill an order using a different fulfillment store:
Use Transaction Lookup to find and display the order. Click the Order Details button on the transaction form. Click Fulfill Order.
If you have the permission enabled and are at a different store than the original fulfillment store, you will be able to proceed.

Comment 1, Comment 2 increased to 255 characters
DevTrack ID #19042
The maximum length of entries in the Comment 1 and Comment 2 fields on transactions has been increased to 255 characters. Previously, the maximum length was 60 characters. Increasing the maximum length of the Comment 1, Comment 2 fields enables retailers to leave more detailed comments that more clearly express the intended message. This change brings Prism in line with RIL (or Retail Pro 9), where the maximum length of Comment 1, Comment 2 fields was already 255 characters.

Touch Menu Enhancements
DevTrack Issue #19009
Touch Menus have been improved to make it easier to move buttons or copy a button from one menu to another. Previously the process for moving or copying touch menu buttons was a bit cumbersome. The changes that have been made make this much easier and save time. The user can either move or copy buttons by highlighting the desired buttons, and then dropping one of the items on a target menu (Navigation Button). Let's say a menu called "Top Menu" has five items: Item A through Item E.
 Next, to move Items A,B, & C to a different menu, called "Sub Menu". First, we create the Sub Menu. Go back to the "Top Menu".
Click Create Button. On the new button screen, select "Navigation Item" as the Button Type and set the destination to "Navigate to Existing Sub Menu".
The Nav button has a small icon showing four squares on it.
To move an item, simultaneously press the Ctrl key and click the button. The Ctrl+click adds a rotating border around the button. You can Ctrl+click on multiple buttons. (To unselect an item, simply do the Ctrl_click again).
After you've selected the desired buttons, drag to the Nav button - in our example, "Sub Menu". Once you drop the buttons, you will be presented with an action request menu:
 
Tender Screen as Modal/Dialog
DevTrack ID#19737
A new preference gives retailers the option of displaying the tender screen as either a regular page or as a pop-up dialog. Displaying the tender screen as a pop-up can make it easier for Associates to distinguish the tender information from the rest of the transaction. The default in a new Prism installation is a page. The new pop-up mode retains the previous tender control styles and actions.
The new preference is found in Admin Console > POS Transactions > General and is called "Open Tender screen in a pop-up window".

Changing Item Tax in POS Item Details
DevTrack ID #19141
Prism users can set the sales tax amount for each item on a transaction on an automatic or manual basis in Item Details. Previously, only the document-level tax could be set (in Transaction Details). As part of this change, a new Taxes tab has been added to Item Details. All item tax-related fields have been moved to the Taxes tab in Item Details.
Automatic is the default Tax Calculation method. This means that the tax amount for the item is determined by the tax rate assigned to the item's tax code in the current store's tax area. When set to Automatic, you can only select a different Tax Code. When set to Manual, the user can enter a specific Tax Amount or Tax %. If set to manual, then Tax Codes are set to value - ‘OVERRIDE'.
The ability to edit item tax is controlled by the following security permission: POS > Change Item Tax Amount. This permission(allow, override, deny) is applied on selection of the Manual radio button for Tax Calculation.

DETAX Amount in Item Discount Details
DevTrack ID #19592
When users click the Show Discount button in Item Details - Discounts, a modal displays information about the discounts (if any) applied to the item. This modal has been modified to include Detax amounts. This enables users to easily see the amount of tax removed because of Detax.

"Change WS Name" permission for Open/Close Register
DevTrack ID #18161
The X/Z-Out - Modify Workstation permission restricts an employee's ability to change the Workstation Name setting on the X/Z-Out report filter screen. Previously all users were able to edit the Workstation Name setting on the report filter. The Modify Workstation permission gives retailers greater control over reports and helps ensure that the report is generated for only the desired workstation. By default, the Z-Out report is generated for the currently logged-in user's workstation.
Z-Out Filter with Workstation field highlighted:
 
If the user belongs to a group that is assigned the permission, when opening or closing a drawer, the user can modify the workstation from the drop down list.
If the user does not have the permission, the Workstation element on the report is automatically set to the current logged-in user's workstation and cannot be edited.

Days in Transit Status on Transfer Slips
DevTrack ID #18702
Changes have been made to the transfer slip UI to make it easier for users to determine the status of the transfer and the arrival date of the merchandise.

• The label for the ETA Date field on transfer slips changes to Arrival Date after the transfer has been verified and the date reflects the actual arrival date.
• The Arrival Status field has been added to the slip header area. The Arrival Status changes from Scheduled to Received to Verified as the transfer moves through the receiving and verification process.

The Status field shows the current status of the Days in Transit value for the transfer. The Status field can have one of the following values:

Value	Description
Scheduled	If a Days in Transit value is defined, then before the voucher is updated, the Status is set to Scheduled. The DIT shows the default value defined in preferences.
Received	When a transfer voucher is updated but not yet verified, the Status is set to Received. The DIT shows the actual DIT based on the slip and transfer voucher created dates.
Verified	When the transfer voucher is updated and verified (per preference setting or Transfer Verification), the Status is set to Verified. The DIT shows the actual DIT based on the slip and transfer voucher created dates.

"Reverse Slips" Permission
DevTrack ID #19476
The "Transfer Slip - Reverse Slip" permission controls an employee's ability to reverse a transfer slip (out slip). In previous versions of Prism, only adjustment memos could be reversed. This permission only applies to a user request to reverse a slip. It does not include any slip reversal that occurs during Transfer Verification. Slip reversals that occur during Transfer Verification are considered a system-based reversal and do not require th "Transfer Slip - Reverse Slip" permission.
If a user belongs to a group that is assigned the Reverse Slip permission, the "Reverse Slip" button is available in the Transfer Slip UI. If a user does not belong to a group with the permission, the "Reverse Slip" button is disabled. When reversal requires an override, the override prompt is displayed.

Caching during Replication
DevTrack ID #19603 [Released with 1.14.6.1273 CCU on July 18]
When replicating messages from one system to another (i.e. from "Producer" of messages to "Consumer" of messages), Prism caches messages to prevent bottlenecks.
Previously, data messages were sent directly from sender to receiver. Caching messages enables replication to proceed more smoothly and helps prevent bottlenecks. Three modules work together to cache replication messages: PrismMQ.exe is an existing module; PrismMQProducer.exe and PrismConsumer.exe are new.
Sending side: PrismMQService saves messages to the PRODUCER_CACHE table. PrismMQProducer.exe monitors the PRODUCER_CACHE table, sends records it finds to the appropriate subscribers and then deletes the records from the PRODUCER_CACHE table. If the queue has more than 1,000 messages, PrismMQProducer stops sending messages to the queue. PrimsMQProducer stops, marks the corresponding records in the PRODUCER_CACHE table and adds the names of the paused queues to the REPLICATION_LOCKED_QUEUE table.
Receiving side: PrismMQConsumer.exe monitors the message queue and saves all received messages to  the CONSUMER_CACHE table. PrismMQ.exe monitors the CONSUMER_CACHE table. If PrismMQ.exe finds any messages, it saves those records to the Prism database and deletes them from the CONSUMER_CACHE table. A single queue, Prism.Day2Day, is used for both initialization and day-to-day replication. The INIT column in the PRODUCER_CACHE/CONSUMER_CACHE tables will indicate if the replication was initialization (1) or Day2Day (0).

Prevent Duplicate Promotion Names
DevTrack ID#19790
A new preference "Do not allow duplicate promotion names" has been implemented at the corporate and subsidiary level. The preference in Admin Console > Node Preferences > Transactions > Promotions. When this preference is enabled, users are prevented from entering a promotion name that is a duplicate of another promotion name. Entering a duplicate promotion name will give user an error message and will not save the changes. 
This preference is enforced when creating a new promotion, editing an existing promotion, or copying a promotion. Default = disabled.

Notes

• The check takes place within a single subsidiary
• The check is not case-sensitive and ignores leading or trailing blank spaces. This means that promotion names "ABC", "abc" and " abc " will be considered duplicates.
• Both active and inactive promotions are checked for duplicates. This means if you deactivate a promotion it will not eliminate it from the duplicate check. Instead, you will have to change the inactive promotion's name.
• When the preference is enabled, when copying a promotion, Prism will try to name the new promotion with the same name as the original one and appended with " (Copy)". If Prism detects that a Promotion with that name exists already, it will try a different naming scheme: the original name appended with " (#nnn)", where "nnn" will increment from 001 to 999. This process ensures that if a promotion is copied multiple times, each promotion will receive a unique name. Note: if there is a gap in numbers, the first missing number will be used. For example, if you have promotions "abc", "abc (Copy)", "abc (#001)" and "abc (#003", the new copied promotion will take the number in the gap, i.e. will be named "abc (#002)".
• If the new preference is turned on - when you are displaying details or are editing a promotion AND the current promotion has a name that is not unique you will see a message "Promotion name is not unique" in the right side section of promotion editor window under the promotion name. Note: the use case when you can have duplicate promotion names is when you had those duplicate names already prior to updating Prism or prior to enabling the new preference.