What's New in 2.0.0.391

PDF

This topic will have information about new features added in Prism 2.0.0.391:

• Prism Licensing
• Inventory Management in Prism 2.0
• Sublocations
• Track Changes when Editing Style Grids
• Availably Qty column in Inventory Lookup
• Assign Item/Style Images in Prism
• Manage POS Shipping and Fees
• Schedule Deletion of Promotions
• Update Physical Inventory in Prism
• PI Sheets with up to 500,000 Items
• Manage Loyalty Levels, Programs in Prism
• Assign Country to Customer
• Search Customers by "Created By" Employee
• Sold Qty on PO Advance Item Lookup grids
• Allow Voucher to Update Inventory Prices
• Store Code, not Store Number in UI    
• Centrals Service Version 2
• Permissions for Printing Held documents
• New Fields on Store Records
• SRO Tool
• Rename Server tool Integrated into Web TTK
• TTK Server Menu Enhanced Layout
• INSTOREZIP on Transfers Doc Designs
• New Transfer Order Permissions
• Store Filter Enhancements in Transfer Verification
• New/Removed Resources
• Admin Console Permissions

Prism Licensing
Prism 2.0 is a licensed product. During installation of Prism 2.0, users are required to enter a valid Client ID and License Key (Software Assurance (SA) code). This means that the client must purchase Prism licensing and SA must be current.
Purchase Prism Licensing
The screenshot below shows licensing for Retail Pro Prism Standard. The Client ID that users must enter when installing Prism 2.0 is shown on the licensing screen.  (masked in the screenshot below).
The second piece of information that must be entered when installing Prism is the SA Code (License Key). The SA Code can be found in the Activation Details area of the licensing web site.
During the Prism Server installation, after the user clicks "I accept the agreement" and clicks the Next > button, the Prism License Check will begin.
Enter the Client ID and License Key (SA Code) and click Validate.

 After the Client ID and License Key (SA Code) have been validated, the following information is displayed:
"Licensed to "
"Valid Until "
Click the Next > button to proceed with the rest of the Prism server installation.
Command Line Parameters for Licensing during Silent Install
When installing Prism silently via the command line, the following parameters are required to pass licensing information. (For information about silent install and the other command line parameters, see the Prism 2.0 Getting Started Guide.)

Example:
C:\Win32PrismServerInstaller.exe /VERYSILENT /SUPPRESSMSGBOXES /LOG: "c:\Win32PrismServerInstaller.log" /ClientID=12345 /RegKey="aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpP"

Inventory Management in Prism 2.0
DevTrack ID #20623
In Prism 2.0, Inventory must be managed via replication profiles. Configure profiles correctly so that the root authority pushes Inventory changes downstream to intermediate POAs and store servers in the hierarchy. In previous versions of Prism, RIL, by virtue of its role as the root authority (RA), was responsible for inventory updates. In Prism 2.0, each store will have its quantities updated by its documents. Any parent in the enterprise those documents are replicated to will also update its quantities for the origin site based on those documents. Depending on how replication is set up this could be to a site's direct POA, or all the way to the RA.
Depending again on how the enterprise is set up, inventory may be replicated down from a POA or RA to the site, and that data would overwrite the data in the store.\

Sublocations
DevTrack ID #20286, 4026
The Sublocations feature gives a store or warehouse the ability to divide the stock into physical or logical partitions ("sublocations") smaller than a single inventory and allow this stock to be tracked by quantity to a specific partition.
Sample Use Cases for Sublocations
Store Sublocations: A single physical store (brick and mortar) may separate their inventory in a few places, such as Sales Floor, Back Room, Display, etc. Inventory is moved between these sublocations, as needed.
Warehouse Sublocations: Retailers may want to minimize in-store inventory carrying costs due to the high cost of real estate in an area. Multiple stores in a region may have merchandise delivered to a central warehouse in the area with ownership of the merchandise taken into each individual store's inventory immediately upon arrival at the warehouse. The warehouse aisles, racks, and bins are defined as sub-locations of individual store inventories.
"Logical" Sublocations: Inventory may be physically present and still accounted for, but also need to be removed from the store's available inventory. Inventory can be transferred to these sublocations and later handled by adjustment, Return to Vendor, etc. Another use for logical sublocations is when inventory is loaned to someone such as when jewelry is loaned to a celebrity or to a tester/reviewer.
Sales Sublocations: Some stores may sell the same item at two different prices. A possible example would be a change in packaging, where the item is still the same SKU. The retailer may put the older packaging items on sale and use a clearance rack. This rack would be defined as a sublocation, which would be assigned a clearance Price Level.
Sample new sublocation:
 
Refer to the Prism 2.0 Sublocations document for more information.

Track Changes when Editing Style Grids
DevTrack ID #19521
A checkbox labeled "Track changes" is included in the Inventory > Style View > Style Grids area. When the Track changes checkbox is selected, changes made in style grid cells are color-coded. If unchecked, all cells are shown without color-coding. This feature is especially useful for keeping track of which cells have been edited when working with styles with many sizes/attributes.
The Track Changes checkbox is only editable when the user is in Style Details and in edit mode.

Availably Qty column in Inventory Lookup
DevTrack ID #20838
"Available Qty" is now available as a view column in inventory lookup.

Assign Item/Style Images in Prism
Users can now assign up to 10 item and 10 style images via the Prism Inventory UI. Previously, users could not assign images to items or styles via the Prism Inventory UI; users had to use the Image Export tool to export images from RIL (or Retail Pro 9) and then move the images to a Prism server. The ability to add/edit item and style images in Prism helps make Prism 2.0 a standalone product.
To add an item or style image:
Display the item in Item Details or the style in Style Details and then click the Edit button.
Navigate to the image placeholder (it looks like a box) and double-click the placeholder.
A modal is displayed for adding/editing images. There are placeholders for 10 images.
Double-click one of the placeholders.
 Another modal is displayed. You can take a picture on the spot or browse to a saved image file. If a web camera is attached to the workstation, click the Take Picture button. Otherwise, click "Choose file to upload".
Supported file formats are: .bmp, .jpeg, .png. The picture is displayed in the modal.
Click Upload.

Manage POS Shipping and Fees
Users can now manage POS fee types, including shipping fees, in Admin Console > Node Preferences > Transactions > Fees/Shipment. Previously, POS shipping and fees were managed in RIL. This change helps make Prism a standalone product.
Fees and shipping may only be modified at the subsidiary level (or lower). In Admin Console > Node Selection, drill down to the desired subsidiary.
On the side menu, navigate to Node Preferences > Transactions > Fees/Shipment.
A list of existing fee types is displayed. The "Shipng" type is at the bottom of the list and is used to apply a shipping charge. To add a new fee type, click the Add New button. A blank row opens at the top of the list. Enter the Fee Name (maximum 25 characters).  The fee type is added to the list. If the Active flag is selected, it will be available at POS.
Sample Fees/Shipping:

 
Schedule Deletion of Promotions
DevTrack ID #18859
Prism users can schedule the deletion of promotions to occur on a regular basis. This provides an easy way to remove promotions that are no longer needed. When scheduling the "Delete Promotions" task, you target for deletion promotions that have been inactive for a user-defined number of days. The user defines the "number of days inactive" in the task payload. Any promotions that have been inactive for that number of days (or more) will be removed from the database.
Schedule the "Delete Promotions" task at all locations that use promotions. By adjusting the payload, you can schedule the task to run as often as needed.
Here is the key information for the task:
Action end point = /v1/rpc
Action Payload = [{"Params":{"Days":"2"},"MethodName":"PCPromoDeletePromo"}]
This payload will delete promotions that are inactive for 2 days or more.
When defining the task, the user also enters a Start Date, frequency, timeout, workstation, etc.

Update Physical Inventory in Prism
DevTrack ID #20302
PI Sheets created in Prism 2.0 are updated in Prism. Previously, updating a PI required a user to export the PI to RIL (or Retail Pro 9) and do the update there.
To update a PI in Prism, when you are finished counting items, highlight the PI on the main screen and click the Update PI button. When updating Inventory, users have the option of updating All Counts or Quantities Only. All Counts will update all items on the PI Sheet, even those with a zero count. Quantities Only will ignore items on the PI Sheet that have a zero count and only update items that have a non-zero count. Updating a PI creates adjustment memos so select an Adjustment Reason.
A green toast message is displayed when the process is finished. Click anywhere on the message to close it.

PI Sheets with up to 500,000 Items
DevTrack ID #21198
Prism users can now create a PI sheet with up to 500,000 items.

Manage Loyalty Levels, Programs in Prism
New Loyalty Level
Navigate to POS > Customers > Customer Loyalty. Click the Customer Loyalty button.
 The Customer Loyalty lookup screen is displayed.
Click the Loyalty Level button.
Existing loyalty levels (if defined) are displayed in alphabetical order.
 Click the Add button.
Type the name of the loyalty level (maximum 30 characters).
Click Save.
New Loyalty Program
Navigate to POS > Customers > Customer Loyalty. Click the Customer Loyalty button.
 The Customer Loyalty lookup screen is displayed. Click the New button.
A screen for entering information about the new loyalty program is displayed.

• Enter a unique Loyalty Program Name (30 characters maximum).
• Select a Loyalty Level. If needed, you can create a Loyalty Level on the fly by clicking the Create New button.
• Select a Start Date and End Date for the loyalty program.
• For points-based programs, select how customers will earn and redeem points and enter a multiplier if needed.
• For percentage-reward programs, enter the percent reward to be received

Click the Save button.
Sample Loyalty Program configuration screen:
 
Assign Country to Customer
DevTrack ID #19324
You can assign a Country to customers in Prism. This enables Customer lists to be filtered by Country. Previously there was no way to assign a country to a customer.
To assign a country to a customer:
Navigate to the customer record and make sure you are in edit mode.
In the Add/Edit Address modal, click in the Country field. A pop-up menu is displayed. Start typing the country name. In the example below, the user has typed "u" and the list is filtered to show countries that start with the letter "u."
Note: As can be seen in the screenshot below, the country you just assigned is not shown in the displayed address; however, it will be visible when editing the address.

Search Customers by "Created By" Employee
DevTrack ID #20784
When searching for customers, the "Created By" search filter is now a dropdown list of existing employees. Previously, users had to type an entry. Being able to select from a dropdown helps prevent user-entry errors.
Sample Customer Search showing Created By filter with dropdown list of employees:

Sold Qty on PO Advance Item Lookup grids
DevTrack ID #15352
Users can add the Sold Qty column to Inventory Search (document) grids. This means the Sold Qty column will be available in Advanced Item Search on purchase orders, transfer orders and other documents.
This helps the user makes purchasing decisions involving the item. Note: Sold Qty is one of the values that can be updated using the SRO Tool (the other values being On Order Qty and Received Qty).

Allow Voucher to Update Inventory Prices
DevTrack ID #21621
A new "Allow Voucher to Update Inventory Prices" preference has been added to Admin Console > Purchasing > Vouchers. This preference, when enabled, will add a "Price" column to the voucher item grid that will display the Price for the currently active Price Level. By default, the "Allow Voucher to Update Inventory Prices" preference is disabled. To update inventory prices, the user can edit the Price field. When the voucher is updated, if any Voucher Prices have been changed, a prompt is displayed to the user:
Update Inventory Prices?
Yes - Updates the voucher and generates price adjustment memos.
No - Updates the voucher without generating price adjustment memos (therefore, no price change).
Permission: Vouchers > Change Price
The ability to change price on vouchers is controlled by the existing security permission: Vouchers > Change Price

Store Code, not Store Number in UI
DevTrack ID #18480
Store Name, Store Code, and Store # have been added to several areas of Grid Formats:

Centrals Service Version 2
DevTrack ID #20595
This release includes an updated version of the Centrals service. When the Centrals service is enabled, customer lookups, returns, gift cards and store credit can all be verified against a central database, providing enhanced security and control.

Permissions for Printing Held documents
DevTrack ID #17293
Permissions have been updated to include separate permissions for printing "held" versions of documents. Previously, a single permission was responsible for controlling printing for each record type (held and non-held). If a user could print a regular document, the user could also print held versions. Adding separate permissions for held documents provides better security and control.
The following table lists the permissions available for each Prism document type:

New Fields on Store Records
DevTrack ID #21752
Global Store Code, Address 4-6, Fiscal Code, and UDF 1-5 have been added to Admin Console > Node Preferences > Node Selection > Stores.

SRO Tool in TTK
DevTrack ID #20600
The Prism SRO tool enables users to update sold, received, and on-order totals for inventory. Running SRO on a regular basis gives users the most up-to-date information, helping managers and other key personnel make better decisions about replenishing inventory and avoiding stockouts.
Navigate to Technician's Toolkit and log in. Once you are logged in, click Data Utilities on the top menu and then select SRO Tool. After running the tool, the values can be viewed in Inventory > Item Details on the Qty tab.

Rename Server tool Integrated into Web TTK
DevTrack ID #20005
Users who need to rename a computer that is a Prism server need to take special steps (using the Rename Server tool) to ensure Prism can run using the new computer name. The Rename Server tool is now integrated into the web-based version of the Prism Tech Toolkit introduced in Prism 1.1.4.7. The Rename Server tool was the lone tool that remained using the old .exe-based version of the Tech Toolkit. With the migration of the Rename Server tool into the web-based toolkit, the old .exe-based version of the Tech Toolkit has been removed from the Prism install files. (Note: Previously the tool was called the "Rename Host Computer" tool and two steps were required with a reboot in between; this is now a one-step process with an enhanced after-reboot program that performs all the former "Step 2" processes.)
To access the Rename Server tool:
Login to the TTK. The enterprise servers are on the left. Click the hamburger menu for the desired server. Click Rename Server.
When you select the Rename Server option on the server menu, a new modal is displayed. The old name is on the left and the new name is on the right.
Click Execute Rename. The process takes some time. Once the process is completed, reconnect the server to the enterprise. Reconfiguration is not complete the server is rejoined to the enterprise.

INSTOREZIP on Transfers Doc Designs
DevTrack ID #19782
In Document Designer, you can add the InStoreZip field to transfer document designs. This field is needed on documents to meet fiscal requirements in some countries (e.g., Portugal). Previously, users could add the OrigStoreZip and OutStoreZip but not InStoreZip.  Per Portuguese fiscal requirements apparently it is necessary to show the in store zip.
Open Doc Designer and select Transfer Slips in the Area dropdown.
Select the desired Transfer Slip document design and click the Edit button
Look at the "transferslip" data fields on the right. Notice that InStoreZip is present.
Drag the InStoreZip field to the desired area of the design and save the changes.

New Transfer Order Permissions
The following new permissions have been added for Transfer Orders:

Store Filter Enhancements in Transfer Verification
DevTrack ID#19791
Store filters in Transfer Verification now include an "ALL" selection. Adding the "ALL" selection to the From Store and To Store filters enables a single resolution rule to be applied as either a "one to many" or "many to one" filter. The store filter selections determine which stores the rule is applied to. Previously, store filters only allowed for "one-to-one" or "any-to-any" filters. This change gives retailers greater flexibility when it comes to verifying transfers.
Define transfer resolution rules in Admin Console > Node Preferences > Transfers > Resolution Rules. When adding a new rule, in the From Store and To Store dropdowns, the "ALL" selection is included in the list of stores.
Note: Store-to-store rules take precedence over store-to-any or any-to-store rules.

Replication - New Resources (and Removed Resources)
Prism 2.0 is a completely standalone application; there is no communication with RIL (or Retail Pro 9). There are no Prism-to-RIL or RIL-to-Prism profiles. In Prism 2.0 there is a single list of resources that are used in Prism-to-Prism profiles.
New Resources

Removed Resources
The tax resource was removed in 2.0.

Admin Console Permissions
DevTrack ID#20441
There are 26 new permissions to control access to specific areas of the Admin Console. Previously, only the "Admin Console - Access" permission was available, which controlled access to all areas of Admin Console. These new permissions give retailers greater flexibility when it comes to controlling access to the Admin Console.