2.3.0.1304 What's New

PDF

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

Apache 2.4.58
This release requires Apache 2.4.58. Before installing Apache 2.4.58, uninstall any earlier version of Apache that is installed.

Select Centrals Server from Dropdown
DevTrack ID #26087
The address of the Centrals Server in Admin Console > Installation Defaults is now a drop-down that displays the list of servers joined to the enterprise. Previously, the address of the Centrals Server was a text field. This change avoids input errors where the user types the wrong IP Address or FQDN.

Customer Search Filter Changes
DevTrack ID #25208, 25817
Customer Lookup has the following changes:

• The NOT EQUAL operator is removed from the following Search By filters: Address1-6, Phone, Email, Postal Code
• Address1-6 filters now search through all customer addresses, not just the primary address.
• The Customer ID filter uses the EQUALS operator by default. Previously the default was CONTAINS. With the filter set to EQUALS, an exact match is returned in the search results.

Changes to Department Lookup filters
DevTrack ID #25645
The filters for Department Lookup include the following changes:

• The Use Qty Decimals filter is a YES or NO selection. Previously it was a RANGE field.
• DCS Code, Department, Class, Subclass and Created By are now all dropdowns with the operator set to EQUALS. Previously, these were all text-entry fields with the operator set to CONTAINS. This change helps avoid user input errors when editing filters.

Drawer Balance on New Disbursement form
DevTrack ID #25567
Associates can see the updated Drawer Balance when making a cash drop or other disbursement. The Drawer Balance shown on the Disbursement form updates based on the entered Amount of the disbursement. Previously, the Drawer Balance was not shown. Having the current Drawer Balance visible on the form can help the user decide to increase or decrease the disbursement amount. 
Sample New Disbursement showing drawer balance:

POS Associate, POS Cashier Flags on Employee record
DevTrack #20764
Employee records have two new flags (POS Associate and POS Cashier) that enable you to select which employees are included in the Associate and Cashier dropdowns on documents. Previously on POS transactions, all users assigned to the subsidiary were listed in the drop-down lists, including back-office users and administrators. This made it harder to find the desired employee. This change is especially useful for retailers who use Salesperson Incentive Fees (SPIF).

• New employee records will have both POS Cashier and POS Associate flags enabled.
• Existing employee records will have both POS Cashier and POS Associate flags enabled after installing the Prism 2.3 update. 

Sample employee record showing POS Cashier and POS Associate flags:

Copy Employee (User) Groups
DevTrack ID #23098
You can copy employee groups. Copying an existing group that offers a close match is a fast, easy way to create new groups. Previously, you had to define a new group from scratch. Now, you can copy an existing group that is the closest match and then modify the copy as needed.
Navigate to Store Operations > Employees > Group Management. 
Search for the desired group and select it in the Results pane. 
Click the Copy button on the bottom menu. 
 A new group record is displayed, ready for editing. The new group's default name is the same as the original group name but with "- Copy" appended. Make any needed changes to the permission assignments and save.

Customize "Enforce Strong Password Policy"
DevTrack ID #26014
You can customize the "Enforce Strong Password Policy" feature with the following new preferences:

Preference	Description
Password Minimum Length	Enter the desired minimum length of new passwords.
Password Required Special Character	If selected, new passwords must include a special character (!, @, #, $, %, &)
Password Requires Uppercase Character	If selected, new passwords must include an uppercase character.
Password Requires Number	If selected, new passwords must include a number (0-9).

These preferences give retailers greater control over password policies and help increase security. The preferences are enforced upon the next interval requiring a user to change their password.
Sample Node Preferences > Employee > Policy:

Licensing
Prism 2.3 enforces site- and seat-based licensing. Purchase the number of sites and seats required by your enterprise and then allocate those sites and seats among the controllers (servers) in the enterprise. 

• The number of sites limits the number of active stores in the enterprise. 
• The number of seats limits the number of users who can connect at one time. 

Prism Tech Toolkit includes a Licensing area where you activate licensing and allocate sites/seats. Open the menu for a controller and select Licensing. See the Prism Licensing topic for information.
To access Licensing, open the menu for a controller and select "Licensing":

View Item History
DevTrack ID#21283
The ability to search item history by document type has been added to the Options menu in Inventory Lookup and Inventory Item Details. The searches are hard coded for the selected inventory item but otherwise function like their respective document lookup areas, utilizing their grid formats settings for "Search By" filters and grid columns.
To view item history:
Use Item Lookup to find and display the item for which you want to view item history.
Click the Options button and click Item History.
 
(Optional) Enter a date range and other filter criteria. For example, you can select a specific Store or Document Type.
Click the View icon for the desired document.
  
The document is displayed. The document includes an "Item History" UI element so you can navigate back to Item History list, if necessary.
Sample Item History document showing Item History UI element at bottom of screen:

 
Replication of Item History
All transactional documents are replicated upstream through the enterprise connections. All data for the enterprise is consolidated at the Root Authority (RA). 

• Viewing Item History at the RA will show complete history for the item for the enterprise. 
• Viewing Item History at a child POA of the RA will show complete history for the item for that branch of the enterprise. History from other branches (other child POAs) will not be available.
• Viewing Item History at a child node (e.g., store server) will show item history for only that node. Item history for other nodes will not be available. 

Security
You can control employee access to the Item History feature by assigning the "Inventory - Access Item History" permission to groups.

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 following table lists the new permissions. 

Permission	Description
Adj Memos - Print Held	Allow group members to print held memos.
Adj Memos - Print Updated	Allow group members to print updated adjustment memos.
ASN - Print	Allow group members to print ASNs.
ASN - Print Held	Allow group members to print held ASN Vouchers.
Disbursements - Print Updated	Allow group members to print updated disbursement receipts.
Merchandise - Print Tags	Allow group members to print merchandise price tags.
PO - Print Held	Allow group members to print held purchase orders.
POS - Print Updated	Allow group members to print updated POS receipts.
Transfer Order - Print	Allow group members to print transfer orders.
Transfer Order - Print Held	llow 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 updated transfer slips.
Vouchers - Print Held	Allow group members to print held vouchers.
Vouchers - Print Update	Allow group members to print updated vouchers.

 
Margin % and Margin Amount columns in Grid Formats
DevTrack ID #25425
You can include Margin % and Margin Amt columns in Grid Formats for the following grids: Inventory Lookup, Inventory Search (document), Purchase Order, Voucher/ASN, Voucher/ASN - PO items, Slip Items, Adj Items and TO Items.
To add the Margin % and/or Margin Amount columns to grids:
Navigate to Admin Console > Node Preferences > Grid Formats. 
Select an area to configure from the drop-down (Inventory Lookup, Inventory Search (document), Purchase Order, Voucher/ASN, Voucher/ASN - PO items, Slip Items, Adj Items or TO Items).
In the Show Columns area, move the Margin % and/or Margin Amount columns from the Available list to the Selected list and reposition as needed within the list. 
Save the changes and log out. Clear the browser cache and log back in. The columns are now visible.

iOS Devices - Convert camera-scanned UPC-E barcodes to UPC-A
DevTrack ID#25910
There are two variations of Universal Product Code (UPC): UPC-A and UPC-E. UPC-E is a shorter version of UPC-A. The Prism iOS Settings screen now includes a "Convert UPC-E to UPC-A" option. When "Convert UPC-E to UPC-A" is enabled, numbers in UPC-E format will be converted to UPC-A format by adding zeros. When disabled, numbers in UPC-E format will not be converted to UPC-A. Enabling this setting ensures UPCs scanned by the device's camera are in the desired format.
Sample iOS Setting screen:

  
Restrict Order Item Rows to Single Quantities
DevTrack ID #25228
The "Restrict Order Item Rows to Single Quantities" preference, when enabled, ensures that when a user lists an order item on a transaction, that order item can only have a quantity of 1. The "Restrict Order Item Rows to Single Quantities" preference is a child setting to "Restrict transactions to a single item type" and is only available when "Restrict transactions to a single item type" is enabled (by default, "Restrict transactions to a single item type" is disabled). 
 Use Case - Avoid Partially Fulfilled Orders with Tax Rate Mismatches
A use case for the "Restrict Order Item Rows to Single Quantities" is to avoid having partially fulfilled orders that could result in mismatches between the tax rate on the original order and the tax rate at a later point.
For example, an order is created that has one or more items and a full deposit is taken. After the order is finalized, the customer wants to increase or decrease item quantity. However, in the interim, the tax rate has changed. If the existing order item has been partially fulfilled and the tax rate has changed since the order was created, we cannot change the tax rate on the order item.
In this type of situation, if the "Restrict Order Item Rows to Single Quantities" preference is enabled, the order item quantity can only be fulfilled or changed to zero; it can never be partially filled (assuming no decimal quantities). The quantity of the line item can be changed to zero because in that case the change in tax rate has no impact.
When "Restrict Order Item Rows to Single Quantities" is enabled:

• If using Item Lookup to add an item as an order item, the item will not consolidate with existing rows.
• If the quantity of an order item is manually edited, the row is automatically split into single quantity rows.

Show Deposits Used in Deposit Details
DevTrack ID #25356
When viewing Deposit History for an order, the deposit list includes both deposits taken and deposit used. Previously, the list only displayed deposits taken. This helps you view and track the full deposit history. Deposits used are shown as a negative amount.
In addition, the "Deposit Available Total" has been added to the bottom of the Deposit History Modal to show the total amount of any remaining deposits.
Sample Deposit History modal showing a negative amount for deposits used:

Improved Workflow for Fulfilling/Closing Orders
DevTrack ID #24385
When fulfilling or closing an order, users can also print a copy of the order. Previously when fulfilling or closing an order users were returned to the default New Transaction form upon transaction update, at which point they had to use Transaction Lookup to find the order and print it if desired. This change saves time and makes the process of printing orders easier for Associates.
Now, when fulfilling an order, upon transaction update users will first see a prompt asking if the order should be closed. 
 
Clicking Yes displays a second modal where users can click Confirm & Print to close and print the order (Clicking OK will close the order without printing.)
Sample Close Order modal with Confirm & Print button:

 
Add PI Counts for Multiple Items from Item Lookup
DevTrack ID #25485
You can add counts for multiple items from within Item Lookup on a PI sheet. Previously, Advanced Item Lookup on the Add Counts tab did not allow for entering a quantity for multiple selected items. This change saves users time when entering PI counts.
On the Add Counts tab of a PI sheet, click the Item Lookup button.
Enter the desired search criteria and click Search. 
In the Results pane in the Add count column, enter the count for individual items. Click Close to return to the Add Counts tab with the selected item counts. 

 Create PI Sheets per Store
DevTrack ID #26015
You can create multiple active PI sheets, provided each active sheet is for a different store. The main PI screen that lists PI sheets now includes a dropdown for selecting a Store Name. Previously, the PI Sheet list was hardcoded to display the PI sheets (if any) for the current logged-in user's store. Users had to delete the current active PI sheet before creating a new active PI sheet. 
You are still limited to one active PI sheet per store. When you create a new PI sheet, Prism will check to see if an active PI sheet already exists for the store. If an active PI sheet already exists for the store, a message explains that if you proceed, the existing PI will become inactive.
Sample list of PI sheets showing Store Name drop-down:
  
Item Lookup by SN/LN on PI Sheets
DevTrack ID #23063
You can scan (or type) an item's serial or lot number to quickly add the number to a PI sheet. On the Add Counts tab in the Item Lookup field, scan or type the serial or lot number. If a match is found, the item is added to the PI sheet. Previously, you had to use Item Lookup to search Inventory for the desired serial/lot number items. This change makes it easier to add serial/lot items to a PI sheet.
Note: To look up items by SN/LN on PI sheets, you must enable the preferences "Enable Serial Number Entry" and "Enable Lot Number Entry" in Admin Console > Node Preferences > Merchandise > PI Sheet.

• If the quantity entered is "1," then the serial number item is added to the Add Counts list with a quantity of "1." 
• If the quantity entered is greater than "1," the Serial Number Entry modal is displayed so you can enter numbers for the other quantities.

Sample PI sheet > Add Counts tab > Item Lookup field:

Import Serial Numbers into PI Sheet
DevTrack ID #21383 
You can import serial and lot number information when importing items onto a PI sheet. 
When the "Enable Serial Number entry" and "Enable Lot Number entry" preferences are enabled (Admin Console > Node Preferences > Merchandise > PI Sheet), the following fields are available:

• Fixed-length: Serial Start, Lot Start.
• Delimiter: Serial Column, Lot Column. 

Sample Import Map with elements to define the start position of serial/lot numbers:
  
View Available Qty in Inventory Advanced Lookup
DevTrack ID #23338
You can include the Available Qty column to Inventory Lookup grids. This enables users to check available quantities when searching inventory in addition to when adding an item to a document. Previously, availability was only checked at the point the item was added to the document. 
To add Available Qty to Inventory Lookup grids, navigate to Admin Console > Node Preferences > Node Selection > Grid Formats.
In the Show Columns area, move Available Qty from the Available list to the Selected list and reposition if needed. 
Sample Node Preferences > Grid Formats for Inventory Lookup:
 
Viewing Available Qty in Inventory
You can also view Available Qty for individual items in Inventory > Item Details > Qty tab. 

Max Take Amount for Tenders
DevTrack ID #25561
Tender Requirements preferences now include a "Max Take Amount" setting that limits the total amount allowed for a particular tender type on a single transaction. For example, you can restrict an individual store to not take more than $100 in cash on a single transaction. 
At POS, Prism adds the Give amounts for a tender type and subtracts the Take amounts for that tender type. 

• If the resulting amount exceeds the Max Over Tender and the Max Take Amount, a message is displayed that explains the error and shows the maximum allowed amount.
• If the amount is under the Max Take Amount but over the Max Over Tender amount, then an overtender error is shown. 

The ability to set the Max Take Amount is a legal requirement in certain countries. You can configure the setting at the store level as some countries do not have such restrictions.
Sample Node Preferences > Transactions > Tenders > Requirements:

Restrict Return Tenders to original Sale Tenders
DevTrack ID #25396, 21808
The "Restrict Return Tenders to original Sale Tenders" preference, when enabled, restricts the tender types and amounts on item returns to what was taken on the original sale. This gives retailers greater control over returns and aligns with the typical desire of customers to be refunded in the same tender as the original sale. You can configure this preference at the Subsidiary and Store level.
Notes

• Each referenced return can use any tender or tender amount from the original sale. 
• The Tender Type list will show only tender types allowed by Tender Requirements preferences and that also exist as taken tenders on the original transaction. 
• If the "Allow Store Credit Tender" child preference is also enabled, store credit will be allowed (if store credit is enabled in Tender Requirements preferences).
• Both the "Restrict Return Tenders to original Sale Tenders" and "Allow Store Credit Tender" preferences are disabled by default.
• When "Restrict Return Tenders to original Sale Tenders" is enabled, all items must be returned; partial returns are not allowed. 

POS - Override Return Tender Restriction permission
The "POS - Override Return Tender Restriction" permission controls the ability of users to override the restriction put in place by the "Restrict Return Tenders to original Sale Tenders" preference. For example, sometimes a refund cannot be made to the original sales tender (like an expired credit card). In such a situation, a manager or other group member can perform an override. 
At the bottom of the Tender Type selection list is a button labeled "Override." A manager or other user with the "Override Return Tender Restriction" permission can click the Override button and enter credentials to remove the restriction. This presents the user with an updated tender type list as if the restriction was disabled (but still subject to the tenders selected in Tender Requirements). 
Sample Node Preferences > Transactions > General page with "Restrict return tenders to original tenders" preference:

Add PDF Printing for Backoffice Documents
DevTrack ID #25214
You can email a PDF of purchase orders (POs), Advanced Shipping Notices (ASNs), Transfer Slips and Vouchers. Previously, the ability to Print to PDF was only available for Receipts. This change makes it easier to send back-office documents to whoever needs them.
Navigate to the Prism Admin Console > Node Preferences > Hardware > Email Server Preferences area.
In the Email Attachment Type field, select HTML or PDF.

• If you select PDF, Prism attaches the document as a PDF file to the email.
• If you select HTML, Prism embeds the body of the email as HTML.

If using the email feature, be aware that is the end user's responsibility to enter the correct SMTP server information.
Tag Copy Defaults
DevTrack ID#20844
Print Preferences for Merchandise Tags enable you to define the default number of tags to print in individual areas of Prism. This helps avoid users printing more or fewer copies than desired. For example, you might want Associates at POS to only print tags equal to the Doc Qty (to replace a damaged or missing tag). You can set tag copy defaults for the following areas: POS Transaction, PO, TO, Voucher, Inventory (Doc Qty disabled), Adjustment Memo, Slip, and ASN. The setting in Print Preferences sets the default; however, users can change quantity at run-time, if needed.
In Prism, navigate to Admin Console > Node Preferences > Hardware > Print Preferences. Select Merchandise Tags. In the Tag Copy Defaults area, select an area from the drop-down and configure tag copy defaults as needed. Each document defaults to Doc_Qty, Inventory defaults to OH_Qty.

Setting	Description
On-Hand Qty	If selected, the number of tags printed for an item will be equal to the item's OH Qty in Inventory. For example, if OH Qty is 50, then 50 tags will be printed.
Document Qty	If selected, the number of tags printed for an item will be equal to the item's Doc Qty.
Copies	If selected, enter the desired number of tags. The number of tags printed for an item will be equal to the number entered in the text box

Sample Print Preferences showing Tag Copy Defaults:
  
Preset Coupons to Validate Promotions
DevTrack ID #20673
When validating promotions by coupon code, you can designate individual coupon codes as "presets." Preset coupon codes are available via drop-down at POS; there is no need for the Associate to scan or type the code. Preset coupon codes are especially useful for offering common discounts like "student," "senior," and "military." 
Notes

• This feature only applies to non-serialized coupons.
• If a coupon code is not designated as a preset, the coupon can still be added to the transaction; however, the Associate must type or scan the code. 

Sample Validation Rules for Coupon Promotion with Preset checkbox:

Selecting a Preset Coupon at POS
At POS, click the Coupons button on the main transaction form. If presets are available, they will be available for selection from the drop-down in the Coupons modal. Select the desired code and click Add. Click Close to exit the modal.
If no presets are available, the UI will display "Preset coupons - No Records Found." You can still type or scan a coupon code (and then click Add) to add the coupon.

Filter PO Lookup by Unfilled Percentage
DevTrack ID #24022
In PO Lookup, you can filter and sort the list by Unfilled Percentage. This enables you to easily see those orders that have the greatest Unfilled Percentage. To filter and sort the list of purchase orders by Unfilled Percentage, you must add the column to Purchase Order Lookup grid formats.
To add Unfilled Percentage to Grid Formats for PO Lookup:
Navigate to Admin Console > Node Preferences > Grid Formats.
Select PO Lookup from the Area dropdown.
In both the Allow Search By and Show Columns areas, move the Unfilled Percentage column from the Available list to the Selected list. Reposition the elements as needed.
Save the changes.
When using Unfilled Percentage as a Search filter, enter a percentage range to filter the list to include only purchase orders with an unfilled percentage that falls within the range. You can then sort the list of search results by clicking the Unfilled Percentage column header in the Results pane. 
Sample PO Lookup grid formats with Unfilled Percentage in the Available list:

Edit Fees and Taxes on Former Voucher
DevTrack ID #22097
Users who use vendor invoices can edit the shipping fees and taxes on a former voucher (provided the total voucher amount does not exceed the vendor invoice amount).
This change is especially useful when fees or taxes are unknown when items are received. For example, when there is only a delivery docket that lists item quantities. Now when the user receives the vendor invoice that has the complete information - including fees and taxes - the user can update the voucher with the correct information, helping to maintain correct inventory valuations.
To edit fees and taxes on a former voucher, you must be using vendor invoices (i.e., the Enable Vendor Invoices checkbox must be selected in Admin Console > Node Preferences > Purchasing > Vouchers). 
Edit Fees and Taxes on a Former Voucher
Use Voucher Lookup to find and display the voucher.
Click Edit.
Navigate to Voucher Details and edit the freight amount, fee amount, discounts, or taxes as needed and save the changes.
Note: If the voucher is referenced on a vendor invoice, you can't add a fee or tax that causes the Voucher Total to exceed the Vendor Invoice amount.

Discount individual items on a voucher
DevTrack ID#25005
You can apply a line-item discount to individual voucher items by editing the item's Disc % field. Updates to the Disc % update the item's Doc Cost and vice versa. This change is especially useful when vendors offer one-off discounts to retailers because of missing items or damaged quantities on a voucher. Previously, users could edit the Disc % of a PO line item but not a voucher line item. 
Add Discount and Discount % Columns to Voucher Item Grids
To discount individual items on a voucher, add the Disc % column to Voucher/ASN grids in Admin Console > Node Preferences > Grid Formats. Reposition the Disc % element to the desired position (e.g., next to Cost so you can easily see how the Disc % changes Doc Cost).

Filter Voucher/ASN Lookup for Transfer vs. Receiving Vouchers
DevTrack ID #20842
You can filter Voucher/ASN Lookup to display documents created for transfers or those created for receiving merchandise from a vendor. This makes it easier to find the desired documents.
Add the following filter elements to Grid Formats and search ASN/Voucher Lookup using a combination of the fields.

Column	Description
Class	The Class indicates the type of voucher: 0=Voucher, 1=Pending Voucher, 2=ASN
Slip	True=The ASN/Voucher was created from a transfer slip. False=The ASN/Voucher was not created from a transfer slip.
From Store Name	The source store name.

To add Class, Slip and From Store Name to the filter list, in Admin Console > Node Preferences > Grid Formats, select Voucher/ASN Lookup from the drop-down. In the Allow Search By and Show Columns areas, move the Class, Slip and From Store Name columns from the Available to the Selected list and reposition the elements if needed. The Allow Search By selections determine the filter elements available for selection in Voucher/ASN Lookup. The Show Columns selections determine the columns used to display Search results.

Restrict Ability to Sell Zero Quantity Serial Number Items
DevTrack ID#21485
The "Prevent sale of Full Control Serial Number items with zero quantity" option in Serial Number Tracking preferences prevents the sale of serial numbers when there is no stock. If enabled, a full-control serial number item must have a positive OH Qty value for the number to be sold. Adding a full-control serial number with an OH Qty of zero results in a red toast message explaining the number is not available and the entry will be cleared. 
Sample Node Preferences > Transactions > Serial and Lot Numbers in Prism 2.3:

Sort Sublocations on Adjustment Memos
DevTrack ID #25715
You can sort the list of sublocations on adjustment memos by the following information:

• Sublocation Code
• Sublocation Description
• Orig Value
• Adj_Value

The ability to sort is helpful when the enterprise has many sublocations to manage.

Sample Quantity Adjustment Memo showing Sublocation columns as sortable:

Transfer Items between Store Sublocations
DevTrack ID #25008
You can use transfer slips to move OH quantities between store sublocations. Previously, users had to create adjustment memos to move OH quantities between store sublocations. 
Transfer slips include a Transfer Type dropdown that toggles between "store-to-store" and "sublocation-to-sublocation" (when sublocations are enabled).
Sample Sublocation Transfer screen showing Transfer Type drop-down set to "Sublocation-to-Sublocation:

Notes

• The Transfer Type dropdown is only editable if "Use Sublocations" is enabled (Global Preferences > Sublocations). 
• When transferring items between sublocations, Prism will automatically create the needed adjustment memos. 
• Created Date, Last Edit Date, ETA Date, Post Date and Status fields are now displayed at the bottom of the slip form instead of the top.
• Instead of the previous From Subsidiary and To Subsidiary fields, the UI has From and To fields which display either the From Store/To Store or From Sublocation/To Sublocation depending on the selected Transfer Type

Line Item Count on Transfer Orders
On the General tab in Transfer Order Details, you can view a count of the line items on the document. 
 
Auto TO Configuration Drop-down
DevTrack ID #25126/25158
The Transfer Review screen in Auto TO includes a Configuration drop-down at the top of the screen that enables you to select the desired configuration to review. When you select a configuration from the dropdown, only the transfer orders proposed by that configuration are shown. This change means that Auto Transfer can now be used by more than one user at a time on the same Prism install.

Counts of Transaction Types, Item Types on X-Out Designs
DevTrack ID #22790
X-Out report designs can include counts of the transaction types (sale, return, order) and item types. This enables you to see how many returns were made for example, or how many orders were placed. 
On X-Out designs, the INVOICECOUNTS node on the data tab includes the following elements: SALES, RETURNS, ORDERS, CASH_DROP, PAID_IN, PAID_OUT, OPEN_DRAWER, ITEMS_SOLD, ITEMS_RETURNED, ITEMS_ORDERED and ITEMS_VOIDED.
To add the INVOICECOUNTS fields to X-Out document designs:
1.    Launch Document Designer and log in.
2.    Select X/Z-Out in the Area drop-down.
3.    Select the desired design (e.g., X-Out 40-col) and click Edit.
4.    On the Data tab on the right pane, expand the INVOICECOUNTS node.
5.    Add the desired elements to the design. Reposition as needed. Save the changes. 

• A document that contains at least one sale item is classified as a SALE.
• A document that contains only order items is classified as an ORDER.
• A document that contains at least one return item but not a sale item is classified as a RETURN.

Require Daily Register Closure/End of Day time
DevTrack ID#22098
New preferences have been added for Structured Z-Out reports:

• Require Daily Register Closure
• End of Day

Refer to the following table for information about these preferences.

Preference	Description
Require Daily Register Close	If the specified End of Day time elapses, the system starts a drawer close that must be completed before the drawer can be reopened. Default=Disabled.
End of Day	This is the time of day that triggers the "Daily Register Close" action. Enter the desired time in 24-hour format. Default=23:59

Sample Node Preferences > Reporting > X/Z-Out:

Database Table Changes
POS_CASHIER, POS_ASSOCIATE added to EMPLOYEE table (DevTrack ID #20764)
The POS_CASHIER and POS_ASSOCIATE flags in the EMPLOYEE table enable filtering of the drop-down list of Associates on documents. 

UNFILLED_PERC added to PO table (DevTrack ID #24022)
The UNFILLED_PERC column stores the document's unfilled percentage, taking into account quantities ordered and quantities received on vouchers that reference this PO.

PRESET_COUPON added to PCP_PROMOTION_VALIDATION table (DevTrack ID#20673)
This flag indicates if the promotion validation includes a preset coupon. 0=not a preset coupon, 1=preset coupon

API Methods
The following api methods are added in 2.3:

GetActiveSubscriptions (DevTrack ID#25916)
The GetActiveSubscriptions method returns the Subscription list ordered by resource name.

GetOriginalTenders (DevTrack ID #25396)
The GetOriginalTenders method returns all tenders used on original documents referenced on return items. For foreign currency tenders, the method combines amounts based on currency sid. No Payload is required.

PromoFilterElementUpdate (DevTrack ID #25871)
The PromoFilterElementUpdate backoffice api method saves updates to promotion item filters more efficiently when the item filter has many items (e.g., more than 1000).

PCPromoGetPresetCoupons (DevTrack ID#20673)
The PCPromoGetPresetCoupons method returns any preset coupons for a transaction. The user can then select the desired coupon code from the list.

ValidateCoupon (DevTrack ID #24746)
The ValidateCoupon method checks if a given coupon code can still be used or if the coupon code has already been used as many times as allowed. If the entered coupon code has already been used as many times as allowed, a message is displayed to the user.

PIModifyQtyByPOSLookup (DevTrack ID #23063)
The PIModifyQtyByPOSLookup method takes the entered lookup string and returns item sid(s). This method searches for serial/lot numbers also, if entry of SN/LN on PI is enabled in preferences.