PrismCore 28.2.12 Release Notes

Important Notes about PrismCore v28

SQL 2008/2012 Required

A prerequisite is SQL2008. For those users that are enrolled in our ISV program, this upgrade doesn't cost anything, and in most cases is a simple process. For those users who want to go from 32bit to 64bit, it will require additional efforts so please contact support for more details. We strongly recommend Server 2008 64 bit with SQL 2008 64 bit to take advantage of the performance and security offered in those products.

Requires PrismCore 27

In order to load PrismCore 28, your store needs to have already had NBC update your servers to PrismCore 27. If you are NOT already on a version of PrismCore 27, you will need to contact IT Support, and they can assist you in scheduling your update.

XP Not Supported

Please note, PrismCore 28 does NOT support Windows XP. If your workstations or registers have XP, you will need to upgrade them prior to installing PrismCore 28.

INVENTORY CONTROL

ICS Item Maintenance/Inventory Maintenance 101/102

Prompt for ID (676727, v28)

Code has been added for ID Check. In Item Maintenance, a checkbox has been added for GM items called "ID Required". When checked the message "This item (SKU "sku") requires you validate the purchaser's ID. Is this purchaser eligible?" is given. If the user presses "Yes" then the item is added to the transaction. If "No", the message "SKU (sku) Removed from Sale" is given and the item is not added to the transaction. NOTE: Request #677805 has been written up to change the second message given to the user that says "SKU (sku) Removed from Sale". This message is being given on refunds as well which could be confusing.

Component Problem Corrected (681332, v28.1.1)

The user is able to add, add new, and delete component line items in the Component dialog box for a New Text record at Item Maintenance without error.

Copy to New Package (691659, v28.1.4)

Prior to the fix, if the user selected the "Copy to New Package" hammer option on the Package tab in Item Maintenance, they would receive the error, "Recordset is read-only." This has been resolved. If the user selects the "Copy to New Package" hammer option on the Package tab in Item Maintenance, the package record is copied to a new record without error.

WinText Users (694579, v28.1.9)

Prior to the fix, when WinText Only users opened Item Maintenance, the application would abruptly close. This has been resolved. When WinText Only users open Item Maintenance, or any other module available, it will open without error.

Components Dialog (691662, 691143, v28.1.4)

Prior to the fix, if a user opened the Components dialog on a textbook record and did not add any line items, the dialog would not close. It displayed the error message: 'Bundles must contain at least two components.' This has been resolved. If a user opens the Components dialog on a textbook record and does not add any line items, the dialog will close without error.
Additionally, a request was created to modify the code that controls the "Components" dialog in PrismCore Item Maintenance. In conjunction with v28, a new version of Stingray has been used to compile PrismCore and this new version of Stingray was causing issues with row counts in the Components dialog. As a result, an extra line was not displaying at the bottom of the details in the grid like it does in v27. This has been corrected so the extra row is now displayed properly at the bottom of the details grid.

Package Stock Adjustments (681365, v28.1.0)

Issue when doing stock adjustments on packages – if detail items do not have enough SOH to complete the adjustment to the package, the user message 'The SOH of the package's detail items is not enough to create the new SOH for the package. Do you want to adjust the SOH of the details so the adjustment can be made to the package?' does not display, warning the user, but the adjustment is made causing a negative SOH on the detail items. The check to display the user message has been taken out so that it will now display no matter what the reason for the adjustment if the SOH for the detail items is too low to complete the package adjustment.

Package Names (681355, v28.1.0)

When version 28 is loaded, a script will update existing data and change duplicated names to name-1, name-2, etc. while leaving the original created name. For example, a Package Name 'test' duplicated three times in Item Maintenance > Package would become 'test', 'test-1', 'test-2'. If a user attempts to add a duplicate description (or edit an existing description to a duplicate) in the Name field, the system will display an error upon save: A package with description: '<Name>' already exists. Please choose a different description. The user cannot continue until the description is changed to be unique.

Quick Search Issues (68846, v28.1.1)

In Item maintenance when doing quick searches by DCC the quick searches results columns for GM styles and season codes were missing or incorrect and on other occasions the quick search results window's DCC column was blank. This issue has been resolved.

No Returns Checkbox (681328, v28.1.0)

The request was created to correct a defect in the Copy/Add Inventory Records dialog in PrismCore Item Maintenance. Previously, if the "No Returns" box was checked or unchecked in this dialog, the modification would not be saved. This has been corrected and any modifications made to the "No Returns" flag in the Copy/Add Inventory Records dialog are now saved appropriately.

Editing ISBN Field (693775, v28.1.8)

Previously, editing the ISBN Field for a pre-existing ISBN at Item Maintenance did not update the Cat#/ISBN column in Purchase Order Detail, but did update the ISBN on the Printed PO (Print Purchase Orders report option.) This caused a mismatch between the Purchase Orders screen and the printed Purchase Order that was sent to the vendor.
This has been resolved. The ISBN in the Cat #/ISBN column in the detail of the screen will match the ISBN printed on the Print Purchase Order report.

979 ISBN (681430, v28.1.0)

Items with a 979 ISBN prefix were not able to be added to Item Maintenance or scanned into PrismCore. This issue has now been resolved.

ID Check for GM Items Added (680133, v28.1.1)

Code has been added for an ID Check. In Item Maintenance, a checkbox has been added for GM items called "ID Required". When checked the message "This item (SKU "sku") requires you validate the purchaser's ID. Is this purchaser eligible?" is given. If the user presses "Yes" then the item is added to the transaction. If "No", the message "SKU (sku) Removed from Sale" is given and the item is not added to the transaction.
NOTE: This option is not used for web/mail order.

Copy/Add Dialog (681328, v28.1.0)

The request was created to correct a defect in the Copy/Add Inventory Records dialog in PrismCore Item Maintenance. Previously, if the "No Returns" box was checked or unchecked in this dialog, the modification would not be saved. This has been corrected and any modifications made to the "No Returns" flag in the Copy/Add Inventory Records dialog are now saved appropriately.

PrismCore Package Descriptions (681355, v28.2.1)

PrismCore used to allow multiple packages with the same description, but this caused issues with the Package Detail report. When version 28 is loaded, a script will update existing data and change duplicated names to name-1, name-2, etc. while leaving the original created name. For example, a Package Name 'test' duplicated three times in Item Maintenance > Package would become 'test', 'test-1', 'test-2'. This solves the issue with duplicate package names.

CRV Items and PRISM360 (681411, v28.1.2, v1.8.4.3)

Code has been added to allow for CRV (non-merch item attached to an item). A Non- Merch item can be attached to a GM item through Inventory Maintenance > Hammer Menu > Non-Merchandise Configuration. This is currently coded for GM items only.

F9 Sales History (TFS398, v28.2.2)

The F9 Sales History report was not calculating the margin totals correctly – always displaying as 1.00 with a '$'. The calculation was corrected so it is now the percentage between the retail and cost totals and the '$' is removed so it makes more sense as a percentage not money.

Scale Items May Be Incorrectly Priced with Half Cents (TFS1219, v28.2.10)

Scale items were being added to PrismCore with partial cents. Code has been changed so that the price displays correctly, due to the weight of the item.

ICS Serial Number Maintenance 105

Serial Numbers and Mail Order Exchange (692515, 692338, v28.1.7)

Prior to the fix, if a mail order exchange was closed with a shipped serial numbered item in the detail, the serial number assigned in the Quick Serial Number Maintenance dialog was not updating Serial Number Maintenance and not printing on the Serial Number Report. This is resolved. If an exchange is generated with a shipped serial numbered item in the detail, the serial number assigned in the Quick Serial Number Maintenance dialog, will update Serial Number Maintenance and print on the line item on the Serial Number Report. Additionally, the request was created to modify the Quick Serial Number Maintenance dialog that appears when closing PrismCore mail orders that contain serial number SKUs. Previously, clicking the line item would not assign that serial/xref to the item. Now when the dialog appears. selecting the line item will assign the serial/xref to the item

Visual Issue in Serial Numbers (688408, v28.1.3)

The request was created to correct a visual defect in PrismCore Serial Number Maintenance. Previously, a blank row was not displaying at the bottom of the detail lines in the module. This was preventing further details from being created by double- clicking on the blank line. This was due to changes in the stingray libraries used for compiling v28.1+ builds. The line is now displaying properly and details can be added without issue.

Apple DEP (693773, 693776, 693777, v28.1.8)

A field has been added to the Customer Maintenance screens with the header "Apple DEP ID". The field is 10-characters long, must be provided by the customer, and with entry, will flag the customer as being eligible to register an item in the Apple DEP program. An additional checkbox has been added to the header at Serial Number
Maintenance. When checked, the serial numbered item will be flagged as being eligible for enrollment in the Apple DEP program.
The executable file has been created to generate a .csv file (DEPExport) for export that lists transaction information for Apple DEP Eligible items. The file is intended to be relayed by a third party vendor, who then automates the process of enrolling Apple devices in the AppleCare Connect program (ACC). The ACC program utilizes a Device Enrollment Program (DEP) to get devices setup for management. The third party provider has a standalone program that imports order and transaction information and sends it to Apples API which then enrolls the devices in DEP/ACC.

Serial Numbered Items (681343, v28.1.0)

Serialized item transactions were allowing completion of the transaction without a customer being assigned to the serial number. This issue has now been resolved, not allowing the transaction to complete without an assigned customer.

ICS Inventory – 142

Physical Inventory DCC (680581, v28)

The request was created to add a new parameter to the Physical Inventory DCC report in PrismCore Physical Inventory. The new parameter (checkbox) is called "Combine New/Used". Running the report with this parameter checked will combine new and used textbook DCC's into one section of the report (as well as display a new column "Type" which shows NTX for New and UTX for used). If the new parameter is not chosen, textbooks will be broken out by DCC as typical.

Physical Inventory Reports (681423, 688457, v28.1.0)

Inventory reports from physical inventory generated using 'all locations' selected will now display the valuation method of the default (store1) location. Previously, the system was using FIFO, regardless of the valuation method in cases where the locations had different valuations methods in PrismCore Admin.

Physical Inventory by DCC report (688427, v28.1.1)

Users were receiving 'Failed to retrieve data' error when posting inventory and printing the 'Physical Inventory DCC' report from the Post Inventory Dialog. This issue has now been resolved and the report can be printed as expected. This same report ran as expected from the reports menu option in physical inventory.

Inventory Report Issues (694581, v28.1.9)

The request was created to correct a defect that was returning an error when running the "Physical Inventory SKU/Barcode", "Physical Inventory by Fixture" and "Physical Inventory by Fixture with Batch" reports from PrismCore Physical Inventory. An error was being displayed when running the reports, but has been corrected and removed.

Sorting Issues (681410, v28.1.0)

The request was created to correct a defect in PrismCore Physical Inventory. Previously, when sorting the records by double-clicking the "Description" column header, PrismCore would unexpectedly crash. This has been corrected so double-clicking the "Description" column header sorts the records appropriately and does not cause the program to crash.

Combine New/Used on Physical Inventory Report (680581, v28.0.2)

The request was created to add a new parameter to the Physical Inventory DCC report in PrismCore Physical Inventory. The new parameter (checkbox) is called "Combine New/Used". Running the report with this parameter checked will combine new and used textbook DCC's into one section of the report (as well as display a new column "Type" which shows NTX for New and UTX for used). If the new parameter is not chosen, textbooks will be broken out by DCC as usual.

Double Sorting in Inventory (681410, v28.1.0)

The request was created to correct a defect in PrismCore Physical Inventory.
Previously, when sorting the records by double-clicking the "Description" column header, PrismCore would unexpectedly crash. This has been corrected so double-clicking the "Description" column header sorts the records appropriately and does not cause the program to crash.

Physical Inventory by Batch Report (696105, v28.2.1)

Physical Inventory by Fixture with Batch report was changed so that the 'Total Scanned' column reflects the amount scanned across all fixtures, not just those included in the report parameters. Also, the asterisk used to designate 'discrepancy' was moved to the "Total Scanned" column as opposed to the "Scanned" column (previously printed).

Inventory by DCC Report (695253, TFS1455, v28.2.1)

Physical Inventory DCC report was not summing correctly. This totaling issue was mostly seen on the Act Cst Var Column, but also effected the final totals for DCC, Location, and Grand Totals. This issue was caused by an incorrect calculation accidentally changed when fixing a sorting issue. This has been corrected.

ICS Catalog Maintenance – 151

Update Prices (681345, v28.1.0)

In catalog maintenance, the hammer option 'update prices' was inadvertently rounding prices on the catalog inventory detail when it should not be, based on the parameters set in PrismCore Admin. When updating prices on the catalog the price was being rounded even when the parameter 'Round prices using store information' checkbox was 'unchecked'. This issue has now been resolved.

Deletions from Catalogs (658547, v28.1.0)

Deleted catalog items were not being removed from the web. This has been corrected.

ICS Customer Maintenance – 156

Customer Maintenance Issues (691658, v28.1.4)

When a new account was added to a customer the account could not be edited or deleted. This has been fixed so the account can be edited and deleted when a new account is added to a customer.

Web Customers (681386, v28.1.1)

When multiple web orders flow to PrismCore for a customer, multiple customer records are no longer created. Only one customer record is created & retained in Inventory Management > Mail Order > Customer Maintenance.

Deleting Customer Results In An Error (695252, v28.2.0)

Prior to the fix, when a user attempted to delete a customer record that had an account attached in the detail in Accounting > Receivables > Customer Maintenance, either on PrismCore Admin or PrismCore, they would receive the following SQL error:
The DELETE statement conflicted with the REFERENCE constraint "FK_Acct_Agency_Customer_Customer_Table". The conflict occurred in database "prism", table "dbo.Acct_Agency_Customer", column 'CustomerID'. The statement has been terminated. This has been resolved. When a user attempts to delete a customer record that has an account attached in the detail in Accounting > Receivables > Customer Maintenance, either on PrismCore Admin or PrismCore, they will receive the following error, "Customer in use: Account". The user can left-click <OK> to return to the customer record.

ICS Mail/Web Order

Location specific ECom (676728, 681427, v28)

The request was created to add the ability to have location-specific Ecom/MOTO Client Authentication Tokens and Client GUID values. Prior to this ITG, the only place to enter these values was in WPConsole – Shif4 – Properties. The field "Shift4 Ecom/MO Client Authorization Token" in WPConsole will still exist and function as normal. The fields "Shift4 Ecom/MOTO client GUID" and "Shift4 Ecom/Moto Client Auth Token" have now been added to PrismCore Admin Mail Order General Parameters, so separate locations doing Mail/Web order processing with Shift4 can enter unique Client Auth Tokens and Client GUID values if desired. These values are added in order to acquire the Shift4 Access Token, which is stored in the database and cannot be viewed in the PrismCore Admin user interface. Once the Access Token is acquired, transactions can be processed normally.

Multiple Pinpads in Mail Order (676726, 681415, v28)

The request was created to add a new dialog in PrismCore Enter Mail Orders – Hammer Options called "Configure Point to Point Pin Pads". This dialog will allow users to assign TID's to pin pads (that are named by the user). The TID entered in the dialog, will be the TID assigned to that user/pin pad while the Enter Mail Order module is open. If the module is closed, the pin pad will no longer be assigned to the user. When in P2P mode (ccmanagementmode = 2), if there are pin pads configured in the new dialog, the user will be prompted to assign a pin pad of their choosing before the first transaction is processed. After the first transaction, the prompt will no longer appear, until the module or program is closed by the user and the next first transaction is processed. The configuration dialog is not available if P2P is not turned on.

Mail Order and P2Pe (688385, 685177, v28.1.7)

The request was created to correct a defect when reversing Mail/Web Order shipments while using Point-To-Point encryption. Previously, when a shipment was reversed (Ship Mail Orders, hammer options) the user was being prompted to enter the CC info into the pin pad. Since the token information was acquired when the order was initially processed/shipped, this step was not needed. Code has been implemented to use the token saved from the initial Processing/Shipping of the order when reversing the shipment. This sends a refund record to Shift4 (DOTN) which cancels out the amount of the sale. At that point, the shipment can be closed again with the same CC info, or a new tender can be added and input into the pin pad if needed.

Pin Pad Issues in Mail Order (692440, v28.1.7)

The request was created to modify the times when a user is prompted to choose which pin pad they would like to use to tokenize CC numbers in Point-To-Point mode. In v28, a new hammer option menu was added to "Configure Point-to-Point Pin Pads". This dialog allows multiple pin pads to be assigned and used from different workstations.
Once the menu is configured with pin pad(s), a prompt appears the first time a user needs to enter CC data into the pin pad for tokenization. At this point the user must choose which pin pad in the menu to assign to themselves for that session (session = until Enter Mail Orders is closed). Previous to this ITG, the dialog would appear the first time a mail/web order was processed, even if no CC info was needed (example: the order was tendered to A/R account). This has been corrected so the user is now only prompted to assign themselves a pin pad the first time CC data is needed from the pin pad. Once the pin pad is assigned, it stays assigned to that user until Enter Mail Orders is closed.

Bundles in Mail Order (692332, v28.1.7)

When a rental bundle was included in a shipment, the components were not flagged correctly in the Rental Y/N column on the Mail Order Packing List. This has been resolved. When a rental bundle is included in a shipment, the component will be flagged in the Rental Y/N column as Y for a rental component and N for a non-rental component. The Rental Y/N column will be blank for the bundle SKU itself.

Quick Serial Number Maintenance (692335, v28.1.6)

When closing an order at Ship Mail Orders that had a serial numbered item in the detail, the <OK> button in the Quick Serial Number Maintenance dialog did not respond (did not assign a serial # to the customer.) This is resolved. When closing or processing an order at Ship Mail Orders or Enter Mail Orders, that had a serial numbered item in the detail, left-clicking the <OK> button in the Quick Serial Number Maintenance dialog after selecting a Serial Number/XREF, will assign it to the customer.

Serial Numbers and Refunds (692337, 691871, v28.1.6)

When a serial numbered item that exists in multiple store locations was added to a refund/exchange, the serial numbers for the specified location were not displaying correctly in the Quick Serial Number Maintenance dialog. This has been resolved. When a serial numbered item that exists in multiple store locations is added to a refund/exchange, the Quick Serial Number Maintenance dialog prompting the user to assign a Serial Number/XREF, displays a selection from the correct store location, matching that of the order.
Additionally, in the Quick Serial Number Maintenance dialog presented after the refund/exchange is closed and the print dialog is acknowledged, the following error was displayed even though the user typed in the Serial#, XREF, or scanned the XREF, & clicked the OK button: Cannot exit. Need to select 1 serial item(s). Typing in either the Serial# or XREF and pressing <Enter> generated the error message: Serial Number/XREF "##########" not found. (########## being the Serial# or XREF.) This caused a loop. The only way to escape the dialog was to left-click the Cancel button. Doing so closed the refund without removing the Customer & Tracking# information from Serial Number Maintenance. This has been resolved. In the Quick Serial Number Maintenance dialog presented after the refund/exchange is closed, the user can type in the Serial#, XREF, or scan the XREF. The serial number line is selected. Clicking the OK button will close the dialog box and remove the customer/order information for the serial numbered item in Serial Number Maintenance.

Changing Mail Order Type (691148, v28.1.3)

The request was created to correct an issue found in PrismCore Enter Mail Orders. Previously, when changing a mail order's "Type" in the module header from "Order" to "Request" or "Quote" and back again was causing an error message stating "Update or delete operation did not affect any rows". This has been corrected so the "Type" field can be changed by the user to whatever type is needed for the record.

Multiple Shipments for Backorders (691146, v28.1.7)

If the user created an additional shipment for a backordered item on an existing open shipment at Ship Mail Orders, the system would not alert the user that it was on an existing open shipment, and actually double the quantity on that open shipment. This is resolved. If the user attempts to create an additional shipment for a backordered item on an existing open shipment at Ship Mail Orders, the user will receive the error, "All Order items exist on a Shipment (#####)." (##### is the order number.) The error is acknowledged by clicking the <OK> button. No additional shipment is created, and the order quantity is not increased on the existing open shipment.

Deleting Shipments with Serial Numbered Items (691873, 692339, v28.1.7)

When the user deleted a shipment with a serial numbered item in the detail, the Quick Serial Number Maintenance dialog was presented to delete an assigned serial number, when none had yet been assigned. This has been resolved. The shipment is deleted without being prompted w/the Quick Serial Number Maintenance dialog.
Additionally, when deleting a shipment that contains a serial number item, the Quick Serial Number Maintenance dialog that displays is prompting the user to assign (add) a
serial# when it should be displaying the serial number to un-assign (remove). This is resolved. When a shipment with a serial numbered item in the detail at Ship Mail Orders is reversed & deleted, after confirming <Yes> to delete the shipment, the Quick Serial Number Maintenance dialog prompts for the user to un-assign the appropriate Serial Number/XREF previously assigned for the order line.

Processing without a Renal XREF (69233428.1.6)

Previously, a user could process an order with a serial numbered item in the detail without being prompted to assign a serial number. This is resolved. If a user processes an order at Enter Mail Orders with a serial numbered item in the detail, the Quick Serial Number Maintenance dialog will prompt the user to assign a serial number prior to the order changing to "Completed" status.

Serial Number Workflow Solutions (692336, v28.1.6)

The request was created to correct a workflow issue within Enter/Ship Mail Order modules in PrismCore. In v28.1, the "Quick Serial Number Maintenance" dialog has been moved to the end of the processing/shipping of mail orders, rather than when the item is added to the transaction. Previously, the "Quick Serial Number Maintenance" dialog was appearing after the standard windows print dialog. Thus when a packing/shipping list was printed, it did not contain the serial number/XREF information because one had not been assigned yet. This has been corrected so the "Quick Serial Number Maintenance" dialog appears before the windows print dialog - except in Mail Order Refund/Exchange, where the "Quick Serial Number Maintenance" dialog appears after the windows print dialog.

BTS Orders (691664, v28.1.4)

BTS orders were going to a 'completed' status before the actual order was shipped. This prevented the items from getting added to a ship mail order record when time to actually ship the completed order. This issue was resolved by placing an extra check in the stored procedure against the transaction detail data.

Email Configuration (681409, v28.1.0)

If all locations have been added to one or more tabs (ex. Shipped Orders), the "Add Location" button will remain active to allow additional locations to be added to any other tabs in Mail Order Email Configuration.

Mail Order Reversals (685592, v28.0.5)

The request was created to remove previous modifications that were implemented to attempt to allow shipment reversals on mail orders done in P2P mode. This process was not allowed. The implementation of these modifications caused other issues with acquiring Shift4 tokens on normal mail order shipments, so they have been removed in order to release this build. Since the modifications have been removed, shipment reversals are still not allowed with Shift4 Mail Orders and refunds/exchanges must be performed in order to reverse a shipment.

Refund after Purge (688384, v28.1.0)

When processing a Refund in Mail Order Refund Exchange against an order where the card has been purged based on the Credit Card purge settings, the refund is no longer allowed.

Web Comments (681369, v28.1.1)

The "Send Section Comment from Course Request to the Web" parameter has been removed from PrismCore Admin > Inventory Control > Parameters > System Parameters > Web. The Web Comment field from the Course Request header is now sent, by default, and will display on WebPRISM. The Comment field from the Course Request header is no longer sent to WebPRISM.

Shipment Email Changed (681392, v28.1.2)

Previously, the Shipped Order email sent to the customer did not reflect a change of shipping method made at the Ship Mail Orders screen. This has been corrected. If the shipping method is changed at the Ship Mail Orders screen, the Shipped Order email sent to the customer will reflect the change in the order totals as a result of the change in shipping method.

NMRP Error Notifications (681335, v28.1.2)

The email error notification has been updated to be more useful when an NMRP rental is processed in Enter Mail order without a customer billing address. The current email stated: 'the balances are off between the store and the web', but did not specify why. The new error notification now states: 'The following NMRP Customers have missing Billing Information: <customer #, transaction #>'.

Refunding Mail Order with Serial Number (681347, v28.1.0)

Prior to PrismCore v28, if refunding a serial numbered item at Mail Order Refund/Exchange, the user was prompted to select the serial number to un-assign when the line item was initially added to the detail. This has changed. The user will be prompted to un-assign the serial number after the refund/exchange is closed & the print dialog is acknowledged. The Customer and Tracking number information will be deleted from Serial Number Maintenance only after the serial number is un-assigned during the closing process.

Web Customer Number (681398, v28.1.0)

If a user enters a Student ID of "0" (# zero) on WebPRISM when generating an order, the Customer ID on the order in PrismCore will become the next instance in the sequence series for web customer in PrismCore (ex. WC-#######.)

Confirmation Emails for Refunds (681393, v28.2.1)

The request was created to correct a defect in PrismCore Mail Order Refund/Exchange. Previously, confirmation emails were not being sent when mail order refunds were processed. This has been corrected so if a mail order has the "Send Email Status" checked when processed, it will send an email to the customer on the mail order record if the order is refunded.

A/R NMRP Mail Order Transactions (681396, v28.1.0)

The request was created to correct an issue with A/R Sales done from WinPOS or PrismCore mail order modules that were allowing the transactions to be tendered to the NMRP or Partnership accounts that were erroneously added to the customer. The NMRP and Partnership accounts exist to track the rebate amounts accrued for either rental program. There have been abnormal situations in past versions where these accounts could erroneously get attached to some A/R customers. If the tender A/R Charge was chosen, these accounts would appear available to be charged for that customer. This has been corrected so if A/R Charge is the tender for the transaction, the account for NMRP or Partnership can no longer be chosen as the account for that customer.

Combine Single Site and Rentals (681353, 28.1.0)

The request was created to correct a defect concerning the "Rental Guarantee" checkbox in the detail lines of the tender tab in PrismCore Enter Mail Orders. When the "Combine all Data into One Website" system parameter was turned on, web orders that were to be processed at any location other than the location of the Web XML Import were not displaying the proper status of the tenders. This has been corrected so if this system parameter is on, the "Rental Guarantee" flag on the tender tab for the order will be reflected correctly for any location.

Print Refund Not Printing Serial Items (653434, v28.1.7)

Serial numbers were not displaying on the 'print refund/exchange' report ran from the Refund/Exchange module. The report should print the serial number information the same as the Mail Order Packing List printed from the Ship Mail Order module. To correct this problem an issue in the UI had to be corrected to link the serial number information from the ship mail order module to the refund/exchange module (ITG#599210). This correction to the UI corrected the display on the reports.

Primary Key < 10 (688380, v28.1.1)

Prior to the fix, the user was unable to retain an account with a primary key < 10 in the Account/Reference column on the Tender tab for a mail/web order. This has been resolved.

Bundles in Mail Order (681400, v28.1.0)

Once a textbook bundle is shipped in Ship Mail Orders, if there are multiple shipments for this same order, the bundle will not be pulled onto subsequent shipments in error. This has been corrected so the bundles appropriate to the proper shipments.

Deleting Catalog Items (658547, v28.1.0)

Deleted catalog items are now updating to the web.

Tax Allocation Issues (591359, v28.1.7)

When changing the shipping method on the Enter Mail Order record, the total tax was not getting updated correctly. This has been corrected.

Multiple Pin Pads (681415, v28.1.1)

The request was created to add a new dialog in PrismCore Enter Mail Orders – Hammer Options called "Configure Point to Point Pin Pads". This dialog will allow users to assign TID's to pin pads (that are named by the user). The TID entered in the dialog, will be the TID assigned to that user/pin pad while the Enter Mail Order module is open. If the module is closed, the pin pad will no longer be assigned to the user. When in P2P mode (ccmanagementmode = 2), if there are pin pads configured in the new dialog, the user will be prompted to assign a pin pad of their choosing before the first transaction is processed. After the first transaction, the prompt will no longer appear, until the module or program is closed by the user and the next first transaction is processed.
The configuration dialog is not available if P2P is not turned on.

Mail Orders and Rental Guarantees (681353, v28.1.1)

The request was created to correct a defect concerning the "Rental Guarantee" checkbox in the detail lines of the tender tab in PrismCore Enter Mail Orders. When the "Combine all Data into One Website" system parameter was turned on, web orders that were to be processed at any location other than the location of the Web XML Import
were not displaying the proper status of the tenders. This has been corrected so if this system parameter is on, the "Rental Guarantee" flag on the tender tab for the order will be reflected correctly for any location.

BTS Interface (681334, v28.2.5)

BTS processed orders were not hitting GL/Sales correctly. This ticket was created to fix an issue with missing journal entry information. When sales were posted, there was a transfer of funds between AR and Cash, which was recorded properly on the Mail Order Register Totals report, but not in Manual Sales – Posted Sales. This problem was caused by a shipment record not getting created when the BTS process ran. Without the shipment record, the information doesn't transfer to manual sales and on to the general ledger entry. The tender section of the Posted Sales Report and the tender section of the Mail Order Register Totals report should match – then the general ledger entry will record the cash and BTS prepay correctly. A Manual Sales record is created for the tenders (negative AR and positive Credit card) and a GL entry is made (debiting the credit card and crediting the AR GL code).

Mail Order Register Totals Report (681344, v28.1.0)

Mail order refunds were not showing up on the 'Mail Order Register Totals' report when the 'selected store locations' option was selected for location. The refund displayed correctly when selecting individual locations. This issue has now been corrected.

Confirmation Emails Not Sending (681393, v28.1.6)

The request was created to correct a defect in PrismCore Mail Order Refund/Exchange. Previously, confirmation emails were not being sent when mail order refunds were processed. This has been corrected so if a mail order has the "Send Email Status" checked when processed, it will send an email to the customer on the mail order record if the order is refunded.

AVS Errors in Mail Order (688430, v28.2.1)

Prior to the fix, AVS errors were not being displayed for manual card entry in mail order in PrismCore when the account was set to do so in PrismCore Admin and with Shift4. This has been resolved. If a customer account is set to display AVS errors in both PrismCore Admin > Mail Order General Parameters and with Shift4, these errors will display correctly when processing/closing a mail order.

Partial Auth Issues with Shift4 (TFS379, v28.2.9)

Prior to the fix, Shift4 partial authorizations were processed as though the authorization was for the full amount. This has been resolved. The Shift4 request going out from
PrismCore disables partial authorization for web and mail orders only (POS will continue to allow partial authorization if flagged to do so in WPConsole.) Partial authorization in this case means that there is a charge limit on the CC, whether it is a daily charge limit or overall charge limit that will be exceeded with the transaction. The idea of partial auth in this case means that there is a charge limit on the CC, whether it is a daily charge limit or overall charge limit that will be exceeded with the transaction. The bank will only allow an amount to be charged that does not equal the full amount of the transaction. With this change, the "Allow Partial Authorization" in WPConsole > Shift 4 > Properties is for POS Only.

Issues with Multi-Web (TFS945, v28.2.9)

To clarify, an item without an inventory record has header information only at Item Maintenance; no inventory location lines for the specified store location are listed in the detail. An item without an inventory record can be added to a catalog, but will not be sent to the web. Prior to the fix, an item without an inventory record that had been previously added to a catalog that was checked for 'WebPRISM', and then had an inventory record added for the web location at a later time, that item was not sent to the web upon a resend of catalog information. This has been resolved. When an item without an inventory record that had been previously added to a catalog that was checked for 'WebPRISM', and then had an inventory record added for the web location at a later time, that item will be sent to the web upon a resend of catalog information.

Replacing Rental Guaranteed Tender (TFS1072, v28.2.7)

Prior to the fix, when set to use P2P (Point-to-Point) authorization and the user deleted a rental guarantee tender that was declined, then entered a new one at Ship Mail Orders, they were not prompted at the pin pad to enter the new credit card information. This has been resolved. When set to use P2P (Point-to-Point) authorization and a user deletes a rental guarantee tender that was declined, then enters a new one at Ship Mail Orders, they are prompted at the pin pad to enter the new credit card information. This change only impacts Ship Mail Order.

Shift4 and Preauth / Changing Tender Information (TFS1199, TFS1390, v28.2.11)

Prior to the fix, when set to Shift4 Point-to-Point, the system would allow the user to change the credit card tender amount on the Tender tab after the original tender total had been pre-authorized at the pin pad. This has been resolved. When set to Shift4 Point-to-Point, the system will not permit a user to change the credit card tender amount on the Tender tab after the original tender total had been pre-authorized at the pin pad. To note, the user can add an additional tender line using the same tender type and credit card number to the order, then pre-authorize the additional amount at the pin pad. There is no error message displayed for the user when attempting to edit the tender total after it has been pre-authorized, the system just does not allow it.

ICS Sales

Posting Sales with SKU Not Found (688396, v28.1.1)

The request was created to correct an issue discovered when posting sales records that contain a SKU that is not found. If a SKU on a sales record for whatever reason is "not found", then the sales record cannot be posted manually (hammer options) and is not posted if the store is setup to post automatically. The SKU that is "not found" must be fixed on the sales record in order to post.

Creating New Sales Event (688423, v28.1.1)

Users were getting a 'query timeout expired' error when creating a new sales event or modifying the 'price modification dialog' from the price ellipsis. This issue has now been resolved.

Markdowns (691870, 688404, 681420, v28.1.5)

The request was created to correct a defect in PrismCore Markdowns. Due to the v28.1+ changes that included recordsets and snapshots, an "Invalid Descriptor Index" error was being displayed when accessing the item filter menu after applying an instant markdown. This has been corrected so the item filter menu is accessible without error after an instant markdown is applied.
Additionally, a request was created in an effort to alleviate issues with applying instant markdowns to large markdown records in PrismCore Markdowns. At some locations, applying instant markdowns to large markdown records was causing PrismCore to hang indefinitely, or take hours to complete. The changes in this ITG implement modifications to the code to correct this.

Refund A/R Transaction (TFS1368, v28.2.11)

When doing a refund on an A/R transaction, a cash tender with change due was being inadvertently added to the transaction. This caused the report to be out of balance and look like additional cash was refunded back to the customer as well as the AR refund. This has been corrected.

ICS Textbooks / Rentals

Order Decision Display (681440, v28.2.0)

Order Decisions display has been changes so that in OD Module and OD Tab in CR Module the Link SKU Vertical tab displays the Parent SKU and its Substitution SKU's and The Component Linked Vertical Tab displays the Rentable Components SKU's for the Parent and Substitution Bundle SKU's.

Request Date and Worked Status (688400, v28.1.1)

The request was created to correct a defect in PrismCore Order Decisions regarding the Work status of order decision titles. Previously, if a title was in a "Worked" status and the request quantity or request date were changed in Course Requests, the status of the title was not being changed to "Rework". This has been corrected so if either of these values are changed for a particular title in Course Requests, the work status of that title in Order Decisions changes from "Worked" to "Rework".

Application Issue (691941, v28.1.1)

The request was created to correct a defect in PrismCore Course Requests. When a number was input from the keyboard into the "Request Type" field, this was causing the application to close unexpectedly. This has been corrected by locking this field down to the available Request Type options and not allowing characters to be typed into the field.

Adopting Partnership v2 Items (691942, v28.1.6)

The request was created to correct a visual defect during the adoption of Partnership v2 items, specifically if the items were bundles. Previously, bundles were not being displayed properly in the adoption list, therefore they could not be properly adopted. If bundles are Pv2 eligible and on the proper course requests, they can be adopted into a Partnership v2 period along with their rentable components.
NOTE: Any bundle is listed in the adoption dialog as a bundle, or as a normal rental item if it meets the criteria.

Instructors (691155, v28.1.3)

The request was created to correct a defect found in PrismCore Instructors. Due to various changes related to the compiling of v28, an "Invalid Descriptor Index" error was being displayed when records in this module were added or modified. This has been corrected so when a record is added or modified in Instructors, that no error message is displayed.

NMRP Bundles and Rentals (688469, v28.1.1)

NMRP bundle items were not updating in rental number maintenance when retail price is updated in inventory maintenance. This issue has now been resolved so when retail prices are updated, then NMRP bundles are updated as well.

Wording Change in Rentals (691156, v28.1.4)

The return type in Rental number maintenance history tab was changed from 'return to Neebo' to 'returned to Nebraska'. This is seen when returning an NMRP back to NBC.

Rental Agreements (691869, v28.1.6)

The request was created to modify the size limit of Rental Agreements in PrismCore Warranty/Rental Agreements. The change was implemented to accommodate rental agreements entered into NMRP Manager and imported in PrismCore that were longer than the previous size limit of 4000 characters. The limit is now 8000 characters and agreements print accordingly.

Return Type Status (681380, v28.1.2)

The return type status in Rental Number Maintenance Rental History was not getting updated correctly when an NMRP return was made centrally back to NBC. This was caused by the RRtnID of that rental not updating when the return was made. All conditions when returned to NBC now display the correct return type on the rental history detail line.

Rental Reconciliation (688454, v28.1.1)

Rental reconciliation was running very slowly on some sites, so the query was tweaked a bit to help it run faster. This has been implemented and running on the test sites for quite a while now without issues.

Rental Periods (681362, v28.1.0)

Users were allowed to add/update a rental period with an 'end date' that occurs after the periods 'due date'. This has now been prevented. A valid 'end date' is now considered either the same date as the 'due date' or a date prior to the 'due date but after the 'start date'.

Allow Substitutions (681368, v28.0.1)

The request was created to remove the "Allow Substitutions" checkbox from PrismCore Course Requests, as this field was added for CTO, a program that was not released.
This checkbox has been removed from the detail grid of the module.

Record Set Issues (695249, v28.2.0)

The request was created to correct a defect caused by the upgrade to Visual Studio 2013 for v28.1+. In the NBC partnership program adoption dialog (PrismCore 114 Order Decision - Check Titles for NBC Textbook Rental Partnership), if a box was checked or unchecked by the user, the message "Record set is read only" would display, thus making it impossible to modify the records. This has been corrected so the items in the list can be chosen without error.

Department Maintenance (693779, v28.1.8)

The request was created to correct a visual defect in PrismCore Academic Department Maintenance. Previous to these code changes, if a detail line in this module was edited, the line would display blank. This has been corrected so if the detail line is edited, the line will display properly and edits are saved.

Changing Rental Information (694577, v28.1.0)

On the "All History" tab, if the user highlights a Rental XREF and right clicks, the option "Change Billing Information" is available. After changing the tender information in the Edit Rental History Information dialog and clicking the OK button to save the change, the new tender information is now retained.

Optimized Order Decisions Issue (688456, v28.1.4)

The Optimized order decisions program was updating all items to the web regardless if there were changes made to the term/course or not. This was causing a large amount of data to be sent to web bogging down the flow of data for other web updates also and causing time delays for the packets to run. The fix was to look at the triggers being set for a comparison of the term/course request/order decision data and only update when a change has been made.

Rental Return Emails (681433, v28.1.0)

The request was created to correct a defect with Rental Return emails. Previously, if an item was rented and returned that did not have an ISBN, the body of the rental return email was blank. This has been corrected so when an ISBN-less item is returned (via POS or buyback) that the rental return email to the customer will still contain the item information.

NMRP Invoice Issues (681341, v28.1.2)

If an NMRP rental is refunded and the invoice is missing from the refund, an error email is sent for the NMRP transaction. The issue was that if the rental was refunded, and both the original transaction and the refund transaction both had missing invoices, only the refund transaction will show on the 'NMRPPeriodSummary –error notification' email and not both. This issue has been resolved so that an email is sent for each missing invoice only.

Reconciliation (681364, v28.1.3)

There were duplicated lines on the NMRP reconciliation due to the 'Return reconciliation module allowing the user to close the session/account twice (double-clicking the 'complete account session'). This issue was resolved by deactivating the 'complete account session' button after the first click/close.

Verbiage Change (688460, v28.1.0)

The request was created to change the verbiage on two buttons in the NMRP and Partnership v2 Return Reconciliation dialogs in PrismCore Rental Number Maintenance -Hammer Options. The NMRP Return Reconciliation has buttons that now read "Complete Account Session" rather than "Close Account Session" and "Exit" rather than "Close". The Partnership v2 Return Reconciliation dialog now has buttons that say "Complete Period" rather than "Close Period" and "Exit" rather than "Close".

Mail Order Reversals (681405, v28.1.0)

When opening a closed Mail Order Refund for a rental, the associated rental history is no longer deleted from Rental Number Maintenance.

Changing Rental Status (681338, v28.1.2)

When an NMRP return status is manually set back to 'outstanding' that rental's flag is not getting updated back to 'outstanding' on the web. This issue is causing an 'invalid return type' between PrismCore NMRP rentals and the web. NMRP rentals can no longer be set back to 'outstanding' via the 'Edit Rental History Information' dialog, but can be changed manually by development. This ticket allows the communication to the web service to update the status of the rental from 'returned' to 'outstanding' when programming makes this change for support.
This communication is now occurring via PrismCore and the web to keep return types synched.

NMRP Processing (681336, v28.1.7)

Changing the NMRP processes order – to send the store shipments before we send the summary. Previously, the summary was getting generated first. This was causing and error email 'Invalid store shipments' to be sent, since the shipment had not yet reached the web and values did not balance correctly. This issue has been resolved by changing the order to send the shipment first then the summary in the NBC Utility night job.

Copying Term Information (688388, v28.1.4)

When copying terms either from a previous term or to another location if the term being copied has a bad record (blank name or description) or the department does not exist for that location a user error message is displayed. This message is very generic and does not provide the proper information needed to correct the bad record (both for the user and dev). This correction changes the error message to give the exact location of the bad record (campus, dept, term name, and the ids for those as well).

NMRP Rental Error (681389, v28.1.2)

When an NMRP rental transaction, refund, or return was suspended at POS no rental history record was being created (as should happen), but an error message was being sent out. This ITG prevents/ignores those suspended transactions, so they are not included in the error notification for missing history record, since they are not completely finished orders.

P2 Returns at Buyback (688452, v28.1.0)

Prior to the fix, if a Partnership2 rental was returned at buyback, no rental return receipt email was generated confirming the rental return. This has been resolved. When a student returns a Partnership2 rental through buyback at the Buy Books screen, a rental return receipt email is generated confirming the rental return.

RNR Billing (681407, 28.1.0)

There is a new hammer option in Rental number maintenance 'RNR Register Assignments' that allows the user to assign (or unassign) a register to a specific POS system for RNR billing. If no register is assigned to a specific POS, the RNR will be sent to the register in which the original rental was done on and use that terminal id. If the RNR Register Assignment is set, then the RNR billing will use the specified register (terminal id) for all rentals that were done on that POS system. This only affects RNRs done on rental for WinPOS transactions, not for Mail or Web order transactions. In a multi-location environment, the terminal assignment is specific only to the location assigned to the POS system, not the register, and cannot cross locations

Shelf Tag Printing Issues (688399, v28.1.1)

This issue was a shelf tag printing issue in which the used item price was printing on the price tag when the 'new only' check box was checked on the detail line in Course Request. This issue has been resolved.

Rental Books Used / Not Used Again (602563, v28.2.1)

The Rental books used/not used again report generated from the rental number maintenance report menu was not displaying correct information. This problem was caused by the report not filtering correctly causing the totals for the various terms and locations to be combined.

Rental Books Report (602563, v28.2.1)

The Rental books used/not used again report generated from the rental number maintenance report menu was not displaying correct information. This problem was caused by the report not filtering correctly, causing the totals for the various terms and locations to be combined. This has been corrected.

OOD Export File Change (602567)

Create and Queue an export file when various changes are made to an AOD record (this only occurs when the OOD Export/Import runs and creates the current file – not a separate file prior to running the service). As new course requests are added for a term, or existing course requests are updated on the current term dataset, PrismCore will create and queue a current export file. These changes/updates include: 1. A new course request for a new SKU 2. Changes made to fields on the course request (SKU, Est.Enrollment, Instructor, Department, Course, Req. Amt) 3. Disabling, Cancelling, or Deleting a course request 4. A course request for an ISBN that already has an order decision in a new term that is outside the given term 5. Resending of the historical export file This export file will be an ASCII pipe delimited file and will contain a separate line for each Current Term identifier/Term combination for the SKUs. This file is then picked up and used for the AOD processing/updating. Any time a current term dataset is sent for a specific SKU, all current term datasets that include that SKU will be resent.

Rental Sales Fields (695254, 688410, v28.2.0)

Order decision new rental sales and used rental sales fields were not displaying accurate counts and the same with new and used sales fields which also includes rentals. This has been corrected.

Rental Books Used / Not Used Report (602563, v28.2.1)

The Rental books used/not used again report generated from the rental number maintenance report menu was not displaying correct information. This problem was caused by the report not filtering correctly, causing the totals for the various terms and locations to be combined. This has been corrected.

NMRP and Mail Order (681396, v28.1.1)

The request was created to correct an issue with A/R Sales done from WinPOS or PrismCore mail order modules that were allowing the transactions to be tendered to the NMRP or Partnership accounts that were erroneously added to the customer. The NMRP and Partnership accounts exist to track the rebate amounts accrued for either rental program. There have been abnormal situations in past versions where these accounts could erroneously get attached to some A/R customers. If the tender A/R Charge was chosen, these accounts would appear available to be charged for that customer. This has been corrected so if A/R Charge is the tender for the transaction, the account for NMRP or Partnership can no longer be chosen as the account for that customer.

RNR Register Assignments (681407, v28.1.1)

There is a new hammer option in Rental number maintenance 'RNR Register Assignments' that allows the user to assign (or unassign) a register to a specific POS system for RNR billing. If no register is assigned to a specific POS, the RNR will be sent to the register in which the original rental was done on and use that terminal id. If the RNR Register Assignment is set, then the RNR billing will use the specified register (terminal id) for all rentals that were done on that POS system. This only affects RNRs done on rental for WinPOS transactions, not for Mail or Web order transactions. In a multi-location environment, the terminal assignment is specific only to the location assigned to the POS system, not the register, and cannot cross locations.

P2 and Buyback (688452, v28.2.0)

Prior to the fix, if a Partnership2 rental was returned at buyback, no rental return receipt email was generated confirming the rental return. This has been resolved. When a student returns a Partnership2 rental through buyback at the Buy Books screen, a rental return receipt email is generated confirming the rental return.

Change Billing Information (694577, v28.2.1)

Prior to the fix, in Rental Number Maintenance the "Change Billing Information" option on the "All History" tab was not changing tender information for the rental guarantee tender. This has been resolved. On the "All History" tab, if the user highlights a Rental XREF and right clicks, the option "Change Billing Information" is available. After changing the tender information in the Edit Rental History Information dialog & clicking the OK button to save the change, the new tender information is retained.

NMRP and P2 Stock Adjustments (583805, v26.3.1)

For NMRP, the stock adjustment made at reconciliation time be the rented qty - returned qty. For Pv2, the ship qty is incremented as the rentals are returned. The field is still editable to the user at the time of reconciliation.

NMRP Rentals (673083, v27.3.2)

In Rental Number Maintenance, using the hammer option NBC Partnership Rental Reconciliation, when selecting the session (in the NBC Rental Period dropdown), but leaving the PrismCore Rental Period blank, the process will close all of the rental periods for that session and create a PO for each period.

NMRP Reconcile Returns (688459, v28.1.2)

The NMRP reconcile returns view was not filtering down to just NMRP records, but was also displaying regular and partnership rentals as well. This was causing count discrepancies on the web. This fix just implemented the use of the fnmrp flag = 1 to filter out only NMRP records when reconciling.

Apostrophe in Short Description (TFS845, v28.1.2)

Prior to the fix, if the Rental Not Returned process was run for a store location that had an apostrophe in the Short Description field in PrismCore Admin > Store Locations, the process would not register an error when the Rental NR field was unchecked for the Rental Fee line for the store location in PrismCore Admin > POS > POS Non-Merchandise. This has been resolved. If the Rental Not Returned process is run for a store location that has an apostrophe in the Short Description field in PrismCore Admin > Store Locations, the process will fail and register an error in the Rental Process Log when the Rental NR field is unchecked for the Rental Fee line for the store location in PrismCore Admin > POS > POS Non-Merchandise – A Rental Non Merchandise code is not set for Location: XXXXXXX (store location).

V2 Reconciliation Report (TFS968, v28.2.7)

The Rental Partnership V2 Reconciliation report was not filtering correctly based on period selected thus displaying incorrect rental quantities when the same items were used on multiple periods. This has been corrected.

NMRP Transaction Issues (TFS1677, v28.2.12-1)

Prior to the fix, when an NMRP transaction was sent to the web in real-time (WinPOS using Shift4), the format of the processed date was incorrect, prompting an error at the register: Could not validate NMRP Rental. Rental must be validated before completing the transaction. This has been resolved.

Digital Book Changes (TFS1878, v28.2.13)

Prior to the fix, stores with port 80 blocked and/or set to use SSL/TLS protocol were unable to complete a transaction at WinPOS for digital textbooks. This has been resolved. If a store uses SSL/TLS protocol to connect to jumpbooks.nbcservices.com, the process will utilize a port other than 80 without error.

Section Import Changes to Allow Email (TFS1959, v28.2.13)

The section import was updated to include instructor email. It was discovered that, if a school utilizes the new import and doesn't include the instructor email, the import will fail. In order to avoid this, the section import was updated to allow for the user to determine how they would like the import set up. A system parameter has been added to the section import that gives the user the following options:

• Include instructor email

• Include section ID

• Include section ID and instructor email

• Keep standard import formatting

• The default is 'Keep standard.'.

ICS Purchasing

Want Lists and Windows 32 bit (692439, v28.1.7)

Previously, when a user with a 32-bit PC running PrismCore attempted to send a want list using the hammer option at Want Lists, the following error was received, then the program closed: "Error converting data type varchar to datetime." This has been resolved. When a user with a 32 or 64-bit PC running PrismCore sends a want list using the hammer option at Want Lists, the want list is scheduled in Outgoing Message Maintenance without error.

Changing Vendor on PO (681378, v28.1.1)

When changing the vendor on a purchase order selected off of the search results dialog, the first purchase order in the list was also getting changed. The vendor was changed in the vendor dialog (via the vendor ellipsis) on the purchase order header record. When saved it inadvertently changed the vendor on the first record as well. This issue has now been resolved.

Pubnet Issues (688468, v28.1.1)

The request was created to correct a defect in PrismCore Incoming Message Maintenance for Pubnet Purchase Order Acknowledgements. Previously, if the source document being imported contained an "EN" code in front of a 10-digit ISBN, the message would not import properly. This was corrected and fixed.

Autogen Orders (681327, v28.1.0)

When adding a new location in Autogen Proposed Orders to the 'Term/textbook' box the displayed OTB% was not correct or was garbage characters. The issue was due to uninitialized data and has been resolved, so that now when adding a new location, it represents the current default value.

Want List Issue (681387, 695251, v28.1.0)

The request was created to correct a defect in PrismCore Want Lists. When saved report parameters were toggled between Separate and Merged location report parameter lists, the PrismCore program would crash unexpectedly. This has been corrected and the program no longer crashes when saved parameter sets are used.

Autogen Display Issues (688465, v28.1.1)

The request was created to correct a visual defect occurring in PrismCore Autogen Proposed Returns. The Add, Delete, Up and Down buttons along the containers on the right hand side of the module for "Selected Locations" "Selected Vendors" and "Excluded Terms" were being overlapped. This has been corrected so the buttons line up properly above the appropriate containers now.

Adding Locations to Autogen (681327, v28.1.0)

When adding a new location in Autogen Proposed Orders to the 'Term/textbook' box the displayed OTB% was not correct or was garbage characters. The issue was due to uninitialized data and has been resolved, so that now when adding a new location, it represents the current default value.

NBCConnect Issues (681356, 695251, v28.2.0)

NBC Connect not sending due to C:\comm file being empty for want lists. Also, when sending the want list from the 'send' hammer option, it was crashing PrismCore in some cases. Now, when sending a want list via NBC Connect (direct transfer – WPConsole), there must be detail items on the want list. When no detail items are on the want list when sent, the user message 'There are no items on the selected document. Electronic orders must have detail items.' displays, not allowing the want list to send as expected.

Want List Crashing (681387, v28.1.0)

The request was created to correct a defect in PrismCore Want Lists. When saved report parameters were toggled between Separate and Merged location report parameter lists, the PrismCore program would crash unexpectedly. This has been corrected and the program no longer crashes when saved parameter sets are used.

Merchandise Request Issues (TFS501, v28.2.2)

If multiple users are creating new Merchandise Transfers at the same time it was possible for the system to display another user's transfer request instead of the one the original user was creating. For example: if user A created a request for location A and user B created a request for location B – when user A created a second request they were likely to end up displaying the same request that user B just created instead the new second request that user A wanted. This has been corrected.

Incorrect Vendor Assignment in EDI Incoming Messages (TFS1048, v28.2.7)

Wrong vendors were being assigned to EDI incoming messages and then consequently the corresponding PO. This has been corrected.

ICS Returns

Changes Not Saving (681403, v28.1.0)

If a change is made to a credit memo field in the header at Resolve Credit Requests, the change will be saved without error by clicking the "Save Record" button on the top toolbar. Previously, performing this action was causing an "Invalid Descriptor Index" error.

Sale to wholesale Issue (681374, v28.1.0)

The request was created to correct a defect within the "Print Wholesale Sale" report in PrismCore Sell Books to Wholesalers. When the "Include Global Note" report parameter was checked, global notes were being printed for items that did not contain global notes. This was due to a flaw in the report code that was inaccurately assigning global notes where they shouldn't have been. This has been corrected so if an item contains a global note, it will print when the parameter is chosen, and items without global notes will not print any unassigned global notes when the parameter is selected.

Partial Cent Returns (681330, v28.1.2)

When a return was created against an invoice where the cost had partial cents, the return ext. cost in the return detail table was getting populated with a 3-decimal cents value. This was not visible in PrismCore, just the table, but in some cases, especially returns with postage values, this was effecting the values displaying on the outstanding credit request report and could have potential effects also to GL and stock ledger. To prevent this issue from occurring again, a change was made so that the ext. cost doesn't contain partial cents in the table.

ICS Reports

F9 Reports Sales History (688395, v28.1.1)

When displaying sales history using F9 reports, if the item did not have any sales history, a blank row was being returned, causing an error to be displayed. This divide by 0 error is now corrected and no longer returns a blank line when no sales history is present.

Report Generator Issues (TFS978, TFS979, v28.2.8)

When creating a report gen report containing an apostrophe in the name a syntax error was displaying. This has been corrected. Additionally, report scheduler was not saving name changes made to reports in the report generator. This has also been corrected.

Report Scheduler Not Generating Reports (TFS1080, v28.1.3)

Reports were not automatically printing or sending via email from report scheduler. This has been corrected.

ICS PrismCore Admin

POS Transaction Report (690411, 691152, v28.1.3)

The POS Transactions report had the incorrect Subtotal and Total at the bottom of the report. This has been fixed so that the Subtotal and Total at the bottom of the report are correct.

Purge (681431, 681329, 681361, 681434, 681331, 681348, 681413, 681328, v28.1.8)

The 'Can Purge' Check functions have been modified to better filter items in returns, wholesales sales, discrepancy and merchandise transfer details. For one of these items to purge, they have to be within the date range for the purge, but also must be in a closed status and resolved.
Additionally, when a user purged rentals in which there had been failed RNR charges, they received the following error: The delete statement conflicted with the REFERENCE constraint "FK_Rental_History". The conflict occurred in database "prism", table "dbo.RentalAuthoFailureLogDetail", column "RentalHId". This has been resolved. When a user runs purge for rentals in which there have been failed RNR charges, the purge process will complete without error.
Also, a correction was made to the can purge logic for CanPurgeReturn, CanPurgeDiscripancy and CanPurgeWholesaleSale when determining if a return exists on a Credit Memo that cannot be purged. In addition, CanPurgeMerchandiseTransfer needed a logic change to test if MR/MTs attached to Credit Memos can be purged. This change prevents returns, discrepancies, wholesale sales, and transfers from getting deleted prior to the credit memo getting resolved and/or closed. Now the logic checks if the return, discrepancy, wholesale sale, or transfer is complete and closed, and if it is attached to any open/existing credit memos that have not been resolved or closed in addition to the date following within the set purge parameters.
Additionally, a request was created to enhance the stored procedure that controls purging items within the purge process. The changes in this ITG have modified statements in the stored procedure in an attempt to speed up the purging items process.
Further, previously, all stock adjustment comments were being deleted when purge was run, even for those stock adjustments retained, falling outside of the purge parameters. This has been resolved. When purge is run for stock adjustments, all stock adjustment comments are retained for stock adjustments falling outside the purge parameters.
Additionally, when a financial aid account with rental transactions was purged, the user received delete statement errors. This has been resolved. A financial aid account with rental transactions can be purged without error.
Also, customers can now purge Partnership credit memos without error.

SOH to Web Parameter (681352, v28.1.1)

The request was created to correct a bug concerning stock updates from PrismCore to WebPRISM. Previously, it was discovered that the system parameter for "SOH Information Sent to Web" in PrismCore Admin – Store Information – Miscellaneous – Web was not being adhered to when stock was updated to the web. This has been corrected so the system parameter is obeyed when stock updates are sent.

User Issues (681384, 688431, 681385, v28.1.0)

When creating a new user in PrismCore Admin and using the apostrophe " ' " character in the user name (ie. O'Connell), a .NET framework error was displaying instead of the invalid character in user name message. This issue has now been resolved – not allowing the apostrophe character in either the user name or password – this is a syntactical character and has the potential to create other issues if allowed. Other special characters such as dashes, underscores or spaces are allowed.
Additionally, the request was created to implement a change to the user focus when updating/modifying a user's password in PrismCore Admin User Security. Previously, if a user's password was changed by a super user, when the password confirmation dialog would appear, the focus would be in the password field, which is already filled in. This has been changed so the focus is now in the "Confirm" field and the user does not have to move into this field to confirm the password change.
Additionally, when setting your password in user under security, after setting the password and pressing F10, the password confirmation box pops up and the focus is now in the correct spot.
NOTE: The system will not inform you of your domain's password complexity rules. If you need assistance with password complexity, please contact your campus or store IT.

Purge Report (681376, v28.2.3)

When purging credits, the purge report and statistics were not displaying correctly. There was bad data being displayed in the Document/record type and the purging dates were off in the detail and on the header of the report. This has been corrected.

Focus in User Security (685178, v28.0.3)

When Changing a password for a user in PrismCore Admin > Inventory Control > Security > User Security, the system will focus on the "Confirm" field in the Confirm Password dialog box (the cursor will be in the Confirm text box.)

Deleting a User Results in Error (681340, v28.1.0)

The request was created to correct a defect in PrismCore Admin User Security. Previously, if a user was deleted that contained a space anywhere in the "Username" field, an "Incorrect Syntax" error was displayed. This has been corrected so a user can be deleted properly from this module, even if the "Username" field contains a space.

Disabling Tenders (681357, 28.1.1)

The request was created to correct a defect when disabling tenders. Functionality had been added to v26+ where the ability to disable a tender for all locations was added, where previously it could only be done by location. Under certain circumstances when tenders were disabled using the new functionality, they were still available in the available tender list. This was causing issues posting sales. The issue has been corrected and when tenders are disabled globally, they never appear in the available tender list.

Passwords for Distributed Server (690583, v28.1.2)

The request was created to correct a bug in the process of passwords flowing to the distributed database for users when changed in PrismCore Admin. Previously, if a user existed in SQL - Security - Logins with the "Check Password Expiration" flag unchecked, then changing that user's password would disrupt the flow of subsequent attempts to flow passwords from main to distributed. These changes allow the password change to flow for users who have "Check Password Expiration" checked or unchecked and doing so does not disrupt the flow from main to distributed.

Loading Buyer's Guide (TFS1835, v28.2.13)

Prior to the fix, if a user did not open PrismCore Admin to 'Run as administrator', and then attempted to load the Buyer's Guide using the option to 'Load New Database from File', the process would abort with a copy failed system error. This has been resolved. If a user opens PrismCore Admin normally with a double-left click, and then loads the Buyer's Guide using the option to 'Load New Database from File', the process will complete without error.

ICS Miscellaneous

Changes for Resetting Passwords (679486, v28)

The request was created to correct two issues with the new way in which users are added and updated based on PCI/PA-DSS requirements. New processes had been added in v27 to assign a password to a cashier when added to the POS Cashiers module. This creates a record in the update user table in prism_security. This then updates to any distributed systems. This ITG corrects a defect that was happening when the location the cashier was added to was not a distributed location. A record was getting created in update user which was causing issues updating other records in the table, because it was not a distributed location. This has been corrected so If the location of the cashier is not a distributed (distributed =2 ), then no record will be added to the table, because no distributed databases will need to be updated with the login info. Another defect was also corrected by the changes in this ITG. Due to some previous changes for v28+, the "User Must Change Password at Next Login" flag in SQ Security - Logins - Properties was not being updated when the password change is initially performed at the POS Register upon first login. This has been corrected so when the new user changes passwords upon first login of the register, that flag is updated on the main database, so they don't have to change their password the first time they log into PrismCore.

SQLCMD (677613, v28)

Users were not able to change passwords at the register unless SqlCmd was installed on the register. When attempting to change the password, the user was getting a 'systems security exception' error and the password was not allowed to be changed. This issue has been resolved.

WPServer Error (679485, v28.0.2)

The request was created to correct a defect discovered during early testing for v28+. It was discovered that certain WPServer services were throwing an error in to the system log. ". Unable to load DLL 'WPCommD.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E). The cause of this defect was isolated to a Veracode scan that was conducted after originally cutting build v27.3.2. The Veracode scan was causing project files to mistakenly call the above dll, which is only typically used in debug mode. This has been corrected, so v28.0.2 no longer uses the project files affected by Veracode and uses only the traditional project files during compilation. The error is no longer reported.

WPServer Attempting to Log In (688463, v28.1.1)

The request was created to correct a defect where WPServer was attempting to login when PrismCore Admin or PrismCore started up. This has been corrected so when PrismCore or PrismCore Admin are opened, no attempt to login is made automatically by WPServer.

EDA (546561, v28.2.0)

The request was created to add the buyer's guide default price for items being added to sales to wholesaler on the mobile app, rather than the previous default of $0.00. These can be changed if needed when added.

A/R Orders with Toolkit (688393, v28.1.1)

This change allows iPhones to process A/R transactions with multiple accounts assigned to a customer and flag any other orders that have restrictions and need to be processed via PrismCore tender dialog using an '!' character.

Credit Request Focus (681391, v28.1.0)

When adding items from a credit request to a credit memo using the Line Items tab, the focus was jumping to a different credit request after each item. This is no longer happening.

Quick Search Invoicing (681360, v28.1.0)

The method in the quick search utilizes the same method as Invoice Detail to calculate the NYI (the difference between the PO's Invoiced Qty for the SKU and the Received Qty for the SKU, accounting for the possibility of multiple invoices covering the Received Qty.)

Mobile Toolkit (688445, v28.1.1, v2.21)

Rental Xrefs were not able to be scanned into a mail order or web order for the same item being purchased, and not rented, when a large number of xrefs already exist in rental number maintenance. This issue has now been resolved.

Enrollment Import (681349, v28.1.1)

The Enrollment import file format was only allowing up to 10 characters to be input when the Course and Section imports and UI allowed up to 20 characters for course name to be input. When the enrollment import runs it matches on Term as well as the Course request information (course name and section) if there is not a match the enrollment records are not imported correctly. This ITG changed the column course_name in the prismtrn table Import_Student_enrollment format to allow up to 20 characters to match the other corresponding tables.

Pubnet and Ingram Issues (688438, 690584, v28.1.9)

Pubnet and Ingram file transfer was not sending orders or populating the c:\comm file. Since the comm file was not updating, there was nothing for the service to pick up causing it to error out in WPConsole and appear to be endlessly running.

Buy Books (688428, v28.1.1)

In the Buy Books module when any of the record sets are empty a user message is to display. This was determined to be caused when a location was deleted from the BB session location tab which was also populated in the BB session workstation tab. This issue has been resolved by not allowing a location in session setup to be deleted if in use on the workstation tab. If the location is deleted the user message, 'location cannot be delete, data exists' displays and does not allow the deletion. In order to delete the location from the location tab, the location must first be deleted from the workstation tab.

NMRP View (681339, 28.1.0)

The request was created to modify NMRPPeriodSummary_vw. Previously, this view, which is also queried when NBC Utility runs, was taking too long at some NMRP sites and causing NBC Utility to fail. Several areas of this view were modified to make it run more efficiently.

Trace Logs (681448, 28.1.0)

The request was created to modify the length of time in which trace files are kept in the c:\prism_backup folder for PCI compliance. The changes cut the length of time from 7 days to 2 days, because too many files were being generated and archived, thus potentially causing disk space issues on ICS and/or POS servers.

Mobile Sale to Wholesale App (533724, v28.2.0)

The request was created to add the buyer's guide default price for items being added to sales to wholesaler on the mobile app, rather than the previous default of $0.00. These can be changed if needed when added.

Transporting Usernames (677612, v28.0.2)

The request was created to move alter statements to dynamic SQL statements for security purposes when storing/transporting PrismCore usernames and passwords.

Reporting Errors (681333, v28.1.1)

The request was created to add functionality to WPConsole when reporting errors in the job histories for each service. Previously, some lines in the system log would have a blank AppText field, thus the job history in WPConsole would be displayed as blank.
The enhancement in this ITG will put any text found in the ODBCText field into the job history view in WPConsole if the AppText field is blank. This should provide better logging for certain scenarios in which blank errors appear in WPConsole, even though the error was logged in the ODBCText field.

Password Retention (608512, v1.84)

If the "Retain Password" flag is not set, and the settings menu is accessed, when the username/password screen is accessed, it is possible to hit "Settings" then "Back" without ever filing in a password. This will attempt to log into the app. Login will not be allowed and will be unsuccessful and return the user to the username/password screen with the message "Alert. Please Login. OK". User PRESSES OK, at this point, if the system settings need to be re-configured (for example the phone changes store locations so a different IP or port is needed), the IP and Port screen can be accessed by the user. Mobile Toolkit allows the user to access the system configuration screen, even if no successful attempt has been made.

Trace Logging (681351, v28.1.0)

The request was created to move the check for trace logging to WPServer. Now WPServer will check the system parameters table for "NBCUtil_Trace_Status". When this value is 0, trace logging is not turned on, and the nag message "Error 106 please call support" will still appear. When the value is set to1, the message will not appear because logging is turned on.

NBCUtil Line to Distributed (681382, v28.1.0)

The request was created to add NBC Utility to the v28.1.0 server side updater when run on distributed servers. This will add NBC Utility to any server where the updater is run if it's not already there. This is due to the new implementation of username/password flow for PCI standards.

Record Set Errors (692442, TFS335, 692333, TFS536, TFS606, TFS967, TFS982, TFS1009, TFS1123, TFS1427, v28.1.7)

These requests were created to correct recordset errors that was caused by the upgrade to visual studio 2013 compiler and the needed modifications to snapshots/recordsets. This included the following modules: Tax Codes, Transaction Types, Matrix Maintenance, Physical Inventory, Registers, Manual Credits in A/P, Balance Sheets, Inventory Maintenance, Account Maintenance.

Shipping Import Issue (688398, v28.1.2)

Prior to the fix, invalid characters in the shipping import/export file would prevent the file from transferring without error. This has been resolved. PrismCore executes a SQL process in the background that analyzes and removes invalid characters within the shipping import/export file prior to transfer.

Potential Web Issue Corrected (688416, v28.0.2)

The request was created to correct an issue that would potentially cause updates to WebPRISM to be rendered non-functional after updating to v27. A modification to the web_routing table made in v25 could potentially cause this issue if the same routing IDs were used for services on a server updating to v27. This would be a rare occurrence, but could potentially cause WebPRISM updates to fail. The fix was placed on UVA's site and included in the 28.1.1 update. It backs out the change from v25 to prevent the problem from occurring in the future.

Security Enhancements (681416, v28.1.0, TFS1378, v28.2.12)

Enhancements have been added to security for resetting passwords to ensure update user records are only created for distributed type 2.
In addition, improvements were made to the way passwords flow when 'change password' or 'reset password' is used at stores with multiple distributed systems. If the user password is 'reset' on Main – PrismCore Admin/user security, the new updated password will flow from Main down to each distributed POS when each systems NBC Utility (NBC Util) runs (each POS picks up from the Main when NBC Util runs).
This password flow also occurs when the user 'changes' their password at the register via the 'File' menu (File/Change password). In this case, the new password will be changed on the POS, then get pushed to Main when NBC Util runs. Main takes it and makes it ready for the other POS distributed systems to pick up when their NBC Util runs, thus updating the user's password at all locations.
The user can also 'change' their password via PrismCore (which is considered – Main, same as PrismCore Admin), using File/change password as well. Again, the password changes on Main, then when the NBC Utils run for each location POS they pick up the new changed password from Main.
The difference between 'Reset' and 'Change' password is who is doing the changing. Resets are typically done by managers/admin so the 'reset' is done in PrismCore Admin User Security or when adding the user as a cashier to a POS. Change passwords are typically done by the user, from PrismCore (sometimes PrismCore Admin if they have rights), or POS register – File/change password menu option.
Once a password has been reset in PrismCore Admin or a new user is added, that user will be prompted on their first login to change their password, same as always and password complexity rules also still apply based on system settings.
In 'login properties' seen in SQL under security/logins, there are 3 password control flags that determine how or when passwords can be changed. These 3 flags are: 'Enforce Password Policy', 'Enforce Password Expiration', 'User Must Change Password at next Login'.
When a new user is created, all 3 flags are set. Once the new user logs in and changes their password for the first time, the 'User must change password at next login' will be deactivated until the password is reset again.
A check was also added, so that if a password change caused an error to occur in NBC utility, that it would not stop the job from running completely, but just log the offending user name in the log seen in NBC utility.

Fully Managed Back Office Changes (TFS1901, v28.2.13)

In order to accommodate the FMBO environment, changes were made specific to that configuration to allow User and System DSN connectivity.

POS Changes

Customers Not Sending to Distributed Systems (TFS1108, v28.2.8)

Prior to the fix, there was an improper check for customer account when sending a new customer from the distributed server to the main, resulting in the transaction not flowing to the main correctly. This has been resolved. When sending a new customer from the distributed server, the transaction will flow to and correctly display on the main server (ex. POS Transaction Inquiry, Customer Maintenance, AR Transaction Inquiry.)

Rework Tender Retail Receipt (668102, v28)

The Tender Retail receipt was not printing on credit card tendered receipts using Tender Retail. This has been fixed so that the Tender Retail receipts prints with the Customer and Merchant receipts (if both are set to print).

Manager Override Change (676725, 681425, v28)

Code has been changed for Manager Overrides. Before the change a manager override was done by entering a manager password which was not tied back to a specific user's account. Now the manager's password is tied back to a specific user's account to allow for a better audit trail.

Campus Account Balance (677544, v28.1.0, v1.8.3.6)

Code has been added to flow the campus account balance field in the customer and merchant receipt templates. When a campus account (CBORD XML) account is used, the balance will print on the receipt and display on the Pole Display. To display the balance on the pole display, the "Show Campus Debit Balance On Line Display" checkbox needs to be checked in Thunder Admin > Pos > Parameters.

Register Totals Report (690406, v28.1.2)

When more than one check was used on a transaction as the tender, the POS Register Totals report was displaying the wrong count for Check tenders. This has been fixed so that when more than one check is used on a transaction, each time a check tender is used, the count on the POS Register Totals report is correct.

Distributed Database Update (688462, v28.1.1)

The request was created to correct a defect during updating inventory information from main databases to distributed databases. If an item existed on the distributed database, but didn't have an inventory record on the distributed database (a rare occurrence), then any inventory updates done to that item from PrismCore would not update the distributed properly. This has been corrected so if an item is present on the distributed without an inventory record, then item/inventory updates to the POS distributed database still take place.

PRISM POS Encryption with PrismCore (TFS1113,

Prism POS encryption for rental guarantee tender not decrypting properly on the PrismCore side. This has been corrected.

POS Transaction Report (691152, v28.1.3)

The POS Transactions report had the incorrect Subtotal and Total at the bottom of the report. This has been fixed so that the Subtotal and Total at the bottom of the report are correct.

Signature Capture Timeout (681325, v28.1.2)

A "Signature Capture Timeout for Signature Only" parameter has been added to PrismCore Admin > Inventory Control tab > Parameters > System Parameters > POS. When set, the pin pad will wait for signature for the amount of time in seconds that is entered in that field. This is for non-credit card tendered transactions that require signature. If a signature is not provided in the amount of time entered in this parameter, the pin pad signature prompt will time out.
NOTE: The timeout works exactly right with Shift4 but seems to timeout early on Tender Retail transactions. If this is an issue, then a new ticket can be created.

Changing Guaranteed Tender (690408, v28.1.2)

Previously, if a user attempted to change the rental guarantee tender for an NMRP rental, or a store managed rental on the same transaction with an NMRP rental, the information in the Govt ID Agency & Govt ID Number fields would be deleted. This has been resolved. If a user changes the rental guarantee tender for an NMRP rental, or a store managed rental on the same transaction with an NMRP rental, the information in the Govt ID Agency & Govt ID Number fields will be retained.

Passwords Not Flowing (690414, v28.1.2)

Previously, if a user's password was changed by a super user in PrismCore Admin User Security, that password was no longer flowing to the distributed location if the user was previously configured for rights at the distributed location. This has been corrected so when a password is changed by a super user, the password is updated on the distributed location as well.

Blank Line on Receipt (688402, v28.1.2)

The receipts were printing a blank line between the description and the SKU. This has been fixed so that the blank line is removed.

Item Not Found Scanning Issue (688407, v28.1.1)

When an item that was not in the system was scanned, no message would alert the cashier that the item was not found. This has been fixed so that if an item is not found, the message "Item (barcode) not found".

Transaction Types (688422, v28.1.1)

When trying to add or delete a row in Transaction Types, those options were always disabled. This has been fixed so that the Add and Delete options are enabled for the Transaction Types module.

Net sales by Tax Code (688470, v28.1.2)

When the transaction tax code was set to zero, the Net Sales by Tax Code Report was off. This has been fixed so that the Net Sales by Tax Code report is correct when transactions are run that are nontaxable or tax exempt.

Password Changes (691157, v28.1.3)

When updating a user's password in User Security, the "Must Change" flag wasn't flowing to the distributed. This has been fixed so that when a user's password is changed in User Security, it flows correctly to the distributed database.

Memberships with Dollars Off (681326, v28.1.2)

There were issues in the field with Memberships not updating correctly that had membership "dollars off" discounts. This has been fixed so that when a membership account is used, the balance is updated to reflect the amount spent after each transaction.

Posted Sales Item Detail (681359, v28.1.0)

On the Posted Sales Item Detail report generated from the reports menu of the Manual Sales module, the Posted FYTD qty was not displaying correctly. The Posted Sale Qty should match the Posted FYTD qty minus any returns. This issue has now been resolved.

POS Transaction Report (688472, v28.1.1)

The POS Transactions report was incorrect in the Subtotal and Total fields when multiple tax types were used. This has been fixed so that the report displays the correct information.

Disabled Tenders (681357, v28.1.1)

The request was created to correct a defect when disabling tenders. Functionality had been added to v26+ where ability to disable a tender for all locations was added where previously it could only be done by location. Under certain circumstances when tenders were disabled using the new functionality, they were still available in the available tender list. This was causing issues posting sales. The issue has been corrected and when tenders are disabled globally, they never appear in the available tender list.

RR Report (666736, v28.1.2)

If an RR report was done at the register where an amount exceeded $10,000, the error "Error converting data type money to decimal" was being given. This has been fixed so that an RR report can be printed at the register without error when an amount exceeds
$10,000.

TI Refunds (681401, v28.1.0)

There was an issue with Transaction Inquiry(TI) refunds with AR sales if the price of the original item was updated in item maintenance prior to the refund being done. If the item price had been changed after the sale, when the TI refund was done, it was only allowing the new price of the item to be refunded not the original price the customer paid. This issue has now been resolved.

Tax Shift (681402, v28.1.0)

Tax was not allocated correctly when using tax shift at the register for an item that is normally a taxed item. This issue was causing a varied discrepancy between the manual sales report 'posted sales – department detail' and the POS 'net sales by tax code' report. This issue has now been resolved.

Receipts Print Without Error (688405, v28.1.4)

Receipts with signatures and reprinting receipts with signatures was giving the message "String or binary data would be truncated. The statement has been terminated". This has been fixed so that receipts and reprinted receipts that contain signatures print correctly without error.

Error Returning P2 Rental (681394, v28.1.1)

The request was created to change the verbiage of an error message seen at WinPOS when Partnership v2/NMRP items are trying to be refunded at a different POS location from which they were rented. The error message has changed from "Rental item must be refunded at same location in which it was rented" to "Rental item must be refunded at same POS System in which it was rented".

Transaction Inquiry (681418, v28.1.0)

Issues with printing receipts from PrismCore Admin/POS/Transaction Inquiry reports menu. When printing reports tax was not getting included on the report totals but was included on the UI transaction inquiry screen. This issue has now been resolved. Some older transactions have had their tax information deleted from the tax table, so all testing was done with new POS transactions.

Credit Card Settlement (691661, v28.1.5)

The Credit Card Settlement report was not printing when Mobile POS transactions exist. This has been fixed so that the Credit Card Settlement report prints correctly when Mobile POS transactions exist.

DCC Column Added (488440, 683126, 688453, 683126, 680581, v28.1.1)

A DCC column has been added to the POS Transactions report between the "SKU" and "Description" columns.

POS Transactions Report (674735, v28.1.5)

Multiple entries of the same NMRP rentals were not showing in the Electronic Journal or on the POS Transactions report. These issues have been fixed so that when an NMRP rental is rented multiple times on the same transaction, all items are included and show in Transaction Inquiry and Electronic Journal.

Refunding Bundles (688381, v28.1.8)

When scanning the barcode on a bundle, only the rentable component was being added to the transaction. It was not bringing the other bundle or other component. When a rentable component XREF is scanned on a return, the following message is now given: "POS Sales with Rental XREF (xref) is Bundle Rental For Bundle SKU (sku) with Component (sku sku) Purchaser may return the Bundle (SKU sku) for a FULL Refund or return Rental Component SKU (sku) for a Partial Refund. Is this a Full Bundle Refund?" If Yes, the entire bundle will be refunded. If No, then only a partial refund will be given for the rentable component. Also, when running a TI refund after the rental price has changed, an error was given not allowing the transaction to be completed. This has been fixed so that the transaction can be suspended until the price is fixed and then retrieve the transaction to complete it.

Manager Override (688432, v28.1.6)

A few changes were made to the Manager Override.

• Allow a user/cashier with Manager rights to override.

• Have the default prompt to the Cashier Username field.

• Have the existing user be blanked out. (User is displayed on Secure Terminal).

Templates No Longer Require Flash (688449, v28.1.2)

The templates for WinPOS have been changed to no longer have dependency to the Flash Plug-In. This means that any moving image that was dependent on the Flash Plug-In has been removed.

Discounted Dollars (681412, v28.1.1)

The Register Totals Report was showing returned discounted dollars as negatives instead of positives in the Dollars Off field. This has been fixed so that the Dollars Off filed displays the correct amounts for sales and refunds.

Shift4 Change (676728, v28.0.1)

The request was created to add the ability to have location-specific Ecom/MOTO Client Authentication Tokens and Client GUID values. Prior to this ITG, the only place to enter these values was in WPConsole – Shif4 – Properties. The field "Shift4 Ecom/MO Client Authorization Token" in WPConsole will still exist and function as normal. The fields "Shift4 Ecom/MOTO client GUID" and "Shift4 Ecom/Moto Client Auth Token" have now been added to PrismCore Admin Mail Order General Parameters, so separate locations doing Mail/Web order processing with Shift4 can enter unique Client Auth Tokens and Client GUID values if desired. These values are added in order to acquire the Shift4 Access Token, which is stored in the database and cannot be viewed in the PrismCore Admin user interface. Once the Access Token is acquired, transactions can be processed normally.

Changing Passwords at the Registers (677613, v28.0.2)

Users were not able to change passwords at the register unless SqlCmd was installed on the register. When attempting to change the password, the user was getting a 'systems security exception' error and the password was not allowed to be changed. This issue has been resolved.

Returning Rentals to Other Locations (681394, v28.1.6)

The request was created to change the verbiage of an error message seen at WinPOS when Partnership v2/NMRP items are trying to be refunded at a different POS location from which they were rented. The error message has changed from "Rental item must be refunded at same location in which is was rented. to... Rental item must be refunded at same POS System in which it was rented"

Signature Capture (690410, v28.1.2, v1.8.4.3)

When signature capture is turned on for tenders in PRISM360 using Tender Retail, the signature capture was not working and a large signature would cause a buffer overrun. Both issues have been fixed so that signature capture using Tender Retail with PRISM360 transactions work correctly without error.

WinPOS and Bundles (681388, v28.1.7)

WinPOS was not handling exceptions thrown by bundle scripts. This has been fixed so that if an exception is thrown, the transaction can be suspended or cancelled.

Discount Changes Not Flowing to P360 (681404, v28.1.2, v1.8.4.3)

When a discount was changed from percentage to dollars, there was a transport issue to PRISM360. This has been fixed so that if a discount is changed from percentage to dollars, then the discount is dollars off. If changed from dollars to percentage, then the discount is percentage off.

RR Reports Not Printing (691153, TFS1124, v28.2.1)

A register was not able to print an RR report. A variable causing the issue was not increased enough. This variable has been increased and RR reports are printing correctly. Also, a change was made to not include RNRs on RR reports (generated from the register), but to include them on the Register Totals Report generated from PrismCore so the totals balance on the other register reports.

Adding POS Users from 360 Admin Tool (691149, 690401, v1.8.4.7, v28.1.5)

Code has been added so cashiers can be setup on PRISM360 through the Admin Tool, Thunder Admin > Security > Users. If a cashier is added here w a transaction flows back to PrismCore, Transaction Inquiry shows the cashier name followed by "360 Cashier".
The user is also displayed in the User Security Module. The Comment field displays "Cashier added by 360 code". Since the cashier is PRISM360 specific, the cashier cannot be used to log into a WinPOS register.

A/R Half Sheet (690584, v28.1.3)

The A/R half sheet insert was incorrectly displaying the balance due. This has been fixed so that the A/R half sheet insert prints the correct balance due.

Discount Plans Not Flowing to P360 (690417, v28.1.2, v1.8.4.4)

Discount Plans were not flowing correctly from PrismCore to PRISM360. This has been fixed so that Discount Plans flow correctly from PrismCore to PRISM360. if a DCC is set up for a percentage off Discount Plan, that DCC will get discounted at the register. If a DCC is removed from the Discount Plan, no discount is given at the register.

POS Discount Field Changes (690407, v28.1.2, v1.8.4.3)

When setting the POS discount "Retail/Cost" field to "Above Cost", that change would not flow to PRISM360. This flag has been added so that discounts set to "Above Cost" flow to PRISM360.

New Customers Not Flowing to P360 (690405, v28.1.2, v1.8.4.4)

If a new customer was added at the PRISM360 register but the transaction was cancelled, that customer was not flowing to PrismCore. This has been fixed so that if a new customer is created on a cancelled transaction, the customer will be created and flow to PrismCore.

Cashier Deletions Not Flowing (690402, v1.8.4.7, v28.1.4)

If a cashier was added in PrismCore and flowed to PRISM360 and then the cashier was deleted on PrismCore, the cashier was still showing on PRISM360 and the cashier could login to a PRISM360 register. This has been fixed so that if the cashier is deleted on the PrismCore side, the cashier is also deleted on the PRISM360 side and the cashier can no longer login to a PRISM360 register.

RR and CR Reports If Store Isn't Closed (688425, v28.1.1)

The RR and CR reports from the register were combining transactions if the store was opened for multiple days. This has been fixed to look at the current date and not the 'store open for' date.

Account Balances Not Flowing (681406, v28.1.3, v1.8.4.6)

A/R account balance deletions were not flowing to PRISM360. This has been fixed so that when an A/R account balance is deleted, it flows to PRISM360.

Parameter Change (688387, v28.1.1)

The text of the paramdesc for Tender Retail has been changed to use a better description to reflect the protocols in use. The text has been changed from "Use SSL Connection" to "Use cryptographic protocol based connection."

SqlCMD (681428, v28.0.2)

Users were not able to change passwords at the register unless SqlCmd was installed on the register. When attempting to change the password, the user was getting a 'systems security exception' error and the password was not allowed to be changed. This issue has been resolved.

Pin Pads and Tender Retail (688471, v28.1.2, v1.8.4.3)

When a pin pad was used with Tender Retail and not in P2P mode, the customer signature was prompting twice. This has been fixed so that the customer is only prompted one time to sign.

Issue with Shift4 (688418, v28.1.2, v1.8.4.3)

PRISM360 was not handling the FR08 Void from Shift4. This has been fixed so that the PRISM360 correctly handles the FR08 Void from Shift4.

Jumpbooks and PRISM360 (688394, v28.1.2, v1.8.4.3)

Deletion of Jumpbooks were not flowing to PRISM360 which was causing the Jumpbooks to still be active on PRISM360. This has been fixed so that if a Jumpbook is deleted in PrismCore it will no longer show as a Jumpbook in PRISM360.

POS Transaction Report Error (688458, v28.1.1)

The request was created to correct a defect in the POS Transactions Report found in PrismCore Admin Closing Reports Setup and PrismCore Admin POS Transaction Inquiry. Previously, when the report was generated, an error stating "Enter Parameter Value" would appear and the report would not generate. This has been corrected so the report generates correctly out of both modules.

Net Sales by Tax Code (TFS508, v28.2.7)

The qty taxed, sales totals and Ext price columns on this report are only a summation of the columns, so if multiple tax types exist it will appear that there are multiple items, but it is just one transaction with multiple tax types. These totals were actually removed at one time, but then requested that they be put back on. The only actual real total is the tax amount totals and that is correct. This report cannot be matched to the register sales totals report except on the tax amount.

Split Tenders (TFS556, v28.2.4)

Prior to the fix, when a transaction was completed on PRISM360 with a split tender, one taxable and one tax exempt, the transaction would not be recorded on the Net Sales by Tax Code Report in PrismCore ICS. This has been resolved. When a user completes a transaction on PRISM360 with a split tender, one taxable and one tax exempt, the transaction will be recorded on the Net Sales by Tax Code Report in PrismCore ICS.

Tenders for New Locations (TFS601, v28.2.3)

It was noticed as new location/pos systems were added to PrismCore Admin that tenders were being added automatically to these new POS systems. This tenders were not being added correctly. It was decided that no tenders should be added automatically. They should all be added manually so that only the tenders needed are added.

Register Totals Report (TFS1659, v28.2.12-1)

There was a "Change Due" issue on the Register Totals Report. This has been fixed so that when a transaction is generated with Change Due, the report displays the "Change Due Count" and "Change Due" correctly on the report.

Tender Retail Settlement Failed (TFS1682, v28.2.12-1)

The Closing Store/Settlement process for Tender Retail was giving a record set error. This has been fixed so that the store can be closed and settled without error.

Shift4 Changes (TFS1950, TFS1896, v28.2.13)

Mail Orders were not being prompted at the pin pad. Code was changed to remove "key" from credit card field. This allows the pin pad to prompt for the card number at the pin pad. Also, for the Shift4 certification with Ecom, Shift4 requested that tokenstoreserialnumber be added to the 07 request. Ecom transactions were run and the trace files were sent and approved by Shift4.Mobile Toolkit

N/U/T Prompt Removed (572299, v2.12)

The request was created to remove the N/U/T prompt for Order Fulfillment. This was completed, however at the time it caused the program to not be able to correctly pick up 13-digit barcodes without the extension. This has been corrected as well.

iPhone Timeout Issues (669661, v2.13)

The socket system will now timeout when the user actually has a socket, but it is not one that is connected to the backend system. Since the protocol messages being sent will never be answered, it will now timeout in the default 90secs Apple uses to indicate the connection is not working.
This will bring the user an Alert, and then let them change their settings. Alerts –

• Error: Check your settings. Unable to connect

• Error: Connection to server failed

• Error: Connection to server failed

• <Return> button has been changed to be a <Done> Button, and on pressing it, it dismisses the onscreen keyboard.

The 3 alert boxes are there by OS, since the connection is invalid, it pops up one box for each error.

Rental Xref (680633, v2.16)

When picking rental order items in Mobile Order Fulfillment, the user is required to enter a Rental XREF. If that item is deleted via the minus icon or cancel button, and re-added, the user is prompted to enter a new Rental XREF. This is required whether using batch or non-batch mode.

Rental Tender (679390, v2.16)

The Rental Guarantee Tender displays next to the "Guarantee" text in the Order Detail screen.

Toolkit and A/R Orders (681482, v28.1.1, v2.21)

Order Fulfillment was unable to process AR tenders. This issue has now been resolved. AR tendered orders now either completely process via Toolkit Order Fulfillment, or are displayed as 'unprocessable' due to DCC or tax exempt limitations, but the user can still complete the order via the Ship Mail Order module using the Tender Dialog.

Batch Mode Xref (675454. V2.21)

If order fulfillment is in batch mode, rental items are not prompting for xrefs when the order is picked/shipped. This issue has now been resolved.

Serial Numbers Limited to 25 Digits (592189, v2.21)

The request was created to set a limit on the number of characters sent for serial numbers from Order Fulfillment to PrismCore. Previously, a serial number of more than 25 characters could be sent. This was causing numerous issues in PrismCore. The changes in this ITG implement an error message if more than 25 characters are entered into the Serial Barcode field in Order Fulfillment: "Length Error Xref cannot exceed 25 characters OK".

New Error Message (691193, v2.22)

Enhancement to have a better user message display when receiving an 'empty message' from the server in Order Fulfillment. This 'empty message' was usually seen when doing an NMRP rental on an order. When the order come into Order Fulfillment and was processed the order would just state 'status OK' but the order was not actually complete, because the user actually had to ship the order from Ship Mail Order. The new user messages - instead of the 'empty message' tells the user the problem and that they need to complete the order in PrismCore before it will close.

FA Module (691195, v2.22)

Toolkit's Financial Aid module was crashing when using the camera option to scan a barcode. Now when scanning a student id (the barcode meant for this module), the id will display in the search box and display all information related to that students account(s). This module does not have a batch option, nor does it leave the camera open after each scan like others because it is meant to scan ids – basically one time scanning.

iOS 9 Support (681485, v 28.1.7, v2.22)

Support has been added for iOS 9.

Orders Unable to be Processed (694578, v28.2.2)

Prior to the fix, mail/web orders with the following would not be shown as being able to be processed in Mobile Toolkit Order Fulfillment unless the PrismCore tender dialog was used before fulfillment:

• A/R Account that was tax exempt

• A/R Account that had DCC restrictions

• A/R account that used account discount

This has been changed. Mail/web orders that have A/R tenders with restrictions are shown as "workable" (able to be processed) in Mobile Toolkit Order Fulfillment.
However, the following restrictions will still be shown as "non-workable" (not able to be processed.) They must still be processed in PrismCore ICS:

• Multiple A/R tenders that are a mix of tax exempt & taxable. They all have to be either one or the other to be workable in mobile toolkit.

• A/R account flagged with an account discount (account-wide discount, not a DCC discount)

• A/R account with DCC restrictions & not all items on the order qualify

• A/R account with DCC restrictions with a discount, & an item on the order qualifies

In addition, if an order has tax on it, but the A/R tender being used is tax exempt, the tax will be removed before processing the tender.

Rental XREF Already Assigned (685040, v28.1.1)

This fix allows an item that has numerous established Rental XREFs to be picked without error in Order Fulfillment in Mobile Toolkit.

Server Connection Error Processing NMRP Web Order (TFS1620, v28.2.13)

Prior to the fix, when selecting to 'Ship' a web order with an NMRP rental in Mobile Toolkit Order Fulfillment, server connection errors were triggered in the application and no packing list printed, however, the order would change to 'Closed' status in PrismCore. This has been resolved. When selecting to 'Ship' a web order with an NMRP rental in Mobile Toolkit Order Fulfillment, the application will first display the message "Please Wait, Updating Order" while connecting to the server to process the order, then the user will receive the message "Status Order Successfully closed." The Mail Order Packing List will print and the order will change to 'Closed' status in PrismCore.

Integrated Accounting System

Gift Certificate Sales - 4126

Multiple Cards Exist (681381, v28.1.0)

Existing gift card balances were getting updated inadvertently when auto generating multiple gift cards in gift certificate sales if the card number already existed. To correct this, a user message 'gift certificate number 'GC-#####' already exists' now displays and does not allow the number to be regenerated, and added to.

Journal Entry Maintenance - 4203

Sort Order Corrected (681373, v28.1.0)

An enhancement was made to the Journal Entry Maintenance default sort order to make it more useful. The new default sort order is now by ascending Transaction Number.

New Manual Journal Entry Causing Issues (TFS1017, v28.2.7)

Prior to the fix, when the user created a new manual journal entry using the Insert Record button on the toolbar, and then left-clicking the <OK> button in the Add Journal Entry dialog box in Journal Entry Maintenance, the record displayed on the screen was not the one just created. It was instead a previous transaction. The user then had to conduct a quick search to locate the new record. This has been resolved. When the user creates a new manual journal entry using the Insert Record button on the toolbar, and then left-clicking the <OK> button in the Add Journal Entry dialog box in Journal Entry Maintenance, the record displayed on the screen is the one just created. The user can then enter further information in the header and detail.

A/R Transaction Inquiry - 4111

Display Issue (688429, v28.1.1)

The request was created to correct an inconsistency in A/R Transaction Inquiry. If an item was purchased on an A/R Transaction that was also on a sales event, the full price was being displayed in the "Price" field in the detail grid. This has been modified so the price of the item at the register (less the sales event) is displayed in the grid.

A/R Daily Transaction (688443, v28.1.2, v1.8.4.3)

ROA Pay ins, ROA Pay Outs and GC purchases were not showing on the A/R Daily Transaction Report. This has been fixed so that the A/R Daily Transaction Report shows ROA Pay Ins/Outs and GC sales and transactions tendered with a Gift Certificate.

Membership Customer Maintenance - 4301

Issues Adding Customers (688421, v28.1.1)

The request was created to correct a defect when adding membership accounts to a customer in PrismCore Membership Customer Maintenance. Previously, a message stating "Record set is read only" was given when attempting this action. This has been corrected so no error is displayed and accounts can be added to the customer record.

Membership Transactions (681390, v28.1.2)

The request was created to correct a defect in PrismCore Membership Transaction Inquiry when viewing transactions containing type substitutions. Previously, textbook items whose 'type' (new/used) were substituted on the Mail/Web order transactions were not reflected in the membership transaction inquiry detail grid. This changes in this ITG correct this so membership transaction inquiry displays the correct details for a mail/web order transaction when the item's type is substituted.

Memberships and Substitutions (681390, v28.1.2)

The request was created to correct a defect in PrismCore Membership Transaction Inquiry when viewing transactions containing type substitutions. Previously, textbook items whose 'type' (new/used) were substituted on the Mail/Web order transactions were not reflected in the membership transaction inquiry detail grid. This changes in this ticket correct this so membership transaction inquiry displays the correct details for a mail/web order transaction when the item's type is substituted.

Deleting Memberships Not Flowing (681408, v28.1.2, v1.8.4.3)

Deleting a membership account from a customer was not flowing to PRISM360. This has been fixed so that if a membership account is deleted from a customer in PrismCore, the deletion flows to PRISM360 and removes the membership account from the customer.

A/R Customer Maintenance - 212

Error on Deletion (695252, v28.2.0)

Prior to the fix, when a user attempted to delete a customer record that had an account attached in the detail in Accounting > Receivables > Customer Maintenance, either on PrismCore Admin or PrismCore, they would receive the following SQL error: The DELETE statement conflicted with the REFERENCE constraint "FK_Acct_Agency_Customer_Customer_Table". The conflict occurred in database "prism", table "dbo.Acct_Agency_Customer", column 'CustomerID'. The statement has been terminated. This has been resolved. When a user attempts to delete a customer record that has an account attached in the detail in Accounting > Receivables > Customer Maintenance, either on PrismCore Admin or PrismCore, they will receive the following error, "Customer in use: Account". The user can left-click <OK> to return to the customer record.

A/R Adjustment Loop (681414, v28.1.0)

When an A/R adjustment was made and saved the 'update or delete failed' error message was displayed and allowed the adjustment to be updated. This issue has been resolved so no message is displayed in this scenario.

Customer Balances (696106, v28.1.)

Prior to the fix, customer account balances were sent to the web & were available for students to charge against prior to the set start date for the account in Customer Maintenance. This has been resolved. Account balances are sent to the web as ".0000" (zero) prior to the start date established in Customer Maintenance.

A/R Account Dialog (TFS491, v28.2.0)

Prior to the fix, when the user left-clicked the ellipsis to select an A/R account from the Find Account dialog, the listing was blank. This affected all modules in PrismCore with an option to select an A/R account (i.e. AR Customer Maintenance and Mail Order.) This has been resolved. When the user left-clicks the ellipsis to select an A/R account from the Find Account dialog, the listing is populated with available A/R accounts.

Information on Security in PrismCore for PA-DSS 3.1

According to password complexity requirements for PCI 3.0:

• Passwords must not contain the user's entire account name value or entire display name value.

• The account name is checked in its entirety only to determine whether it is part of the password. If the account name is less than three characters long, this check is skipped.

• The display name is parsed for delimiters: commas, periods, dashes or hyphens, underscores, spaces, pound signs, and tabs. If any of these delimiters are found, the display name is split and all parsed sections (tokens) are confirmed not to be included in the password. Tokens that are less than three characters in length are ignored, and substrings of the tokens are not checked.

o For example, the name "Erin M. Hagens" is split into three tokens: "Erin," "M," and "Hagens." Because the second token is only one character long, it is ignored. Therefore, this user could not have a password that included either "erin" or "hagens" anywhere in the password.
Passwords must contain characters from three of the following categories:

• Uppercase characters

• Lowercase characters

• Base 10 digits (0 through 9)

• Non-alphanumeric characters: ~!@#$%^&*_-=`|(){}[]:;"'<>,.?/+

There are two areas where PrismCore software and servers interact with this requirement.

Server Component

In order for the PrismCore server to force adherence to complexity requirements, login attempts, expiration times, and other security related features, users must set the server up with password policy requirements. This is done via password policy that controls the servers running SQL. For information on how to set up and control this feature, Microsoft suggests the following:
{+}https://technet.microsoft.com/en-us/library/dn452420(v=ws.11).aspx+
Note: You will need to locate the information specific to the version of the operating system running on your server

PrismCore User / SQL User Component

When a PrismCore user is created, the system automatically creates a corresponding SQL user.
Beginning with PrismCore 27.3.2, all NEW users added to PrismCore are automatically set to "Enforce Password Policy" and "Enforce Password Expiration" in SQL when their PrismCore user is created. This means those users will be set up to adhere to the security policy set up on that server (see Server Component).
For users created prior to PrismCore 27.3.2, if a manager would like their PrismCore users to adhere to the security policy set, they will need to contact IT Support. Support will then enable the SQL users to "Enforce Password Policy" and "Enforce Password Expiration".