What's New in 2.2.0.25

PDF

This topic has information about new features and functionality added in Prism 2.2.0.25.

New Features and Enhancements

• Navigate Lookup Results  (#20930)
• Import Items on Documents  (#21527, 21528)
• UDF Fields Redesign with additional UDF Fields  (#22380)
• Search Options for Currency  (#23423)
• New Document State upon Switching Location  (#21394)
• Record Sale for Orders and Send Sale  (#15610)
• Email PDF copy of Receipt  (#22040)
• Delete Time Clock Records  (#22628)
• Edit Document Date permission  (#20197)
• Set Give Tender to last Take Tender  (#22534)
• Fulfill Send Sale at different Sublocation  (#21561)
• Multiple Address, Phone, Email included in Customer Lookups  (#21684)
• Add Created Date to Customer History Grid Formats  (#23012)
• Customer Required fields: "Company" and "Name or Company"  (#22461)
• Refund by Reference for Global Payments (Cayan)
• Promotion "Search By" Filters  (#17428)
• Validate Promotions by OH Qty  (#23163)
• Validate Promotions by Price Range  (#22614)
• Apply Item Promotion to Single Item or All Items  (#23200)
• Suggest Z-Out Open Amount match previous Leave Amount  (#23164)
• "Allow Add (tender)" setting in Tender Requirements  (#21869)
• Style UDFs  (#21194)
• In Transit Qty fields in Item Details - Qty tab  (#22615)
• Create All button in Style View  (#19281)
• Pagination for Adjustment Memo Lookup  (#23143)
• Auto TO
• Source OH, Target OH on Transfer Slip Item Grids  (#23860)
• Allocation Patterns for Transfer Orders  (#21210)
• Reason preferences for slips and transfer orders  (#21067)
• PO Lookup on Vouchers by Bill To Store, PO Store  (#23819)
• Disable editing of Qty field on ASNs  (#24759)
• Vouchers - Edit Pending permission  (#23005)
• Consolidate like items on ASNs, Vouchers and Slips  (#24445)
• Update Order Cost when Making Vouchers  (#25042)
• Convert Store Credit to Central Credit Tool in Tech Toolkit  (#24736)
• Show Total Discount Amount on Printed Receipts  (#24768)
• Add Foreign Currency symbol to PO Doc Designs  (#20149)
• Store Address and UDFs/Aux, Z-Out Read Count in Doc Designer  (#18637)
• Serial and Lot Number Fields on Tag Design  (#23037)
• Print Preferences for Standard, Return, Order Receipts  (#21566)
• Document Designer Subsidiary/Store Assignment  (#22695, 24111)
• PrismMQPublisher.exe (released as part of a 2.1.2 CCU)
• Purge Day-to-Day Replication History  (#17696)
• Reprocess All Errors (Entire enterprise or single connection)  (#24438)
• RabbitMQ Queue Cleanup when removing a server  (#23983)
• Log Settings for Data Replication Programs in Service Manager  (#24643)

Auto TO
See the Auto Transfer (Auto TO) topic for information.

Record Sale for Send Sale and Orders
DevTrack #15610
Users can record a sale from a "send sale" or order (customer, layaway, or special order), with the option to print/not print a receipt.
In Admin Console > Node Preferences > Transactions > Orders, you can define the desired workflow (for each order type) when recording a sale: Always Allow (0) or After Final Deposit (1). By default, Always Allow is selected.
All items on the order document must be unfulfilled to use the Record Sale option. If the Balance Due for the order is 0.00, the Prism server always allows record sale. If there is a Balance Due amount, the Prism server checks the Allow Record Sale preference setting. If the preference is set to Always Allow (0), the Prism server allows record sale; if the preference is set to After Final Deposit (1), the Record Sale button will be disabled in Order Details and the user must first use the Fulfill Order feature to pay the unpaid balance.
Order fulfillment and a record sale are treated as two separate actions by Prism. That is, a user can have the ability to fulfill an order but not record a sale, and vice versa. Separate permissions control each action: "POS - Record Sale" and "POS - [Order type] Fulfill."
 
To record a sale at POS, display the order document and click Order Details and then click Record Sale.

When you click Record Sale, a prompt asks if you want to print a receipt. Click Yes to print a receipt for the record sale or No to skip. When recording a sale, Prism will create a sale transaction to fulfill all order items, using Deposit as the tender. Note that this may cause the deposit balance to be negative on the order.
Record Sale/Record Return Toggle button
After a "Record Sale" occurs, the Record Sale button in Order Details becomes "Record Return." This enables users to record a return for an order to reverse the Record Sale.
Editing an Order after Record Sale
If a record sale has occurred for an order, no item level values may be edited, no doc order discounts, fees, customer, shipping, associates, or adding items. You may edit: order date, ship date, cancel date, doc comments, and deposits.

Import Items on Documents
DevTrack ID #21527, 21528
You can import a list of UPCs, ALUs, or Item Numbers to populate the item list on a document. Importing a list of items is especially useful when a local store has only a single or limited number of POS systems. Documents like purchase orders, vouchers, adjustments, etc. can take a long time to complete and interfere with sales activity. Using the import feature, a user can create a list of items on a non-POS computer (e.g., a laptop with Excel) and then import the list into a purchase order or other document when the POS system is not busy.
To import items on a document, click the Options button and select Import Items.
When importing items on a document, you must first select an existing mapping schema or define a new schema. For each line (record) in the import file, the schema tells Prism the beginning position and length for values like UPC (or ALU), Doc Qty, Doc Cost and Doc Price. In this way, each item listed in the file can be listed on the document in Prism.
Sample new document mapping schema:

Click Continue.
Next, browse to the location of the import file and click import. Note: Some records may fail to be posted, for a variety of reasons (failed lookup, availability checking, bad import data, etc.). In the case of failure, a message will report back to the user how many records failed and give the user an opportunity to view/download the failed records.

Convert Store Credit to Central Credit Tool in Tech Toolkit
DevTrack ID #24736
The new Convert Store Credit to Central Credit tool in Tech Toolkit enables retailers to easily migrate customers' regular store credit to central store credit so retailers can take advantage of the benefits of using Centrals.
Benefits of Centrals:

• Reduces the risk of fraudulent transactions caused by communication lag time.
• Helps to ensure a smooth customer experience.

Requirements
Run the tool on the Centrals server. Prior to running the tool, make sure all customer records have been replicated to the Centrals server.
The tool is only available when:

• Centrals is enabled in Prism Admin Console | Installation Defaults and Node Preferences | Transactions | Centrals.
• Any customer records with store credit exist at the Centrals server.

Notes
The tool creates a Prism sale document where the store credit amount is taken as a tender and the same amount is given as a central credit tender. This transaction will subsequently be recorded n the customer's Customer History listing.
After running the tool at the Centrals server, the updated central credit information will replicate to other servers in the enterprise (assuming Connection Manager replication settings are configured correctly)
Click Data Utilities > Convert Store Credit to Central Credit. (If the link for the tool is not visible, verify you are logged into the server shown as the "Central Address" in Admin Console | Installation Defaults.)

The tool first checks to make sure the system meets the requirements (i.e., Centrals enabled and customers with regular store credit exist). If the requirements are met, the Execute Credit Migration link is visible and active. Click Execute Credit Migration. When the process finishes, the number of migrated customers is shown:

Navigate Lookup Results
DevTrack ID #20930
After a search, if selecting ‘Ok' (or Details) to view one of the results, there will be Next and Previous buttons to allow navigating through the search results. This enables users to navigate a list of lookup results without having to return to the results list each time. In V9, the PgUp and PgDown buttons served a similar purpose.
The Previous and Next buttons are available in the following lookup areas: POS Transaction Lookup, Disbursement Lookup, Inventory Item - Detail View, Vendor - Detail View, Department - Detail View, Adjustment Memo - Document View, Purchase Order - Document View, Voucher - Document View, ASN - Document View, Transfer Slip - Document View, Transfer Order - Document View.
The Next and Previous buttons are not enabled when in Edit, Copy or New mode.

New Document State upon Switching Location
DevTrack ID #21394
When a user changes location on a document (all types), the system is put into a new document state and the user is free to move forward adding items to the document. Previously, when changing location before entering items on a document, users had to click the New button on the bottom menu to edit the document at the new location. This saves time and button clicks.

 UDF Fields Redesign
DevTrack ID #22380
The preferences areas for user-defined fields (UDFs) have been redesigned.  The new design makes it easier to distinguish between text and date fields. The following preference areas are updated: Inventory, Customer, Vendor, and Employee UDF.
New design:

Search Options for Currency
DevTrack ID #23423
When working with the list of currencies (Admin Console > Global Preferences > Currency), users can now:

• Search for a currency.
• Deactivate/activate a currency.
• Display active, inactive or all currencies.

These search and filter elements make it easier to navigate and work with the list of currencies.
Search for a Currency
Type any or all characters of the currency name and click the Search button or press the key. The list is filtered based on the characters entered. To clear the Currency Name entered in the Search screen (and the filtered list), click the X.
Activate/Deactivate a Currency
To activate/deactivate a currency, select the currency and click the Activate/Deactivate button. The Active column changes to True/False. The Denomination grid now also displays active status in its columns.
Filter by Active/Inactive Status
To filter the list of currencies by Active/Inactive status, click the Active or Inactive buttons at the top of the list. To view all currencies, click the All button. If filtering by active or inactive currencies, users also have the option to "activate all" or "deactivate all". Doing so updates all items in the results and changes the grid to display the opposite filter (so the user will see all newly activated/ deactivated items).
Sample list of currencies showing Search and filter options:

Email PDF copy of Receipt
DevTrack ID #22040
Retailers can configure Prism to email a PDF copy of the receipt to the customer's email address. Previously, email receipts were in HTML format. Now users can choose the desired format: PDF or HTML.
To email receipts to customers:

• Configure Prism preferences and enter email server information.
• Add email addresses to customer records.

When one or more email addresses are in a customer's record, Prism enters the customer's primary email address in the Print dialog when printing/updating a transaction. You can add or edit the email address in the Print dialog.
If using the email feature, be aware that is the end user's responsibility to enter the correct SMTP server information in the Prism Admin Console > Node Preferences > Hardware > Email Server Preferences area.
In the POS Receipt Email Attachment Type field, select HTML or PDF. If you select PDF, Prism attaches the receipt as a PDF file to the email. If you select HTML, Prism embeds the body of the email as HTML.

Sample Node Preferences > Hardware > Email Server Preferences:

Delete Time Clock Records
DevTrack ID #22628
There is now a Delete button on the Time Clock screen that enables a user to delete the most recent Time Clock record for any employee if the user has the appropriate permission.
Two permissions have been added to Group Management:

• Time Clock - Delete Check In
• Time Clock - Delete Check Out

Sample Time Clock lookup screen showing Delete button on bottom menu:

Edit Receipt Date permission
DevTrack ID #20197
The user can now edit the transaction date at POS>Transaction Details.
The permission "POS - Edit Document Date" governs this functionality.
A user with the permission set to DENY cannot edit the date
A user with the permission set to OVERRIDE can edit the date with override credentials.
A user with permission set to ALLOW can edit the date freely.

Change Customer on Finalized Transaction Permission
DevTrack ID#22957
The POS - Change Customer on Finalized Transaction permission enables retailers to control which employees can edit Bill To Customer on updated transactions.
Notes:

• You can change the Bill To Customer but cannot remove it.
• You cannot change the customer if the transaction involves customer loyalty.
• You cannot change the customer if there are fulfillment transactions that reference order item.
• This permission does not apply to the Ship To Customer.

 Override default Give Tender to be current Take Tender
DevTrack ID #22534
A new preference "Set give tender to last take tender if allowed" has been added to Node Preferences > Transactions > Tenders > Requirements.
The "Set give tender to last take tender if allowed" preference gives retailers greater flexibility in situations like the following:
Associates use mobile devices for sales and the Default Give and Take tenders for are set to credit card. However, some sales use non-default tenders (e.g., Cash). too. If the "Set give tender to last take tender if allowed " preference is enabled and a return is made against a non-default tender, the Take tender will be entered as the Give tender. This saves the Associate from having to select the Give tender (which the Associate may forget to do and thus use the wrong tender). Note: An exception is if that non-default Tender type is not enabled for 'Give'.
Previously in that situation, the default Give tender specified in preferences would be used.
Sample Tender Requirements preferences showing the "Set give tender to last take tender if allowed" checkbox in the upper left corner:

Company as Customer Required field
DevTrack ID #22461
In Admin Console > Node Preferences > Customer > General, there are new fields in the "Required" list: "Company" and "Name or Company."
Company works the same as the other required fields. If it is selected, then when creating a new customer record, the Company field requires an entry.
Name or Company is dynamic. This selection will require any of the three fields (First Name, Last Name, Company) to be populated. Once any of these three fields are populated, the requirement is met.
The Name or Company selection helps retailers in Spain comply with fiscal laws that require the company name when issuing an invoice to a legal entity, (First Name, Last Name when issuing an invoice to a person).
Sample Node Preferences > Customer > General showing Name or Company selected as a Required field (and First Name, Last Name and Company disabled)

Add Created Date to Customer History
You can add Created Date to the Search By filters used to search Customer History and the Customer History results grids. This change enables Associates to see the when a transaction took place when viewing customer history.
1.    Navigate to Admin Console > Node Preferences > Grid Formats. Select Customer History from the "Select a grid to configure" dropdown.
2.    In the Allow Search By area, move the Created Date field from the Available list to the Selected list. Reposition the field to the desired place in the list.
3.    In the Show Columns area, move the Created Date field from the Available list to the Selected list. Reposition the column to the desired place in the grid.
4.    Save the changes.
Sample Node Preferences > Grid Formats for Customer History:

When a user clicks the Search By dropdown in Customer History, the Created Date field will be available in the list.
When the user clicks the Search button, the Results grid will include the Created Date column in the appropriate position.
Sample Customer History search results showing Created Date column:

Customer Required Fields: "Name" or "Name or Company"
In Admin Console > Node Preferences > Customer > General, there are new fields in the "Required" list: "Company" and "Name or Company."
Company works the same as the other required fields. If it is selected, then when creating a new customer record, the Company field requires an entry.
Name or Company is dynamic. If First Name, Last Name, or Company are enabled, then Name or Company is disabled. If First Name, Last Name, and Company are all disabled, then Name or Company can be enabled. Enabling Name or Company disables First Name, Last Name and Company.
The Name or Company selection helps retailers in some countries (e.g., Spain) comply with fiscal laws that require the company name when issuing an invoice to a legal entity, (First Name, Last Name when issuing an invoice to a person). In the Name or Company field, the Associate can enter First Name, Last Name, or Company name.
Sample Node Preferences > Customer > General showing Name or Company selected as a Required field (First Name, Last Name and Company are disabled):

Refund by Reference for Global Payments (Cayan)
Refund by Reference is a special Global Payments feature that ties a Prism return transaction to the original EFT transaction (using tokenization). If a returned item references an original sales transaction, and the original transaction listed a credit card as tender, the Associate sees a prompt to issue the refund to the original tender. No credit card is required at the time of the return. This feature ONLY applies to credit cards. The tender MUST be one of the tenders linked by the returned items.
Start a new item return in Prism. Select the original transaction and items.
Click the Tender button and then click the Give button.
A dialog asks if you want to return the amount to the original Credit Card. Click Yes to issue the return to the existing token.

 
A dialog displays the credit card tender(s) for the original transaction. Click the desired tender.
Refund by Reference with single credit tender:

 
Click the Print/Update button to update the transaction. The amount is refunded to the card.
Note: If you click No, then a non-token return request will be sent to Global Payments. You will be prompted to swipe the card through the CED.
Split Tender using Multiple Credit Cards
If "Yes" is selected and there are multiple tokens (because multiple cards used) on the original transaction, a multi-select dialog will be displayed. Each token is represented by card type, masked number and original amount. Please note that this dialog only allows you to select one credit card for the refund. If you need to use the tokens for multiple cards to refund the amount due to the customer, you will have to create multiple receipts. You should click Cancel in the dialog, and then modify the transaction to use the amount of the first card, tie the refund to the token and tender. Then repeat for additional cards as needed.
For split tender transactions involving multiple credit cards, the card and amount will only display if the card's token is in the Prism database. If the token was removed, then the card will not be displayed in the dialog to select a specific card.
Refund by reference with multiple credit tenders:

Promotion "Search By" Filters
Devtrack ID #17428
Additional filter types are available in the ‘Search By' list in promotion search: Promotion Group, Discount Reason, Store and Price Levels have been added. You can add any or all of these filter fields to the ‘Allow Search By' list in Admin Console > Node Preferences > Grid Formats. This makes it easier to find promotions.
Sample Node Preferences > Grid Formats for Promotions showing the new search options:
 
After adding the fields in grid formats, log out and log back in.
Next, go to POS > Promotions.
Click the Search By dropdown. The new search elements are included in the list. Select the desired search element(s) and enter criteria.

Validate Promotions by OH Qty
DevTrack ID #23163
The ability to specify a Store On Hand Quantity has been added to validation rules.
Company OH Qty is a calculated field and cannot be used for this filter.
It is important to note that when Store On Hand Quantity is defined, Prism only checks the OH Qty when the transaction is started. For example, if the Store On Hand Qty threshold is set to 5, the promotion will trigger when the Store OH Qty is 5 or less when the transaction is started; however, if the Store OH Qty is 6 and the customer buys all six units, the promotion will not trigger.

Validate Promotions by Price Range
DevTrack ID #22614
The ability to specify a price range has been added to the price filter in Promotions.  This allows the user to set a range, and any item with a price in the specified range will trigger the promotion at POS.

Apply Promotion to Single Item, All Items
DevTrack ID#23200
The Validation Rules screen for item promotions has two new radio buttons that enable retailers to control how item promotions are applied:
Single Item: if the promotion has a subtotal validation rule, the promotion will apply to a single item quantity (one item every run)
All Items: If the promotion has a subtotal validation rule, the promotion will apply to all item quantities. This supports use cases like "Buy $100 in socks and get 20% off."
Sample Validation Rules for Item Promotion showing Subtotal filter and "Single Item" radio button selected (Discount applied to items that meet or exceed the item subtotal threshold):

Suggest Z-Out Open Amount match Previous Day Leave Amount
DevTrack ID #23164
The Leave Amount of the previous drawer closing is now the suggested Open Amount for the next Z-Out, whether the system uses structured or unstructured mode. The user can modify the suggested opening amount if needed. For example, a retailer may have a policy to always leave 500 Euros in the drawer when closing the drawer at the end of the day. The following day when the store clerk opens the drawer the same amount should be defined entered as the Open Amount when creating the Z-Out Open for the same workstation.
Setting the Open Amount to the previous days' Leave Amount helps retailers:

• Maintain consistency when closing/opening drawers.
• Avoid data entry errors.
• Draw attention to discrepancy amounts.

"Allow Add (non-currency tender)" setting in Tender Requirements
DevTrack ID #21869
The "Allow Add" option in tender requirements preferences enables retailers to limit which tenders can be added in the Non-Currency Count area when closing a drawer. By default, the Allow Add option is enabled for all tenders. Disable the option for specific tenders as needed. Previously, users had access to all active tenders in the Non-Currency Count area.
In Admin Console > Node Preferences > Transactions > Tenders > Requirements, the the Allow Add option is paired with the Auto Match option. The two settings work together to limit users' ability to add non-currency tenders on Z-Out reports:

• When Auto Match is enabled for a tender, the Add button is disabled in the X/Z-Out report interface. This forces the Auto Match behavior and prevents the user from adding additional instances of that tender.
• When Auto Match is disabled and Allow Add is enabled, the Add button will be enabled in the Non-Currency Count screen. The one exception is deposits. The Allow Add option cannot be enabled for Deposits. Deposits are set to always Auto Match.

Sample Node Preferences > Transactions > Tenders > Requirements showing Auto Match/Allow Add checkboxes:

 UDFs for Inventory Styles
DevTrack ID #21194
A UDFs pane has been added to Inventory Style View. These UDF fields are the same available for items. These UDF fields are configured in Admin Console > Node Preferences > Merchandise > Inventory > UDF Fields. The Style UDFs may be edited from within Style View and applied to the currently selected style item or all items in the style.

Sample Style UDFs interface in Inventory:

In Transit Qty added to Inventory Item Details - Qty tab
DevTrack ID #22615
The following "in-transit" quantity fields have all been added to the QTY tab in inventory lookup>item details: SO Sent, SO Ordered, PO Ordered, PO Received, Transfer In Qty, Transfer Out Qty, TO In Ord Qty, TO Out Ord Qty, TO In Sent Qty, and TO Out Sent Qty.
Sample Inventory Item Details - Qty tab showing In-transit quantity fields:

Create All button in Style View
DevTrack ID #19281
There is now a Create All Items button in the style grid that becomes usable once the user has selected Edit mode.  This button assigns a 0 to each field in the OH Qty table in the Style grid.  Items are created in inventory for each such field once the style is saved.

Pagination for Adjustment Memo Items
DevTrack ID #23143
You can define different pagination settings for adjustment memo items in Admin Console > Node Preferences > Grid Formats. Select Adjustment Memo Lookup in the "Select a grid to configure" dropdown. The Results Per Page dropdown can be set to various settings between 10 and 1000. This enables you to control the number of records listed on each page of results. For example, the Results Per Page setting can be set to a higher or lower value depending on whether Prism is running on a desktop computer or a mobile device.
 
Source OH, Target OH on Transfer Slip Item Grids
DevTrack ID #23860
You can add Source OH and Target OH columns to Transfer Slip Item grids to easily view and compare on-hand quantities at the source and target stores involved in a transfer. If a user creating/editing a transfer slip changes the Source or Target stores, the values in the Source OH and Target OH columns will update.
To add the columns to transfer slip item grids, navigate to Admin Console > Node Preferences > Grid Formats. In the "Select a grid to configure" dropdown, select Transfer Slip Items.
Move the Source OH and Target OH columns from the Available list to the Selected list and reposition if needed, then save the changes.

Allocation Patterns for Transfer Orders
DevTrack ID #21210
You can define and apply allocation patterns for transfer orders (TOs). Allocation patterns for TOs work the same as allocation patterns for purchase orders (POs). You can apply a pattern to a specific item, an entire style or to the entire document.
Allocation patterns specify the relative order quantities for each store. When applying a pattern, Prism assigns quantities for individual stores based on the total quantity ordered. Prism does this by first summing the quantities entered in the allocation pattern for all stores and determining what percentage of the total has been allocated to each store. Prism then multiplies each store percentage by the total item quantity to determine the quantity of that item for each store. If you change the quantity on the TO, Prism recalculates the quantities ordered for each store according to the allocation pattern. If the Total Order Quantity is a multiple of the total quantity in the pattern, then each store receives the specified relative allocation. If the total quantity ordered is not a multiple of the allocation pattern, the remaining items are allocated to the stores one at a time.

New Allocation Pattern
On a TO in progress, navigate to the Apply Allocation Patterns dropdown and select New Pattern.

In the Add \ Edit Allocation Patterns modal enter a name for the pattern (20 characters maximum) and relative order quantities for each store.
Click Done when finished.
When the example pattern below is applied, store 0 will be allocated twice as many units as Store 2 and the other stores will not be allocated any units.
Sample allocation pattern:

Apply Allocation Pattern
List the items on the document.
Make sure the document is in edit mode.
Click the "Select Allocation Pattern to Apply" dropdown and then select the desired pattern.

 
With the pattern name listed in the dropdown, click the checkmark.
A menu for selecting how to apply the pattern is displayed. When applying an allocation pattern, you can apply the pattern to the selected items, the entire document, or the entire style. To apply an allocation pattern to selected items, first select the check mark icon on the left side of the item grid. To apply a pattern to an entire style, select the check mark icon for any member of the style.
 
The item allocations are updated according to the applied pattern.
Save the TO.

New Reason Preferences for Slips and Transfer Orders
DevTrack ID #21067
Define reasons for transfer slips and transfer orders in the following areas:

• Admin Console > Node Preferences > System > Reasons and Notes> Slips
• Admin Console > Node Preferences > System > Reasons and Notes> TO

Reasons are short text to explain why a document was created or provide other information for reports. Reasons are 30 characters maximum.

Add new TO/Slip reasons:
Navigate to Admin Console > Node Preferences > System > Reasons and Notes.
Select Slips or TO in the Type drop-down.
Click New Reason.
In the Create Reason modal, enter the Reason text (maximum 30 characters). The Description field allows users to enter a long description. By default, new reasons are Active. If the Default checkbox is selected, the reason will be entered by default in the Reason field when a new TO or Slip is created. (Note: The Shrinkable checkbox is only for quantity adjustment memos; it indicates the reason is used when reducing item quantity due to shrinkage. You can ignore the Shrinkable flag for TO/Slip reasons.)
Click Save & Exit.
The reason is added to the list and will be available when creating that document type.
Sample Slip reasons:

PO Lookup on Vouchers by Bill To Store, PO Store
DevTrack ID #23819
When creating a voucher, users can search for a purchase order by the Bill To Store or the PO Store. This change is especially useful for multi-store operations.

• Use the Bill To Store filter to search for POs by the store to which the merchandise is allocated (e.g., for drop-ship multi-store or marked for multi-store purchase orders).
• Use the PO Store filter to search for POs by the store where the merchandise will be sent (e.g., for drop ship single-store purchase orders).

Disable editing of Qty field on ASNs
DevTrack ID #24759
In Prism 2.2. and later, only the Orig Qty field (not the Qty field) is editable on ASNs. Previously, both Orig Qty and Qty were editable. This is important because when generating a voucher from an ASN, the voucher reads the Orig Qty field on the ASN, not the Qty field. Disabling editing of the Qty field helps avoid confusion and prevents users from mistakenly editing the wrong field on an ASN

Vouchers - Edit Pending permission
DevTrack ID #23005
The Vouchers - Edit Pending permission controls the ability of users to edit ASNs and Vouchers that are not updated. Retailers can assign the Edit Pending permission to those user groups (e.g., managers) that need to edit vouchers while other user groups (e.g., employees) can have permission to update vouchers but not permission to edit pending vouchers.
As part of this change, the following permissions have been removed: ASN VOUCHERS - EDIT PENDING, ASN VOUCHERS - EDIT FINALIZED, TRANSFER SLIPS - EDIT FINALIZED, and ADJUSTMENT MEMOS - EDIT FINALIZED

Consolidate Like Items on ASNs and Vouchers
DevTrack ID #24445
New preferences enable you to control consolidation of line items on ASNs, Vouchers and Slips:

• The Consolidate Like Items on ASNs and Vouchers preference (Node Preferences > Purchasing > Vouchers), when enabled, will consolidate line items with the same UPC (or ALU) when added to an ASN or Voucher.
• The Consolidate Like Items on Transfers preference (Node Preferences > Transfers > General), when enabled, will consolidate line items with the same UPC (or ALU) when added to a transfer slip.

If either preference is disabled, item quantities items with the same UPC (or ALU) will be listed multiple times if scanned multiple times on the original document. Default = Enabled
Note: Line items on purchase orders and transfer orders are always consolidated.
Sample Node Preferences > Purchasing > Vouchers preferences:

Update Order Cost when Making Vouchers
DevTrack ID #25042
(Note: This feature was released as part of 2.1.2 CCU)
A new preference prevents overwriting of Order Cost with Voucher Cost when making a voucher.

• Enable Update Order Cost when Making Vouchers to record Voucher Cost as Order Cost in Inventory each time an item is received on a voucher.
• Disable Update Order Cost when Making Vouchers to leave Order Cost unchanged when Voucher Cost differs from Order Cost.

The Update Order Cost when Making Vouchers preference is.in Admin Console > Node Preferences > Purchasing > Vouchers.

Show Total Discount Amount on Printed Receipts
DevTrack ID #24768
This section explains how to show the total discount amount that has been given across all items on a printed receipt. This is useful for seeing the total when multiple items on a receipt have received an item discount.
In Document Designer, navigate to the POS Transactions area and select a design to edit. The field to show the Total item Discount is in the document_item section and is called TOTAL_DISCOUNT_AMOUNT.
Sample 40-col Receipt design with Sold_Qty_Block expanded and TOTAL_DISCOUNT_AMOUNT field highlighted:

Widen the band called 'GroupFooter: Sold_Qty_Block.' , and then drag the TOTAL_DISCOUNT_AMOUNT in the band. Next, double-click on the field, and change the text to read:
[FormatPrice(SUM(,Item_Detail_1_Block))]
Then click OK. (Note: You may want to put a text label in front of the field.)

Add Foreign Cost Symbol to PO Doc Designs
DevTrack ID #20149
Users can add display the appropriate currency symbol when including FC Cost (foreign currency cost) on PO document designs.
For Items with a Vendor with a Foreign Currency Cost (FC Cost), it is possible to have the Foreign Currency Symbol displayed in the PO Document in the GUI and in the PO document designs. For Doc Designer, when you add the 'FC Cost' field to the PO design, you have to re-format the field.
To Reformat the FC Cost field in Doc Designer
After Listing the field on the design, double click it. You will see the text [poitem."FCCOST"]. Replace this text with [FormatCurrency2(,)]  (all characters included) and save it.
Sample FC_Cost field formatting:

Store Address and UDFs/Aux, Z-Out Read Count in Doc Designer
DevTrack ID #18637
Store Address1- Store Address6, ZIP Code, Phone1, Phone2, UDFString1- UDFString5 have been added to the Filter area. Retry Count field has been added to the header info.

Serial and Lot Number Fields on Tag Designs
DevTrack ID #23037
Serial and lot number information can be included on merchandise tag designs. In Doc Designer, navigate to the Merchandise Tags area and select a Document to edit.
In the selected design, drag-and-drop the following fields into the design as needed: LOTEXPIRYDATE,  LOTNUMBER, LOTTYPE, SERIALNO, SERIALTYPE
These fields are populated only when printing tags from documents (transactions), vouchers or slips.

Print Preferences for Standard, Return, Order Receipts
DevTrack ID #21566
You can define print preferences specific to standard receipts, returns and orders in Admin Console > Node Preferences > Hardware > Print Preferences, under the POS Transactions > POS Receipt parent area. Having sub-areas for standard receipts, returns and orders enables you to define settings specific to that type. For example, some countries require printing two copies of return receipts. Previously, users could set the number of copies at the parent POS Receipts level but this would be applied to all receipt types.
When printing a POS Transaction and consuming these child area preferences, Prism determines which child area to use based on transaction contents. If the transaction contains ONLY returns, Prism will use the Return area. If the transaction contains ONLY orders, Prism will use the Order area. In any other case (all sale, all void, mixed), Prism will use the Standard area.
Override Sub Areas
The "Override Sub-Areas" setting determines if the child sub-areas are editable in Admin Console and consumed during POS printing. If the Override Sub-Areas checkbox is enabled for the POS Receipt parent area, the child areas for Standard, Return and Order are read-only and not consumed during POS printing.
Sample Node Preferences > Hardware > Print Preferences:

Document Designer Subsidiary/Store Assignment
DevTrack ID #22695, 24111
You can assign document designs to specific subsidiaries/stores. This enables retailers to define (and update) designs at the POA level and then those designs will replicate to the desired stores. Previously, managers at the POA level would have to connect to each store and set the design at the local level.
The main screen of Document Designer includes a Store Assignment button. Click the Store Assignment button to display a modal for selecting which subs/stores can use the design.
New UI with Store Assignment button:

 PrismMQPublisher.exe
[Note: This program was released as part of a 2.1.2 CCU]
The PrismMQPublisher.exe program publishes records on the sending side of the data replication process. Previously PrismMQ.exe handled publishing, but PrismMQ.exe also handles consuming messages. Separating the producing and consuming functions into separate programs results in more efficient replication.

PrismMQService workflow:

Purge DaytoDay Replication History
DevTrack ID #17696
You can purge Day-to-Day replication history using new options in Admin Console > Connection Manager > Day to Day. If you click Purge All History, then all Day-to-Day replication history is purged. If you drill down to a specific listed server, there is a Purge History button that when clicked purges Day-to-Day history for that server only. This enables you to safely purge the day-to-day replication history for a single connection or all connections.
Sample Prism Dashboard Day to Day tab showing Purge All History button:

 
A confirmation is displayed. Click Yes to proceed or No to cancel.
 
Reprocess All Errors (for entire enterprise or single connection)
DevTrack ID #24438
In Connection Manager > Prism Dashboard, the Reprocess Errors button enables users to reprocess all errors for either the entire enterprise or specific connections. The Reprocess Errors button is disabled if there are no errors displayed in the list of connections. 
If there are errors, the Reprocess Errors button is enabled and clicking it opens a modal. In the modal, the user can click "Reprocess All" to reprocess all errors for all connections or select specific connections and click "Reprocess Selected." (Note: The Reprocess Selected option is disabled if there are no selections and the Reprocess All option is disabled if there are selections.) The time required will vary depending on how many connections and errors are being reprocessed.
 

RabbitMQ Queue Cleanup
DevTrack ID #23983
This section has information about deleting RabbitMQ queues at the POA and subordinate when removing a subordinate server from the enterprise. Before removing a subordinate server from the enterprise via the Web Tech Toolkit (TTK), verify the following RabbitMQ queues are empty:

• The subordinate's server's message queues at the POA.
• The POA's message queues at the subordinate.

Notes:
Deletion of the Day2Day and management queues from the RabbitMQ console for the subordinate may take up to 60 seconds (possibly longer).
Under certain circumstances the queues may not be deleted:

• RabbitMQ actions may prevent the queues from being deleted.
• In some cases, a deleted queue may be re-created because of another process.
• The replication producer may be loading the queue with messages, preventing the deletion.

Do not start/stop RabbitMQ or any other services during the deletion. Starting/stopping RabbitMQ or other services could permanently prevent the queues from being deleted.

Service Manager - Prism Support Apps
DevTrack ID #24643
Users can set log settings in Tech Toolkit Service Manager independently for the individual data replication programs that support the main PrismMQ replication program:

• PrismMQPublisher.exe
• PrismMQProducer.exe
• PrismMQConsumer.exe

These programs perform specific tasks to facilitate the exchange of data between servers. Previously, all replication-related applications fell under the umbrella of "Retail Pro Prism Replication Service" (i.e., PrismMQ) in terms of Service Manager logging configuration. Now users can easily change log settings for individual programs as needed. For example, users can temporarily set a program to log level 3 for troubleshooting.
Note: The Retail Pro Prism Replication Service listing in Service Manager (PrismMQ.exe) still controls the stop, start, restart and status commands.
Sample Tech Toolkit Service Manager showing Prism Support Apps at bottom of list:

Misc
Tracking No expanded to 30 characters - DevTrack ID#24608
The TRACKING_NO field in the DOCUMENT table has been expanded from 24 to 30 characters  to allow for 30-character TRACKING_NO entries in the INVOICE table imported from V9 using the Data Migration Tool.
Password expanded to 30 characters - DevTrack ID #24633 (released as a 2.1 CCU)
The PASSWORD field in the EMPLOYEE table has been expanded from 24 to 30 characters to allow for 30-character passwords imported from V9 using the Data Migration Tool.
Store Phone 1, Phone 2 expanded to 30 characters - DevTrack ID #24448
The PHONE1 and PHONE2 fields in the STORE table now have a max length of 30 characters. Previously, the max length was 15.
GetLastLeaveDrawerEvent
The following api methods were added to support enhancements in this release. More information can be found by logging into API Explorer and exploring the methods.
DocumentImport - DevTrack ID #21527, 21528
This DocumentImport method is used with the new Import Items on Documents feature.
GetOriginalTenders - DevTrack ID #21808
Customizations can use this method to make sure returns use the same tender as the original sale. This helps prevent fraud and allows for better management of payments. Restricting the return to the original tender typically means there will be fewer opportunities for the cashier to open the drawer and have access to cash. In addition, customers usually want the return to be in the original tender. For FC tenders it combines amounts based on currency sid.
PurgeD2DStatus - DevTrack ID#17696
The PurgeD2DStatus method is used with Purge Replication History enhancement described earlier in this document.  
ReprocessAllData - DevTrack ID #24438
The ReprocessAllData method is used with the "Reprocess Errors" enhancement described earlier in this document.
GetLastLeaveDrawerEvent - DevTrack ID#23164
The GetLastLeaveDrawerEvent rpc method is added for the "Suggest Z-Out Open Amount match Previous Day Leave Amount" enhancement for Z-Out reports. This method returns the SID of the last LEAVE drawer event matching the passed parameters.