18.104.22.168 What's New
This document has information about new features, enhancements, and changes to the user interface in Prism 22.214.171.124
- Auto Min/Max
- Auto PO
- Trade discounts
- Customer default charge terms
- Advanced Inventory Search
- Hide inactive proxies
- "Create Store" security permission
- Fees/Shipment preferences updated
- Plugin-specific logging configuration
- Tax Rules include Char and Message fields
- Pop-up message duration
- Total Qty on Order for Inventory Search
- Bypass Full-Control Serial Numbers, Lot Numbers on Adjustment Memos
- Vendors UI Changes
- Change Item Order in Promotion Item Filter
- Add Price Level Reward on Tiered Promotions
- Send PI sheets to other locations
- Import PI sheets into zones
- Fee permissions
- Item discounts on purchase orders
- Pause-Day-to-Day replication
- Customize replication processing order
- markdown resource for replicating markdowns
- PrismMQProducer workflow
- Control Replication of ASNs generated from Transfer Slips
- Streamlined Z-Out Reports
- Filter Foreign Currency Tenders on X/Z-Out Reports
- MySQL 8.0 Required
- Windows 11, Windows Server 2022 Support
Auto Min/Max calculates the desired Min (minimum) and Max (maximum) stock levels for Inventory items. Auto Min/Max helps retailers maintain adequate on-hand quantity levels for items relative to their demand (while avoid stockouts) while also considering budget and/or space requirements. The other auto tools (Auto PO, Auto TO, Best Replenishment) use these values to generate documents to re-order merchandise or transfer excess quantities to other stores. By default, the sales analysis will include all items; however, users can create an Item Filter as part of the formula to include only sales of items that meet the Item Filter criteria.
Sample Auto Min/Max formula:
Auto PO automates the creation of purchase orders needed to restock Inventory to the desired levels. Auto PO analyzes Inventory and uses each item's Min (minimum), Max (maximum) and current On-Hand Quantity values to determine whether a reorder is needed and how many units to order. The Auto PO configuration settings enable users to order enough merchandise to bring the quantity back to the Min quantity, to the Max quantity, or to any designated percentage in between the Min and Max.
Auto PO can run a PO analysis for a single store or for multiple stores. When auto-generating POs for multiple stores, the resulting POs can be generated individually for each store, or a single PO can be generated for the entire company.
Each purchase order generated by Auto PO includes a proposed list of items and quantities to order that can be reviewed and accepted or discarded at the user's discretion. Once the proposed items are approved, Auto PO generates the necessary POs. The document numbers of automatically created POs can be customized to help identify them for further review.
All POs generated are for a single vendor.
- Auto PO can optionally consider quantities needed to fill pending Sales and/or Transfer Orders.
- Auto PO enables users to define options and filters. The options and filters enable users to:
- Specify the items to include on the generated orders
- Select the fill level to attain based on each item's defined Min/Max levels.
- Select which order documents to analyze (when generating orders to fill pending SOs/TOs)
- Customize document numbers of auto-generated POs for easier identification.
- When analyzing Inventory to determine how many units to order, current On-Hand Quantities are always included, as well as quantities on active POs unless optionally excluded. The Auto PO analysis can also consider merchandise needed to fill active sales orders and/or transfer orders. By default, only items with an OH Qty less than the defined Min quantity will be included on the generated purchase orders (when taking into account order documents, if so configured; for example, an item may be under its Min Qty but a large quantity is due in on a purchase order). Auto PO configuration settings are saved under a user-defined name so the settings can be reused when needed.
Sample Auto PO configuration screen:
DevTrack ID# 22505
A trade discount is a reduction in Cost that a vendor gives a retailer when the retailer buys a certain item or group of items. This is based on an agreement between the retailer and the vendor.
To use Trade Discounts:
In Admin Console > Node Preferences > Purchasing > General: Cost to use on POs and Vouchers, select "Trade Discount." This selection means the Trade Discount % for the item is applied to the Vendor List Cost to calculate the Order Cost, which is used as the Doc Cost on purchase orders and vouchers.
Navigate to Inventory Item Details > Purchasing tab. Edit the Vendor List Cost, Trade Disc %, and Minimum Order Qty fields. The Trade Discount % is applied to each applicable item's List Cost to calculate Order Cost. If using trade discounts, Order Cost is automatically used on purchase orders and vouchers, and vouchers are unable to update an item's Order Cost. The amount of the trade discount varies depending on the item and vendor. By adjusting the "Minimum Order Quantity" the trade discount can be tied to quantity ordered.
Sample Inventory record showing Vendor List Cost, Trade Disc %, and Minimum Order Qty fields:
(Optional) Edit the Trade Discount % in the vendor record. The Trade Discount % entered in the vendor record, if present, is automatically entered for new items for that vendor. When you edit the Trade Discount % field for a vendor record, it has no effect on existing items.
- Trade discounts are different from Vendor payment terms that offer a discount.
- Trade discounts are usually given to retailers that order large quantities of a product and/or retailers with a good relationship with the manufacturer
- Vendor payment terms are defined in the vendor record and are based on payment plans with the vendor with no relation to order quantities.
Assign Default Charge Terms to Customer
DevTrack ID #20702
Users can now add default charge terms for customers in the Customer record on the Payment tab and those terms will be automatically entered on the tender screen when the customer is listed on a transaction with Charge as the Tender Type. Previously, charge terms had to be entered manually at POS. Being able to define default terms that are automatically applied at POS makes it easier to manage things like business-to-business (B2B) transactions.
The following fields for charge terms are available in the customer record:
|Discount %||The discount percentage to apply when the customer pays in full within the specified number of Discount Days. Integer or null.|
|Discount Days||The number of days when, if full payment is made, the Discount % is applied. Integer or null.|
|Net Days||The number of days when full payment is due (discount or no discount). Integer or null.|
Sample Customer record showing Default Charge Terms:
If the customer is entered on a transaction and the user select Charge as the Tender Type, the default terms are automatically entered.
Enhancements - General System
Improved Inventory Search
Note: This feature is not available in the POS or Physical Inventory areas
Prism's Advanced Item Search has been enhanced to allow users to add/edit/delete items. Previously, users could only look up items when searching Inventory, Now, when users are searching for an item they can add an item, edit an item, etc. This feature is especially useful when creating a purchase order to order an item that is not yet in Inventory. For example, a user starts a new purchase order to order the item. The search for the item Inventory does not return any results, so the user creates a new Inventory item on the fly. After the user save the item and returns to the document, the new or changed item is brought back to the document.
Sample Inventory Search screen with New, Edit and Activate/Deactivate buttons (enabling creation or editing of items from the lookup screen) :
On the Inventory Advanced Lookup screen, if the user clicks the New button, the UI is refreshed and a new item record is displayed. If the user clicks the Item Details button, the item's inventory record is displayed. At the top are fields for entering Doc Qty, Doc Cost and Doc Price for the current document. The rest of the UI is the same as one would see in Inventory when creating a new item.
Users can Cancel or Save as needed. After clicking Save, click Return to Document.
Sample Inventory Search screen with New, Edit and Activate/Deactivate buttons (enabling creation or editing of items from the lookup screen) :
- This feature is available when using Advanced Item Search on the following document types: Purchase Orders, Transfer Slips, Transfer Orders, Vouchers, ASNs and Qty/Price/Cost Adjustment Memos.
- Items can be given document quantity on the document
- New Items can be created and added to the document
- New Styles can be created and added to the document
- New DCS and Vendor Codes can be created
- The user's security permissions are checked if the user tries to create a new item, edit an existing item, or activate/deactivate an item
Hide Inactive Proxies
DevTrack ID #20298
The Proxies list (Workstation > HAL Settings) now shows the Active/Inactive status of workstations and includes a checkbox to enable filtering of the list to show only active workstations. This makes it easier to configure HAL Settings when many workstations are involved with some inactive workstations. A user can click the Show Active checkbox (default = selected) to filter the list. Previously, all Proxies were listed, active or inactive.
Sample HAL Settings showing "Show Active" checkbox:
"Create Store" Security Permission
DevTrack ID #21938
A new "Employees - Create Store" permission has been added to control the ability of employees to create stores. The permission is in the Admin Console group of permissions in Store Operations > Employees > Groups > Details. You can find the permission among the list of permissions by typing the word "store" in the search box.
Remember that Store Assignments for Employees take precedence over permissions. In practical terms, this means an employee may have the "Create Store" permission and be able to create a new store; however, that employee may not be able to see the store just created unless the employee's Store Assignments have the entire Subsidiary selected or the user is a sysadmin user.
Sysadmin users can see all newly created store.
If the employee's Store Assignments has the Subsidiary selected, any new stores added are automatically added to the visible Stores list. If the employee only has individual stores within a subsidiary selected, then each store must be enabled to become visible.
When the permission is enabled for a user's group, the user can click the "New Store" button in Admin Console > Node Preferences > Node Selection.
Shipping tab in Fees/Shipment preferences
The user interface for defining fee types and shipping methods has been updated. There now are separate tabs for Fees and Shipping. Previously, both fee and shipping types were listed on the same tab. This change makes it easier to work with fee types and shipping methods, especially when there are many types defined.
Navigate to Admin Console > Node Preferences > Transactions > Fees/Shipment.
Drill down to the desired Subsidiary or Store.
Click the Fees tab or Shipping tab.
To add a new fee type or shipping method, click the Add New button. A new blank row is added at the top of the list. Type the new fee or shipping type and click the check mark.
Sample Admin Console > Node Preferences > Transactions > Fees/Shipment:
Plugin-specific Logging Configuration
Users can set logging levels for individual plugins via the Prism Proxy "right-click" configuration settings. Previously, it was not possible to change log levels for individual plugins that might need a different level of logging detail.
The Configuration Settings screen has separate tabs for the Prism plugins that are installed with Proxy. To access the settings, start the Proxy, then right-click on the proxy icon and select Configure
Select the tab for the appropriate plugin and update the Log Level and any other log settings as needed. Settings configured for an individual plugin will override the default logging settings defined in PrismLogging.ini, as follows:
If no setting is made for a plugin, the plugin's log settings default to the settings made for Proxy.
The Proxy log settings themselves, as displayed in this UI, default to the "Global" settings in PrismLogging.ini until they are manually changed to different settings.
Tax Rules: Char and Message
The fields Char (or Indicator) and Message are added to the Tax Rules Grid in Admin Console > Node Preferences > Taxes > Tax Areas. These were a feature of Retail Pro 9 tax rules. Some countries have a tax requirement to show items that are taxable or non-taxable on the Receipt when both types are sold in the same transaction. The Tax Char (or Indicator) field is used to satisfy this requirement. In the RPS.tax_code_rule table, the fields are labeled Reference (Char) and Legend (Message).
Sample Edit Tax Rule screen showing Char and Message fields:
Pop-Up Message Duration
The Prism user interface occasionally displays pop-up messages (also known as toast messages) to inform the user of the success or error of an action, to issue a warning, or simply provide more information. To make the message go away, the user must click the message or wait for the popup message duration to expire, in which case the message will go away on its own. In Admin Console > Node Preferences > Themes & Layouts, users can customize the duration of the Success, Warning and Error pop-ups in seconds (default=five seconds). Reduce the default duration to make the messages go away sooner. A zero means pop-ups will remain displayed until the user clicks the pop-up.
To test the current default duration values, click the "eyeball" icon. A test pop-up for each message type is displayed and will go away when the defined pop-up message duration is reached.
Total Qty on Order for Inventory Search
DevTrack ID #21069
Detailed quantity information is now available for each item on a document via Item Details. The quantity information in Item Details show the item's current OH Qty at each store in the subsidiary. For example, in Advanced Item Lookup on a purchase order, select one of the items returned by the search results and then click Item Details.
In Item Details, click the Qty tab. The Qty tab will show all inventory quantity information for that item at each of the stores for the subsidiary.
Bypass Full-control Serial Numbers, Lot Numbers on Adj Memos
Serial and lot numbers can be full control or partial control. This is set by selecting either Full Control or Partial Control (or None) in the item's Inventory record in the Serial Type (or Lot Type) dropdown.
When a full-control item is entered on a document, the user must select (or enter) a separate number for each unit on the document. New permissions enable retailers to bypass full-control serial and lot number tracking on adjustment memos. This enables quantity adjustments even if the serial or lot number is unavailable (e.g., when a quantity memo decreases item quantity).
|Adjustment Memo - Allow bypass of full control serial number entry||When a user tries to update a memo before all numbers for full-control items have been entered, a prompt is displayed:
Not all full control serial numbers have been entered. Continue with update?
Only users who belong to a group that is assigned the "Allow bypass of full control serial number entry" permission can continue with the update.
|Adjustment Memo - Allow bypass of full control lot number entry||hen a user tries to update a memo before all numbers for full-control items have been entered, a prompt is displayed:
Not all full control lot numbers have been entered. Continue with update?
Only users who belong to a group that is assigned the "Allow bypass of full control lot number entry" permission can continue with the update.
Vendors UI Changes
DevTrack ID #22170
In Prism 2.1, the user interface for Vendor records has been updated. Previously, vendor records had four tabs: Account & Terms, UDF Fields, Lead Time and Fulfillment.
In Prism 2.1, the Lead Time and Fulfillment tabs are removed, leaving the Account & Terms and UDF Fields tabs. The Lead Time field is still available; Lead Time is moved to the Account & Terms tab. The Vendor Fulfillment feature is scheduled for a future release of Prism.
Sample vendor record in Prism 2.1 showing two tabs (Account & Terms and UDF Fields) with the Lead Time field on the Account & Terms tab:
Send PI Sheet to other Locations
DevTrack ID #22641
The Options button menu on PI sheets includes a "Send PI Sheet" option that enables users to send the Physical Inventory sheet to another installation (e.g., to the HQ location).
Clicking the "Send PI Sheet" option prompts the user to select the store where the PI sheet will be sent. The sheet will be packaged up for export and sent to the selected destination. The origin installation will have a sheet status of "Exported", which cannot be edited/updated/exported. The destination installation will have the active sheet, which can be worked fully from that location. Note: There will be an allowed possibility that the destination install has more than one active sheet per store, after receiving an exported sheet.
In the Physical Inventory area, select an active PI sheet. Click the Options button on the bottom menu.
Click "Send PI Sheet."
Select the desired installation and click Send. Note: Sending the PI sheet can take a long time, depending on the number of items, zones, etc. on the sheet.
Import PI Counts into Zones
Users can import counts for multiple zones at the PI sheet level. This simplifies the process of importing counts. When importing counts, Prism will add the counts to the correct zone. If a zone being imported does not yet exist on the PI, Prism will create the zone. Previously the Import button was only available on the individual Zone sheet and user could import counts for that specific zone only.
- Importing into multiple zones must be done at the PI Sheet level.
- Inside a zone sheet, users can only import into that zone.
Permissions for Fees
DevTrack ID #20109
Access to fee fields at POS can be controlled using the following permissions. These permissions apply only to users. In cases where a fee is being applied by the system due to some other action (e.g., Copy, Reverse, etc.), these permissions are not checked.
|POS - Allow Sales Fee||Allow group members to add a sales fee on a POS transaction.|
|POS - Allow Order Fee||Allow group members to add an order fee on a POS transaction.|
|POS - Allow Negative Sales Fee||Allow group members to enter a negative fee amount on a POS transaction.|
Item Discounts on Purchase Orders
Users can add a discount to individual items on purchase orders. This is useful when a vendor offers a discount on specific items. Previously, users could add a transaction-level discount to a purchase order (via the General tab in Purchase Order Details) but not a discount for a specific line item.
To add item discounts on purchase orders, first add the Discount and/Discount % columns to Purchase Orders Grid Formats preferences.
Navigate to Admin Console > Node Preferences > Grid Formats.
Select Purchase Order from the drop-down. Add the Discount and/or Discount % columns to the Selected and Default Visible lists.
Save the changes.
Sample Grid Formats preferences for Purchase Order showing Discount and Discount % columns moved to the Selected list and marked as "Default Visible":
To enter or edit a line-item discount amount or percentage on a purchase order:
List the item on the purchase order.
Click the item and then navigate to the Discount or Discount % column. Enter the desired value.
Save the purchase order.
Change Item Order in Promotion Item Filter
DevTrack ID #20436
When defining an item filter for a promotion, users can use the Move Up and Move Down buttons to change the order in which the items are listed. Changing the order in which the item filter items are listed can make it easier for users to review and edit the filters, especially when many items are included in the filter.
Be careful to use the correct "JOIN" operator (AND, OR) when changing the order. By default, when adding an item to an item filter, the "AND" operator is used. To use the "OR" operator, the user must click the OR checkbox in the item filter. For example, suppose the item filter has two item filter definitions like this:
1) [ [UPC, eq, 31] ]
2) [ OR [UPC, eq, 24] ]
If the user selects the second filter and then uses the Move Up button to move it up the list, then the user must also correct the JOIN operator to use the OR operator between those filters. If the join operator is not corrected after the Move Up action, the filter will be treated as [UPC, eq, 24] AND [UPC, eq, 31] and the promotion will never trigger (because an Inventory item can have only 1 UPC value). To correct the JOIN operator, select the item filter in the list, click Edit and then click the OR checkbox.
Add Price Level Reward on Tiered Promotions
DevTrack ID #19277
Users can add a "price level" reward (Reward Rules Discount Type = PL Price) on "Tiered" promotions. Previously, price level rewards were only available on BOGO promotions. When the discount type in Reward Rules is set to "PL Price," the discount values available for selection are the individual price levels. The price of the item at the selected price level is the discount that will be applied when the promotion is triggered.
Sample Tiered promotion with Reward Rules set to PL Price:
'markdown' resource for replicating price markdowns
Prism now replicates Markdowns separately from other Inventory information using a new 'markdown' resource. The markdown resource sends the Price Adjustment Memos created when a markdown is updated in Price Manager. Previously, replicating markdowns required sending the Inventory resource (a time-consuming resource to process). By creating a separate resource for markdowns, these price changes can be replicated more efficiently.
- Requires both the "markdown" and "adjustments" resources in the replication profile for both directions of the link (Store to POA/POA to Store).
- Adjustment memos created by a markdown, when replicated to stores/POA and applied to Inventory through Scheduler, are processed by PrismBackofficeService. This might slow down PrismBackofficeService. For example, suppose a user creates a markdown with 100,000 items and clicks Apply Now. This creates 100 Adjustment Memos (1000 items per memo) that will be replicated. When the other side of the connection (store) receives the adjustments, it will create 100 scheduled tasks to apply the markdown to Inventory.
Sample Profile screen in Connection Manager with markdown resource selected:
Customize Replication Process Order (PrismResources.ini)
DevTrack ID #22360
Users can override the default processing order for resources. By changing the process order, users can ensure that certain resources are processed before certain other resources.
Important! Before changing the default process order, be aware that the default process order has been determined to work well under most circumstances. Changing the order could have unintended consequences.
To modify the default processing order:
Use Notepad++ or other text editor to create a file named PrismResources.ini
In the PrismResources.ini file, enter a header and a list of resources with the desired process order for that resource.
Copy the PrismResource.ini file to the \ProgramData\RetailPro\Server\conf folder.
The only changes to the default process order will be those entered in the PrismResources.ini file. To return to the default processing order, delete the PrismResources.ini file.
Sample format for PrismResources.ini file:
- If the PrismResources.ini file does not exist or a value for a particular resource is not present, the default processing order is used. If making any changes, you are responsible for making sure any subordinate resources are also replicated. For example, if you choose to change the process order for Inventory, you will also have to change the process order for resources that are subordinate to the inventory resource (Processing order for packages and kits is inventory plus 5).
- Changing the processing order does not affect records already in the cache. Changing the processing order with the PrismResources.ini file changes the process order for the resource dictionary (used when a user creates a new replication profile) and all existing replication profiles. This can be viewed in the producer_cache/consumer_cache tables.
Replication of Offline Store Data
DevTrack ID #22755
When servers are taken offline, whether for maintenance or other reasons, it creates an interruption in the normal data replication process flow. For example, new inventory items or other changes made higher up in the hierarchy will not be processed in by the offline server. Likewise, any data created at that offline store server will not flow upstream to the POA and HQ. In the past, this situation resulted in sluggish data replication (why was replication slow in the past when servers were offline?)
In previous versions of Prism, pending messages for offline servers would accumulate and this would slow down replication for the other (online) stores. Changes were made so that the presence of pending messages for offline stores no longer affects replication for online stores.
The PrismMQProducer creates multiple threads for online and offline messages. The number of online threads is controlled by the D2DTHREADSPERSENDERCNT setting (default=5). The number of offline threads is controlled by the OFFLINE_THREADS_CNT setting (default=3).
The PrismMQProducer checks for any "clogged" queues. A queue is deemed clogged if the number of messages exceeds the QUEUEMESSAGELIMIIT (default=1000). The PrismMQProducer also checks if the queues have any records that also exist in the PRODUCER_CACHE_DESTINATION and PRODUCER_CACHE_OFFLINE tables. The PrismMQProducer will do this check every 60 seconds by default (controlled by the QUEUECHECKINTERVAL setting).
For each existing queue ("online" and "offline" records), a separate thread is created. This separate thread processes the number of records specified by the PRODUCERBATCHSIZE setting (default 1000). Thus, each thread serves its own queue.
Pause Day-to-Day Replication
DevTrack ID #18755
The Connections user interface now includes user interface elements that enable users to:
- Filter connections by description
- Filter connected only servers
- Pause day-to-day replication for a connection
- View a server's paused status
These changes help with scenarios like the following:
- A company is rolling out a set of stores. Due to lack of room in the store, the POS workstations are built and initialized in the company warehouse. In between the initialization and when the stores go live, day-to-day messages are generated and remain on the Rabbit MQ buss while the system is shipped to the store.
- A store goes down or loses the Internet connection. In many non-US countries, outages can be lengthy. While the store is down, day-to-day messages are generated.
These scenarios lead to orphaned federated queues and queues bloated with messages, causing issues with RabbitMQ.
Filtering Connections by Description
In the "Filter by Remote Desc" text box, start typing the connection name (defined in each server's Installation Defaults) to dynamically filter the list.
Filtering for Connected Only Servers
Select or clear the Connected Only checkbox to filter the list to include only machines in the enterprise directly connected to the local server.
Sample Admin Console Connection Manager (Connections tab) showing text box to filter connections by description, Connected Only checkbox selected, and the Pause/Resume button showing Not Paused:
The third column from the left is labeled Pause/Resume and it has a button in it that the user can click to pause replication to the selected server.
- When the selected server is not paused, the button reads Not Paused.
- When the selected server is paused, the button reads Paused at (Date of pause).
- New records created during time server is paused
- If any items, departments, vendors, documents, customers, or employees are created during the time replication to other servers is PAUSED, those records will not replicate normally after the server is UNPAUSED. Any such items, departments, vendors, documents, customers, and employees created while the connection is paused will need to be edited to replicate; upon editing the records, the records will replicate normally.
Control Replication of ASNs generated from Transfer Slips
When a user updates a transfer slip, Prism removes the quantities from the source store's Inventory. The expectation is that a user at the target store will create a voucher to receive the quantities into the target store's Inventory. To facilitate the receiving of merchandise at the target store, users can set a preference in Admin Console > Node Preferences > Transfers > General: "Upon Transfer Slip update generate: [ASN | Voucher | None]". By default, the preference is set to ASN, which means an ASN will be generated upon transfer slip update and prepared for replication to the target store (To Store on the transfer slip).
Two changes in Prism 2.1 work together to give retailers control over the replication of reference ASNs:
- ‘None' option added to "Upon Transfer Slip update generate:" preference
- Store Assignments feature added to Tech Toolkit
About the ‘None' option
The ‘None' option is new for Prism 2.1 and has been added to give retailers more control over the replication of reference ASNs generated from transfer slips. The use case for the ‘None' option is when the retailer wants the reference ASNs for transfers to be generated at an upstream installation, typically the HQ installation. When set to ‘None,' the installation where the slip is originally created and updated will not generate an ASN. Instead, the slip will be replicated up the enterprise tree until it reaches the controller that is "in charge" of the destination store for the slip.
Sample Admin Console > Node Preferences > Transfers > General showing "Upon Transfer Slip update generate:" setting:
About the Store Assignments feature in Tech Toolkit
A new "Store Assignments" feature in Prism Tech Toolkit enables users to select the installations for which this controller is "in charge" and for which the reference ASNs will be sent downstream.
An ASN will be generated if a transfer slip is received during replication and:
The slip has no reference document
The controller where the slip is received is the controller for the destination store (To Store on the transfer slip)
After the ASN is created at the HQ, the ASN will replicate throughout the enterprise unless the appropriate Advanced Filters are created for the receiving resource. In most cases, the desire is to replicate the ASN down the enterprise tree only to the destination store.
Log in to the Prism Tech Toolkit. For the desired server (e.g., the HQ), click the menu icon and select Store Assignments.
Select the individual store locations that are assigned to this local server. A server that does not have a store selected is not designated to a specific store.
When using the ‘None' option, it is important to add Advanced Filters to the receiving resource for the appropriate replication profiles. The Advanced Filters prevent the ASNs generated at the HQ from replicating throughout the enterprise.
Advanced Filters enable fine-grained control over which records for a specific resource are replicated. In the example, vouchers that have a VouClass field that is NOT EQUAL to 2 (‘cancelled') will be replicated; vouchers that have a VouClass of 2 will be filtered (not replicated). This type of Advanced Filter is used to send receiving documents upstream to the POA.
In the example below, receiving documents that have a Store Number equal to 1 will be replicated. This type of Advanced Filter can be used to send receiving documents (ASNs) downstream to the destination store.
Finalize Z-Out Reports
DevTrack ID #22622, 18223
Key changes to Z-Out reports in Prism 2.1 include:
Reports have a new "finalized" status that enables a two-step approval process (first the cashier closes the register, then the manager finalizes the report.)
A new "X/Z-Out - Finalize Z-Out" permission to control users' ability to finalize reports
Reconciliation screen displays "Short" amounts in red and "Over" amounts in green
When users enter the Z-Out area, any unfinalized reports are listed in the pane on the right side.
If a register is not yet open, the user interface will include an Open Register button.
The "Require Entry of Open and Close Amounts" preference has been removed in Prism 2.1.
Sample Structured Z-Out user interface showing Open Register button:
If the register is already open and a user wants to close the register, the user can select From the list of Z-Out records in the right pane, find and select the unfinalized Z-Out record to be closed. If many records are listed, use the filter elements to filter the list. The list can be filtered by Start Date/End Date or Status. Modify filter elements as needed and click Search. By default, only Z-Out records for the current Subsidiary/Store (as displayed in the upper-right corner) are displayed. Users can click the All Stores or All SBS checkbox to include records from other stores or subsidiaries in the search.
Highlight the desired record and click Close/Audit.
There is a Finalize & Print button on the bottom of the Reconciliation screen (replaces the previous "Print" button). Finalize & Print button provides a type of two-step approval for Z-Out reports. For example, one user group could have the X/Z-Out - Close Register while another group has the X/Z-Out - Finalize and Print permission.
Filter Foreign Currency Tenders on X/Z-Out Reports
When a user opens or closes a drawer or makes a disbursement, the list of currencies is filtered to display only those currencies marked as "Give" or "Take" in Admin Console - Node Preferences - Transactions - Tenders - Requirements. Previously the screens for counting currencies on Z-Out reports listed all currencies. Filtering the currency list makes it easier for users to add/edit counts for currencies. For example, a retailer may only use a few currencies. Removing unused currencies from the display reduces the risk of user error.
Sample Z-Out report currencies screen showing filtered list of currencies:
To mark individual foreign currencies for Give or Take, expand the Foreign Currency node to show the list of "active" foreign currencies (marked as Active in Admin Console - Global Preferences - Currency).
Important! If DOLLARS, the default Base Currency for Prism, is included in the list of foreign currencies in Tender Requirements (a known bug in Prism 2.1), DO NOT disable DOLLARS. If DOLLARS is disabled, then it will not be displayed in Z-Out reports or Disbursements.
Prism 2.1 supports MySQL version 8.0 and above. Legacy versions of MySQL supported in earlier versions of Prism (e.g., MySQL 5.7) are unsupported. Before upgrading to Prism 2.1, MySQL users should make sure their version of MySQL is 8.0 or above.
Windows 11, Windows Server 2022 support
Prism 2.1 supports Windows 11 operating system. Previously, Windows 10 and Windows Server 2019 were the most recent Windows versions supported