Release 12 (Summary)
This topic lists a summary of new features available with release 12 (12.1.15 and higher). Release 12 is a "full" release with many changes. It is being made available to all users in February 2017. These notes provide a summary of the features included with the release. Fixes to issues, due to new development and that were not present in the most recent production release of version 11, have been excluded but may be found in the "BETA" notes section.
Release Notes can show you new features and fixes that are available to your company, some of which you may have requested! To find out if you can use these features, compare this version of Help 26.0 with your application version, which is listed in Help > About. When you install the latest software version, you can use all of the features discussed here, even if your company "skipped" one or more of the previous versions.
You may see references to some changes, particularly fixes, in more than one release. For example, we may fix an issue in our production line (current release) as well as our beta or development lines. For this reason, you may see similar items that are also referenced in other notes.
We use identifiers in these Release Notes to indicate the kind of change they represent. New features and enhancements begin with a "E-" or "B-" for backlog, "R-" for requests, and "D-" for bug fixes (defects). We leave these entries in the Release Notes to make them easier for you to refer to if you have questions.
|
Note: To find what you are looking for on any page, you can use the "Find" function CTRL-F. Later notes for updates (stability) are also provided in separate topic(s) so that users can just view those changes. We provide links in the main "feature" notes to any stability notes topics. |
|
Account Maintenance A new "Compare to Store Retail" check box is provided when a customer's default price level is set to a level other than the "store retail," or level zero (0), price. If the option is checked, and the store retail level price is lower than the customer's level price, it will be used. Certain other pricing, not based on levels, such as contract pricing, can override this behavior. Genius® by TSYS Cayan™ Card Interface TSYS Cayan is a new offering for card processing. It uses the same Verifone MX model devices that many of our users are familiar with, but with a fresh modern interface, and fully supports EMV (chip card) processing, manual entry, and tokenized sales. TSYS Cayan is required for use with the True Value Quick Credit Card Applications feature. Card Processing For all card processing, canceling from the signature would continue to process the transaction. Now a cancel will allow the cashier to decide whether or not to continue processing. The prompt for "card on file" will now only appear after a bankcard amount has been specified in the Process (F12) form and if the user has permission to do tokenized transactions. Please note: this has been changed in release 12.3.7 to happen when the Process (F12) form is initially shown in the Point of Sale, Sales transaction. Item Merge (Point of Sale, Data Grid) This option provides the ability to combine duplicates of the same item together from the data grid in Point of Sale transactions supporting Item Entry. This new utility allows you to combine multiple open order documents together into one single order. Restrictions apply. We have added a new menu marker option that can be used to reverse the quantities in a Sale transaction. This only works for items that allow returns. Suspend/Resume We have made changes to how we retain suspended transactions to better ensure that suspended transactions remain available after release updates. When a transaction is suspended we actually record (save) the entire state of the window's form at that time. Any changes to the form or data, as result of a software update, could therefore "break" the ability to resume from that "snapshot." One common cause of problems is when background data is added to the tables linked with item entry (data grid). If columns were added by a software update that didn't exist before the resume, it would always break the resume. Now, we've modified the code so that it will attempt to assign default values to any columns that didn't exist at the time of the suspend. This gives the suspend a better chance of working; however, it's not completely foolproof. Should we add columns that involve new custom objects rather than standard values (integers, decimals, strings, etc.), the resume could still not work. For this reason, we still suggest that you resume and process transactions prior to software updates; however, if you don't, there's a better chance now of resuming those transactions than in the past. True Value Rewards True Value Rewards and related features... •Quick Credit Card Application •Rewards Enrollment and Lookup •Email Collection at Point of Sale •Substitution/Replacement Item Report For Basecamp XML Import (F2), we now set the unit price of the mapped SO item to the match the "customer extended price" divided by the quantity and unit cost to the "dealer extended price" divided by the quantity (unless the SO item has a cost percentage assigned which overrides this). A command argument of XML2OLD can be used to override this change if necessary either for individual desktop shortcuts or for the entire application. The XML Import (F2) function for BROSCO orders was discounting the "net price" which already considered any discount. Now, it will only discount the "gross price" if no "net price" is set in the data. Administrator users can now select disabled users. When adding a cash-only account from the Process (F12) form, and if one of the account (customer) user-defined keys is "Loyalty ID," add the input field to the form and store it in the proper location of the new account. If a "DoItBest" wholesaler is defined, check the ID for validity (as would be done in account maintenance). For Basecamp XML Import (F2), we now set the unit price of the mapped SO item to the match the "customer extended price" divided by the quantity and unit cost to the "dealer extended price" divided by the quantity (unless the SO item has a cost percentage assigned which overrides this). A command argument of XML2OLD can be used to override this change if necessary either for individual desktop shortcuts or for the entire application. The XML Import (F2) function for BROSCO orders was discounting the "net price" which already considered any discount. Now, it will only discount the "gross price" if no "net price" is set in the data. Price Change - Not Net Task List Message We have changed the situation triggering the task list message, "Item Pricing was changed without marking the item as net." Now, the warning is only triggered if the price change lowered the price of the item. Changes that increase the price will no longer result in the message. Penny rounding, previously only available to Canadian users, has been enabled to allow use by anyone. This is done for cases where companies are located outside of Canada in regions where penny rounding is permitted or required by law. |
|
Vendor EDI PO Update - Barcodes were not updating because of logic to move barcode update out of the transaction. Barcodes are only set when items are added automatically by EDI (meaning the item doesn't already exist and is added using the template item and catalog data). This change does not correct any barcodes that were not updated in the past due to the problem. Signon Installer - Installer changes: installer changes version number in send and receive scripts in EDI and code to prevent newer version scripts from running. Updating a PO with Retail Prices via EDI PO Update: The retail price on the PO was getting reset to the item's retail price if the PO was modified in PO Entry after it was received via EDI. This would cause incorrect pricing to come into price updates if the PO was then copied. Branch Setup, EDI tab: it is now possible to just set the script name in the EDI settings for send and receive (recv) scripts rather than the full path. EDI will run it from the "ediscripts" directory if the send or receive values aren't a valid fully qualified path name. Vendor EDI - Ashley Furniture A new EDI option for Ashley Furniture has been added. Vendor EDI - Emery-Waterhouse Change to support long descriptions in the catalog load routine. Backward compatible to previous version so if the file doesn't contain long descriptions it will still load. A new House-Hasson EDI interface has been added. Changes to Orgill Inventory Load. UM was trying to put a 5-character UM into a 4-character slot. Would get an error when trying to add any measure that was actually 5-characters. Wrote a routine that strips the numbers from the end of an Orgill UM. Orgill has measures such as "CD 5" and "CD 50." Changed routine so that it would check the format of the file before updating to make sure we are loading the correct file. Vendor EDI - True Value Company Fully integrated direct EDI with True Value Company is available with this release. Fix an error in ACE EDI for loading hotsheets with the "cost-only" mapping formats. Removed an error message for ACE EDI displayed when checking that the base path name is a rooted path. This check is no longer needed with SFTP. When importing a Mobile PO, we now default the back-order flag to True and set to the vendor's default value if a vendor has been specified. Corrections were made after an issue with tally items was identified. Prorating the remaining quantity across items was not working properly when the member/child items of the tally had base measures that were not the same as the order quantity unit-of-measure (UM). This has been corrected. |
|
For items where the cost measure (UM) in the data grid is same as the item's pricing UM we are no longer recalculating the cost to set the item's average cost (as it isn't necessary in these cases). The re-calculation could cause rounding issues if the item had conversion factors. Changes have been made to allow the Import (F2) of items from a Manufacturing Work Order that are associated with a customer order for the purpose of printing Special Order labels. There were restrictions against importing material list type items which caused an issue with import. Manufactured items usually are linked to a material list. The Import (F2), Inventory option now allows for import by vendor code. Matching is done on each item's primary vendor. New designer fields for WMS Location Barcodes and WMS Unified Barcodes were added. These allow for the printing of a single location barcode on an item or single unified barcode for an item. Previously, labels would be printed for each of the item's locations. Those options are still available; however, they are not available for use with DYMO printers. These new options are available for both Zebra and DYMO brand supported label printers. The font size on DYMO tags wasn't being set properly once the label height was sized greater than 28 pixels. The font size wasn't being set to 16pt (point). Additional checks are now done to ensure that the Image List form is not being closed due to scaling before final save of current screen in the form closing event. When the Image Lists form loads at time of sign-on, it now does a count only to speed login over remote connections. An error on the data grid has been fixed. Set a shortcut on the menu to "A" for keyboard navigation. This utility provides data exchange with IME, "Intelligent Margin Enhancement," a service/product of Group CBF, Inc. 7-Zip, an open source (free) file archiving software product, is required for this utility. This is available from http://www.7-zip.org/. To access this utility, "IME Pricing" must be enabled by support and branch settings for your store number, access key, and secret key must be completed. This tool is commonly used by True Value members. This new utility is provided for use with catalog vendors. It's purpose is to provide an easy way of comparing the vendor's catalog with your inventory items to identify differences between the two (2). Selection involves choosing an EDI enabled Vendor and then selecting the field or fields you want to compare. Merge/Rename Items (Merge Discontinued) A new folder tab for merging discontinued items has been added. This is specifically for True Value members and only allows selection of vendors assigned to a wholesaler name of TRUEVALUE or TRUESERV. Items that have been discontinued by True Value Company and have substitution items designated will be listed for selection. |
|
We have added the ability to define a list (group) of adjustment codes and then link that list with a manufactured item. This allows more than one adjustment to be linked with any given manufactured item. When linked to a special order manufactured item, the adjustment(s) are applied at Point of Sale when creating an Order or Quote for the item. Do not allow an adjustment code that is being used on a Manufacturing Adjustment List to be disabled. Adjustment Code - Setup Charge A new method for manufacturing adjustments of "Setup Charge" has been added. When applied, the amount designated is multiplied times the quantity of the manufactured item. Special Order Labels (Tags & Labels) for Work Orders Changes have been made to allow the Import (F2) of items from a Manufacturing Work Order that are associated with a customer order for the purpose of printing Special Order labels. There were restrictions against importing material list type items which caused an issue with import. Manufactured items usually are linked to a material list. When adding adjustments from both the manufacturing process and the adjustment list, remove duplicates (overwrite process values with selected adjustment list values) Code was moved to prevent an issue when updating Work Orders in the scheduling queue. Due to the order of code events, it was possible for a reserved document to no longer exist causing phantom queue records to be inserted in the schedule. This has been corrected. |
|
This new parameter for Receivables uses the "net due" (balance less open credits) for certain types of statement processing. When enabled, this changes the ending balance printed on balance forward statements to the "net due" and also how certain messages are triggered such as "no payment due" and "credit balance," for example. In a future release, it will also determine whether calculations for finance charges consider open (unapplied) credits or not. These statement changes are partially implemented and should not yet be used (as of release 12.3.7). When printing statements, this parameter will combine the statement and invoices into a single print file to ensure that invoice reprints and statement documents stay together (print spooling can sometimes print jobs in a different order). This is currently being tested and is not yet available (as of release 12.3.7). The parameter will not currently affect statement processing and should be left off. For companies with the "statements print open credits," option enabled and the "1-up" invoice reprint option, invoice reprints were not being produced during statement processing. This has been corrected. |
|
AP Checks Display printer errors (if any) when printing vouchers. Fix an index error that could happen if the vendor code was less than 4-characters long (checking for MISC vendor). |
|
This feature is provided for new installations or companies who have never used the ledger actively. Companies who have posted ledger entries (journals) are not eligible. Non-standard GL allows a company to define either 12 or 13 cycle periods plus an additional adjustment cycle (for a total of 13 or 14 cycles). The starting dates for each cycle can vary and names can be customized. The reason for offering this feature is that monthly cycles vary in length and number of business days. Allowing a company to set its own dates provides the ability to create cycle periods that are more equal in nature. We have expanded the restrictions on disabling a GL account to include any case of mapping set for the owner account. If the owner account (title) has any departmental equivalent mapped, we won't allow the account to be disabled (one exception is the specific mapping for a check register). Account Mapping When returning an account with a branch offset, use the original account if the selected account is disabled. The "MTD Change" version wasn't considering the filter for excluding zero balance accounts. This has been corrected. Income Statement - Combo Budget totals and % of budget were not being displayed when running the "combo" version. The "% Sale" figures shown for the Cost of Sales section was not correct when multiple departments were selected and the option to create a separate report for each department was also chosen. These issues have been corrected. |
|
Inquiry New function in delivery inquiry to be able to view unassigned documents. |
|
A change was made to how the Folders attachment function works when interpreting document identifiers using the file names of the files in the source (scan output) folder. To properly match attached images with existing documents, the code now will trim off any characters appended to the file name in addition to the document. For example, if the file's name is "1609-C12345_0001.PDF," we will only use the document port (the first 11-characters) for comparison. Some scanning software requires at least one character in addition to the barcode. We have added a task list error that will appear if the user is marked as disabled, but is assigned to any accounts or jobs. |
|
Graphical User Interface Redesign The Spruce application design has been redone to have a more modern appearance. This redesign includes changes to the color scheme, icons, asset logos, and minor changes to control functionality. DPI Changes for 4k Monitors We have made changes to the application to support newer high resolution (4k) monitors. This required redesigning most controls to be able to handle the added resolution. New application security codes have been added for card transactions using integrated card interfaces. These allow restriction of manual card entry (on the device), card not present, and tokenization. Application of security will vary based on the card processing solution being used. Sign-on Errors A few companies received a message during sign-on: "Signon Error. Specified Item Index is not in the ItemSet (idx=-1/count=2)." The error was caused by code querying the current active sessions for the user to locate the oldest session. Due to a timing problem caused by slower connections, the oldest active session could not be determined (because the last access time had been updated to a future time). Instead of an error message, a new message is now displayed to notify a user that the oldest active session could not be determined, and that the user needs to log-off one of their sessions in order to sign-on again. Since this issue does not occur for all customers, the new message will only be displayed if the customer has been assigned a debug option SESSIDLETIME. Please contact support if you have encountered this issue. Capital One Trade Credit (formerly BlueTarp) Inquiry We have added an additional check on data returned from a Capital One Trade Credit (formerly BlueTarp) credit inquiry to prevent cases where a Capital One Trade Credit (formerly BlueTarp) account was "active" during the morning download, but subsequently suspended by Capital One Trade Credit (formerly BlueTarp) later on the same date. Added a secondary on-line Help provider for use in cases where the first provider isn't available or is unreachable. If neither provider can be reached, we now display an HTML document with contact information, etc. rather than a "page not found" or other type of error message. |
|
Many improvements and fixes have been made to this report during BETA development. Please view the Daily Sales Report documentation for a full explanation of current functionality. |