12.10.6 - 12.10.22 Summary Release Notes (November 2017)
Release Notes and Help topics can refer to changes, features, and fixes that your company may not yet have installed. Use Help and About to check your application version for comparison to the Help version. The current Help version is 12.15.35. When an update is installed, all changes up to that version are included even if your company "skipped" one or more prior updates.
It is possible for some changes, particularly fixes, to overlap more than one release. For example, an issue may be fixed independently 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.
Identifiers are now included with most items in the notes. These are used by our project tracking software, or source control, and are sometimes linked to support tickets. Identifiers prefixed with the letter "R" are requests, "D" are defects (fixes), and "B" or "E" stands for backlog items (enhancements or new development usually).
Note: To find individual release changes on this 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. |
Automated Upgrade - Notice On-premise customers who use automatic upgrades should be aware that we have decided to incrementally roll-out software updates with release 12.10.11 and later. This means that even if your company normally installs the latest update right away (no delay days), there now may be a delay of several days before you receive the release. Each day after release, we will incrementally increase the number of downloads permitted. Why are we doing this? There are a number of reasons. One concern is the large number of on-premise customers who upgrade immediately after release. Secondly, we used to reserve large feature and enhancements for a yearly major update; however, updates throughout the year can now contain significant changes. Just to be safe, we want to minimize the impact of any possible issues that might arise after release. |
Stability Updates since Release 12.10.6
Release 12.10.6 was the first 12.10.x version distributed to customers and serves as the base for the notes. All changes are listed below listed by application area and ordered alphabetically by title; however, for a listing of all changes in a particular stability update, click the link(s) below or visit the following sub-topics below this summary in the Help's table of contents.
12.10.23 (February 2018)
12.10.22 (February 2018)
12.10.20 (January 2018)
12.10.19 (January 2018)
12.10.12 (December 2017)
12.10.11 (December 2017)
12.10.9 (December 2017 - BETA Only)
Summary Notes (All Changes for 12.10.x):
Sections below are organized by application area or category and can be expanded by clicking each heading link or expand all hidden topics using the button found in the Help's header topic header panel. The following video provides a summary of some of the features found in this release:
Changes were made to update existing "add-on" SKUs after quantity changes are made to the originating item in the data grid (the item with an add-on SKU). Canada, Exempt Sales Tax WarningWhen a customer is assigned to a zero (0%) rate PST/HST tax and no tax exempt ID has been indicated from the Process (F12) form (in a Sale transaction), we now provide a task list warning to the user (cashier). The message is "PST/HST Tax Exempt Number not entered." This change only applies to Canada. D-38053 B-43772 - TSYS Cayan - ACE Gift Card ActivationWith TSYS Cayan, the "99" (or "990") prefix was not being done automatically for ACE Gift Card activations. This has been corrected, so the gift card activation amount will now be prefixed with "99" for amounts under the maximum $250 dollar amount and "990" for amounts below $10 ($5 is the minimum). Please note: the activation amount displayed on the pad will differ from the amount the customer is charged. For example, if the customer is purchasing a $25 gift card, the activation amount will be "$9925" not $25. This is due to the way ACE chose to implement their card program. Instead of doing a gift card activation, it's processed as a SALE and will usually receive a DECLINE response from the processor (which indicates a successful activation). The first time you activate a card, it's best to contact ACE to verify that the card was truly activated. ACE Gift Card activation requires use of an item assigned to the "ACEGiftCard" item type and has other requirements. You typically need to provide merchant information to ACE Hardware Corporation before you can activate cards. (12.10.11) B-43772 TFS-150610-P D-41982 - TSYS Cayan Bankcard ReceiptsTSYS Cayan card receipt document data was being saved in a raw data format. For future receipt data, we now format the data in a readable form so that they can be more easily viewed from the Documents form Viewer. We must keep receipt data for certain bankcard transactions. (12.10.19) D-41982 TFS-151689-P D-41319 - TSYS Cayan - Signature for Receivables Charge TimeoutThe time-out period for collecting a customer signature for an on-demand signature (such as for a receivables charge) when using TSYS Cayan configured devices has been changed to four (4) minutes. The time-out parameter had been removed in release 12.10.x leaving the default setting as the value which was too short for many signatures. (12.10.9) D-41319 TFS-149898 (BETA) R-47318 - Point of Sale / Installed - Canada Real Property TaxOn hand quantities were being doubled on returns linked to installed sales when real property tax was indicated. This was due to an unintended consequence to correcting "R-42416 - PST real property tax not calculated properly" issue. For real property, PST tax is paid on the materials by the merchant. While the tax was being correctly calculated on the material cost on the ticket, the cost on the ticket did not necessarily reflect the current weighted average of the items. Returns with real property wound up calling the routine to adjust on-hand twice, once from PSTicketsData and once from BusinessLogicCloseout. This has been corrected. (12.10.19) R-47318 TFS-152230 D-42393 - Point of Sale / Installed - Material CostsThe Actual Material Costs were being calculated and displayed incorrectly on the form (and subsequently saved in the installed contract header record). (12.10.20) D-42393 TFS-152848-P B-45474 - Point of Sale / Item Returns - Set Net flag based on Original SaleWhen returning an item and specifying an original invoice, and if the originally sold item was marked as "net" (N) as the discount code, we now set the return item to be "net" as well. Previously, the returned item's current discount code was being used. This works with both "enhanced" (Stocked Return Info) and non-enhanced returns. (12.10.23) TFS-153398 D-42399 - Point of Sale / Open Tickets - Use TaxUse Tax Code Totals were not being updated correctly for Tickets linked to installed sales when invoiced. This has been corrected. Tax totals are not updated until invoicing. Tickets associated with installed sales contracts are invoiced automatically when the contract is closed; however, they can also be manually invoiced. (12.10.19) D-42399 TFS-152521-P D-42700 - Point of Sale / Open Tickets - Dispatch StyleA dispatch style invoice document is only printed in cases where the "Invoice Now" check box had been checked; however, when not invoicing, a different "pick ticket" ticket style is used. This style was not displaying the weight total. This has been corrected. (12.10.23) TFS-153574. D-42750 - Point of Sale / Reports / Management / Sales AnalysisDates with a year prior to 2010 were causing a malformed date exception. The error has been corrected. (12.10.23) D-41721 - Point of Sale / Sales / Multi-page Invoice Tax Panel displays PlaceholderThis issue was identified during the BETA test period and was not distributed to production (all) customers. On a multi-page invoice, pages except for the last page were printing a long numeric place holder ("1234567890123456790") where the tax information would normally print on the last page. The placeholder has subsequently been removed so that it no longer displays or prints on the invoice document. D-41721 (12.10.12) TFS-150955-R TFS-150968-P D-40208 - Cash Drawer Tally - PrintChanged the Cash Drawer Tally to use the new Print > File method when using the Remote Client. Now using new print image method of the Remote Client. (12.10.19) D-40208 TFS-151394-P Close Cash Drawer Utility - Tally FeatureIf used, any tally amounts for cash, check, bankcard, coupon, and gift card are now saved with the cash drawer session records. New fields were added to the table and data object changes have been made. B-42281 Contract pricing can now be done using customer class selection as well as customer account. This allows contract pricing for groups of customers you categorize using the "class" option. New radio buttons for "account/job" and "class" have been added to the form. Contract pricing for an account/job contract will override the "class" contract if both exist. D-41335 - Customer Order/Quote Selection ControlAn error would be generated by clicking on the column header cell in the selection listing of quotes or orders. Error was caused by code used to re-size the columns after a sort. Code was always using the length of the first item in the listing after the "NEW" selection; however, in the case of an exact match, the "NEW" selection didn't exist nor did any additional items in the list. Now, if there are no additional records, as is the case with an exact match, the zero (0) index is used for the re-size caused by the sort action. (12.10.9) D-41335 TFS-149893 R-47762 - Point of Sale / Order-Quote Selection Sorting by UserWe now allow sorting the selection list for Orders-Quotes by user. (12.10.19) R-47762 TFS-152524-P Corrections to for the recently added sort by order user id. Second field in order changed from to DocIDInternal for both ascending and descending user id sort. (12.10.19) R-47762 TFS-152526-P Installed Sales, Billing Tab The billing tab of the Installed Sales transaction has been redesigned. Text areas provided for installment (progress) billing have been replaced with a data grid. The benefit being that the grid permits additional payment instances. Currently, the number of items that can display on the contract document is limited to a maximum of fifteen (15) plus one final billing; however, the next stability update (12.10.7) will have a change that allows the document to have additional levels. Open Tickets associated with Installed Sales for the Installed Sale "CASH" account can now be ticketed and invoiced prior to completion of the contract. The capability to invoice installed sales tickets prior to the completion of the contract was added with release 12.9.x and has been extended to "cash" contracts. D-40980 - Installed Sale - Contract DocumentLimitations on the original Installed Sale contract document were addressed to permit the printing of additional pages when progress payments exceed the number that can be printed on a single page. With the initial release 12.10.x, the number of payment plan levels is no longer limited, so the document had to be adjusted to accommodate this new capability. (12.10.9) D-40980 TFS-149143 (BETA) D-41683 - Installed Sales - Contract VoidWhen voiding an Installed Sale Contract, we now mark the contract as "complete." (12.10.19) D-41683 TFS-150938 D-41877 - Point of Sale / Installed Sales / Use TaxInstalled sales contracts were not recording the "use" tax totals with the Installed Sale contract (header), so the Installed Sales report which referenced the "use" tax was not displaying totals for the amount. The contract is now being updated with these amounts so that the Installed Sales report can properly report them. (12.10.19) D-41877 TFS-152680-P D-41770 - Invoice POS Assured UtilityUpdated the Point of Sale, Utilities menu to only show Invoice POS Assured Sales when POS Assured is enabled in Parameters. (12.10.19) D-41770 TFS-151528-P D-41953 - Point of Sale - Footage Document Styles (Orders & Invoices)Logic for calculating square footage measures were missing references to the item's Pricing UM. Board footage calculations did not have the same issue. This would only manifest for "Sheet Goods" type items where the only valid square footage measure was the Pricing measure (and none of the others were). (12.10.19) D-41953 TFS-151547-P B-42304 - Point of Sale - Open Tickets (Advice Notes - UK)The Open Tickets transaction in Point of Sale now allows cash-only accounts. Tickets relieve inventory in advance of payment processing. This ability can be useful in a number of different situations (delivery, drive thru, etc.). To invoice the ticket, select the existing ticket then choose Invoice Ticket (F8) function from the Open Tickets transaction. The transaction will switch to a Sales transaction to permit payment processing for the cash-only customer. B-42299 Additionally, a change was made to retain the cash-only customer's account information when switching to a "ticket" transaction from another transaction type (order, etc.). B-42304 B-43251 - Point of Sale - Open TicketsWe have added a new warning message to notify the user when processing an Open Ticket and using either a cash-only or system type account. (12.10.9) B-43251 TFS-149521 D-39999 - Point of Sale / Orders / Dispatch Copy - Weight Decimal DisplayWe are now displaying the weight out to two (2) decimal places on the Dispatch Copy of customer order documents to be consistent with the other weight displays on order document styles. (12.10.19) D-39999 TFS-151895-P D-42185 - Point of Sale / Orders - Quotes Document Selection - Sorting by DateAn exception would occur if users sorted the selection listing of quotes or orders in reverse order by date and then clicked the "more" option. This has been corrected. (12.10.19) D-42185 TFS-152130 D-41990 - Point of Sale / Orders - Quotes Document SelectionCode was changed to skip the column header adjustment when the only record in selection list is the "<< New >>" selection. Error could occur if a user entered a non-existent quote document ID and then clicked the down arrow followed by clicking column header for job name. (12.10.19) D-41990 TFS-151680-P Point of Sale / Payouts - Refund Acct Balance (Credit Balance) A new feature has been added to the Payouts transaction in Point of Sale to help make processing refunds of credit balances easier. Only accounts with a credit balance can be selected and there is no capability to partially refund a credit balance, so if used, the entire balance must be refunded. Users must select a "Debit GL" account to complete processing. The selections provided are the same as those mapped for "Debit Adjustments" (receivables). Credit balances can be refunded as either "cash" or "backroom check." Backroom checks generate a payable invoices similar to the function provided in the Sales transaction (for later processing by issuing a check via payables). D-42150 - Point of Sale / Payouts / Refund Acct Balance by Refund CheckThe Refund Acct Balance option in Point of Sale / Payouts was using the Payables Accrual account improperly if the user choose "Refund Check." Now, the debit adjustment (AR) and billing invoice (AP) will use the "refund checks" account mapped to sequence #28 in the Point of Sale system journal mapping. The offset selection is not used for "backroom check" refunds, only cash-type refunds. The selection control is hidden when the user selects "backroom check." (12.10.19) D-42150 TFS-152040-P An additional change was made to more clearly indicate that the "debit" account selection is not used when choosing the "backroom check" option from the Payouts, Refund Acct Balance option. The debit account selection control has been moved below the radio buttons and is now disabled to show a message that the selection is "not available." (12.10.19) D-42150 TFS-152102-P
D-41942 - Point of Sale / Reports / Management / Credit ManagementThe Credit Management report, when scheduled, was not setting the date range based the menu marker date preset selection. This has been corrected. (12.10.19) D-41942 TFS-151597-P B-36572 - Puerto Rico Sales Tax ReportingWe have added support for Puerto Rico tax reporting. When a sale is processed, the tax paid is transmitted to a web service for reporting purposes. Pending changes are being tested for printing this information on receipts as well as updates to the invoicing utilities corresponding with this change. These changes, once tested, will be included in an upcoming stability release. B-36572 B-42569 - Sales, Cursor FocusA change was made to improve cursor focus in the Sales transaction for Remote Desktop Services users. B-42569 D-40378 - Sales - Alternate SKU and ACE RewardsThe application uses timers for certain operations including the alternate SKU update and ACE Rewards dialog. There were cases where these could error when closing the application form at certain points. We have added code to avoid the situations causing the exceptions. D-40378 Reprice Material ListsThe "reprice" function has been updated to handle the repricing of material lists. Returns referencing an Original Invoice with AdjustmentsCode was changed that deals when applying adjustments from an original invoice when repricing items to match the original sale. Adjustments were always setting the adjustment's "discount" flag to false to treat them as "adders" to calculate the original price but should have been setting the value to the opposite value of the original sale adjustment instead. This ensures that discounts are applied instead as an "adder" to set the original price and adjustments that originally were applied as adders are instead applied like a "discount." This helps better duplicate the original sale situation for the reversal pricing. D-41799 - Totals ReportCost corrections total from same period last year were being added into cost corrections for current period in error. This only happens when the month option is being used for selection (MM/YY). Date range can be used as a work around until this fix is applied. (12.10.19) D-41799 TFS-151138-P D-41504 - Verifone Point - ACE Gift Card ActivationWith Verifone Point, the "99" (or "990") prefix was not being done automatically for ACE Gift Card activations. This has been corrected, so the gift card activation amount will now be prefixed with "99" for amounts under the maximum $250 dollar amount and "990" for amounts below $10 ($5 is the minimum). Please note: the activation amount displayed on the pad will differ from the amount the customer is charged. For example, if the customer is purchasing a $25 gift card, the activation amount will be "$9925" not $25. This is due to the way ACE chose to implement their card program. Instead of doing a gift card activation, it's processed as a SALE and will usually receive a DECLINE response from the processor (which indicates a successful activation). The first time you activate a card, it's best to contact ACE to verify that the card was truly activated. ACE Gift Card activation requires use of an item assigned to the "ACEGiftCard" item type and has other requirements. You typically need to provide merchant information to ACE Hardware Corporation before you can activate cards. (12.10.11) D-41504 TFS-150610-P D-41970 - Verifone Point - ReconcileIn some cases, the approved amount shown wasn't exactly matching the transaction amount and could be off by a penny (.01). EMV approved amount off by a penny from actual Approved Amount. This change will simply display the actual approved amount instead of the EMV_9F02 element. SPDebugOpt argument to switch back to original code of EMV9F02. (12.10.19) D-41970 TFS-151642-P D-41934 - Point of Sale / Utility / Order MergePrevious correction would only work if there was only one (1) job on the account. Multiple jobs would cause an error where the address fields on the new merged order would be blank. Corrected. (12.10.22) D-42427 - Point of Sale / Reports / Invoices & TicketsQuantity was not being included in the summarized details. (12.10.22) D-42451 and D-42356 - Point of Sale / Random Length Tally ReturnsWhen returning a random length tally (either a partial quantity return or full quantity return), the quantity in the grid reverts to the quantity on the original invoice. For example, if 200 were sold on the original invoice and then 60 were returned (by entering -60 were on the random tally form), after the user selected the original invoice on the item return form, the quantity in the grid reverted to +200. (12.10.22) D-42453 - Point of Sale / Utilities / Item ReturnsWhen Special Order goods were marked for resale from the utility and the user sets a new unit price, the code was setting only the suggested list price but not any of the item's price levels. Prices levels are now updated as well. (12.10.22) |
A defect was corrected where the vendor-item's designated unit cost wasn't always being updated appropriately when changes to the order quantity were made. Vendor items can have up-to three (3) multiple levels each with their own cost. D-37686 D-39927 - Purchasing, Order Entry - Import (F2), InventoryWhen using the new Import (F2), Inventory feature in Purchasing, Order Entry prior to selecting a vendor, and unhandled exception (error) would occur. (12.10.9) D-39927 TFS-149287 (BETA) An additional change was made so that the vendor control will only be selected rather than showing the drop down listing. (12.10.9) D-39927 TFS-149288 (BETA) D-41215 - Purchasing / Order Entry / Build (F7) - Replenishment Build Memory IssueChanges were made causing the full Inventory to be queried prior to evaluating for build inclusion. Since the replenishment is date based on sales, we added some restrictions on the initial pull of items for inclusion to limit them to items sold on or since the start date selected by the user. This eliminates any items that were never sold or were sold prior to the start date selected by the user processing the build. This is appropriate in this case because replenishment builds are always based on net sold for the period. (12.10.20) D-41215 TFS-152840-P D-39308 - Vendor EDI - EmeryChanges were made to the Catalog Load operation to consider the new field for Ordering UM (unit of measure) now included in the file and to populate the catalog accordingly. We will change the vendor Ordering UM to PACK if the Vendor UM matches the ALT/Retail UM and a conversion factor exists. (12.10.9) D-39308 TFS-148893; TFS-148972;TFS-149041 D-42120 - Purchasing / Vendor EDI / Orgill - File Maintenance - Manufacturer's NumberThe manufacturers code (model number) for the Orgill catalog was only allowing 7-characters, so some model numbers were being truncated. We have expanded the length of the field to allow up to 16-characters. (12.10.19) D-42120 TFS-152006-P B-44689 - Vendor EDI - Orgill - Mapping Overrides - Purchase Order SendThere are two (2) new mapping overrides for Purchase Order submission with Orgill, Inc.: PO Send w/Retail and PO Send w/Price0. In either case, an additional DT2 record is created in the data for each item ordered. This record includes either the suggested list or store retail (level 0 price) for the item. The price is found in positions 4-12 of the DT2 record. The format can be manually selected from the Transmit, EDI tab of the Process (F12) form when processing a Purchase Order. To permanently use the override for ALL orders, select the desired override from the Mapping Overrides form for the Orgill EDI vendor from the Branch Setup form's EDI tab (Main Menu > Maintenance > Database > Branches). ![]() Orgill PO Data with Price If the override is set as the default, users won't have to select it from the Purchasing, Order Entry transaction. Even though the Transmit, EDI tab will still list "regular order" as the selection, the override will be used when creating purchase order data. (12.10.19) B-44689 TFS-152006-P D-39921 - Vendor Quote - Email AttachmentVendor Quote documents were Emailing with a PDF file name of "-1.PDF" instead of using the document number of the quote. This has been corrected. (12.10.19) D-39921 TFS-150805-P |
Changes were made to ensure that the original receipt adjustments (adders, etc.) are not changed when a receipt is reversed. After reversal, the original adjustments are now retained in their original state on the document.
D-42126 - Inventory / Inquiry / Tracking - Cash Invoiced TicketsThe Tracking inquiry was including Open Tickets (aka. Advice Notes) where the ticket had been invoiced for a system or cash-only using the new "Invoice Ticket" (F8) function. In these cases, the ticket is not converted to a regular invoice. Instead, a new "cash" sale invoice is generated and the original ticket is no longer updated. The Tracking inquiry has been changed to only include "open" tickets to avoid issues with the on-hand calculation for tracking history. (12.10.19) D-42126 TFS-151989-P D-41835 - Inventory, Adjustments, Qty AdjustmentThere are three (3) distinct options available when the Qty Adjustment (radio button) is selected: Item, Transfer out, and Work Order. We no longer allow a mix of regular item adjustments along with Transfer Out and Work Order reversal. Each option is now isolated. Once any of the three (3) options is selected, the remaining two (2) are now hidden until processing is completed or the user cancels the transaction. Additionally, the Transfer Out option prevents user changes to the items being reversed. (12.10.19) D-41835 TFS-151388-P D-42570 - Inventory / Tags & Labels - DYMO Special Order LabelsThe design element "Description5" (which prints up to 5-lines of 32-characters each for the item description) would error on very long descriptions causing the label to print "lblDescription5" instead of the item description text. Changes were made to check the overall length when parsing the description into segments and exit once the maximum length is met. This issue was particularly noticeable with SO manufactured items which tend to have longer descriptions. (12.10.23) D-39725 - Inventory, Transfers When printing and also Emailing a transfer out document, an additional copy was being printed to the user's default Windows printer. D-39725 B-43486 - Inventory, Transfers Pending - Unit TallyWe have added the ability to request specific units from another branch. (12.10.9) B-43486 TFS-149954 D-39397 - Item Returns UtilityThe item return utility was not handling "return to stock" correctly when the vendor return originated in inventory adjustment due to a code error. If more than one adjustment document existed for the item in question, the quantity adjustment was being applied incorrectly. (12.10.19) D-39397 TFS-151186-P |
D-42124 - Manufacturing / Work Orders / Build (F5) - Adjustments on Stocked Manufactured Items Adjustment code lists for stocked manufactured items associated with a customer order were not be associated with the Work Order when using the Build (F5) function. This has been corrected. (12.10.19) D-42124 TFS-152027-P R-46553 - Manufacturing, Work Orders A change was made to no longer update the quantity ordered on the linked order detail when removing an order reference from a work order. (12.10.9) R-46553 TFS-149671 (BETA) |
The label for the "POS Branch" selection was missing on the "Codes" folder tab. The label is now visible. This did not prevent the selection or display of a POS Branch, the text label was being hidden. D-39755 Restrictions have been placed on the Close Cycle form regarding changing the billing schedule. Only support can modify the scheduled time on pre-production (non-production) system types. The month-end (EOM) billing process must run during a time frame considering the EOD process and between business days. In the past, processing times have changed causing issues with the billing process. The date can be modified as long as other conditions are met. Additionally, new schedule date options have been added for the first day of the month, last day of the month, and selected day of the month. Additional checks against the live date parameter have been added. B-45653 - Receivables / Close Cycle - Scheduling TimeChanges were made to allow the run time to be set to other than the default time of 12:30 AM. Additional range of times allowed are 6:00 AM - 9:00 PM are now permitted. (12.10.22) TFS-153039 & TFS-153037 - Receivables / Close CycleMessage #2069 updated to "First Close Billing Cycle schedule date is within 20 days from the live date. Do you want to continue?" Also, removed check for five (5) days within the live date. (12.10.22) D-42227 - Job Maintenance - Job SelectionWe have made corrections to address a sequence where the user enters in a very high project number that does not exist. This would produce a selection list with only a "<<New>>" option. If the user then clicked the job name column header to sort the empty list, an exception would occur. (12.10.19) D-42227 TFS-152240-P D-42731 - Documents / AR Posting Session ReportWhen printing an AR posting session report with a second copy, the second page would print with the same document ID and account, but with the totals for "Credit on File" and "Discounts Applied" doubled. The document ID would match and both documents would list a page number of one (1). This has been corrected. (12.10.23) B-41209 - StatementsMulti-tray support has been implemented for "single file" statements with invoice reprints. The "single file" feature combines the statement pages with the invoices into one single file that's sent to the printer driver to better ensure that the statement and invoice pages are printed together. After this change, we include the tray selection for reprints from the Statements delivery form and include that in the print file so that the printer can print the invoices and statements from different trays. This means that regardless of your statement settings (single file or separate file) and reprint scaling for invoices (full page, 2-up, or 4-up), different trays may now be used. B-41209 When using the "Statements Show Open Credits" parameter with job-billed open item accounts, there were cases where the totals listed (such as "total," "credits," "pay by" and "if paid by") weren't being shown on all the statement pages (summary, remit, and statement) consistently. There are cases where certain totals, such as "if paid by," aren't shown (such as when there's no discount). AT-142531 B-43552 - Statements - Discount TotalsIn certain cases, both the "pay by" and "if paid by" totals on statements could be printed even if there was no discount amount. In these cases, we only want to print the "pay by" total and suppress the "if paid by" discount total. This issue would only occur if the Receivables Parameter "Statements Show Open Credits" was enabled (Y). (12.10.9) B-43552 TFS-149989 D-41011 - Statements - Emailed from DocumentsChanges were made to ensure that statement documents can be emailed or saved (output) to a file from the Documents form and when done, be listed in the Print, Email, & Fax Queue. (12.10.9) D-41011 TFS-149295 (BETA) D-41087 - Statements - Invoice ReprintsA change was made to prevent against invoices reprint processing when the reprint page count is determined to be zero. Another change was made to correct an issue preventing the Email and output to file processing of statements from the Documents form. This would only happen when the "single file" parameter was enabled (checked). This did not cause issues with statement delivery from the Receivables, Statements form. (12.10.9) D-41087 TFS-149310 (BETA) D-40767 - Statements - Reprint ProcessingWhen invoice reprints is not selected (checked) on the Statement Delivery form, Email statement delivery is selected, and a customer's account is set to reprint invoices, invoices would be prepared for Email delivery, but would also get printed due to the use of the "single file" receivables parameter. Now, after code changes, invoices will only be printed if indicated by the user in the Statement Delivery form (even if they are generated for Email or Fax delivery for the account). (12.10.9) D-40767 TFS-149053 (BETA) R-45753 - Receivables, Reports, Trial Balance Report (Statement Date)Added the statement date to the Receivables (AR), Trial Balance report for clarification on the period being reported. Depending upon when a company does billing, the "current" and "previous" month selections may be interpreted differently. In a previous update, we had altered how "current" and "previous" month were interpreted by code because there were cases where no data would be returned. "Current Month" now means the most recent billing period and "previous" means the cycle before the most recent. By adding the statement date to the report, this provides further clarification for the period being reported. The figures on the Trial Balance report come from the statement documents themselves. (12.10.9) R-45753 149294 |
B-43603 - Payables, Disbursements - UK Check FormatNarrowed the check document so it would not print an extra blank page in UK (United Kingdom) when using A4 printer settings. (12.10.9) B-43603 TFS-150126 D-41700 - Payables / Disbursements - Printing Checks via Remote Client ServiceThe printing of disbursements may involve a single printer with multiple trays where one tray holds pre-printed check forms and the another plain or colored paper for additional voucher pages when needed. There was an issue when printing the checks and vouchers through the Remote Client Service. Additional page settings are now being passed to correct the issue. (12.10.19) D-41700 TFS-152108-P D-40945 - Payables - Miscellaneous POS RefundsFor non-standard General Ledger users, a change was made to ensure that the correct ledger period is displayed in Payables, Billing Entry after a back office check refund is issued from the Sales transaction. (12.10.9) D-40945 TFS-148892 D-42318 - Payables / Reports / Open ReceiptsFormatting for dollar values was added to the total's row of the report. (12.10.20) D-42318 TFS-152835-P |
B-43570 - General Ledger, Journal EntryRestrictions have been added for modification of automated journal entries. The entries associated with the journals are linked to transaction records. The modification or deletion of these entries can cause issues with standard and custom reporting as well as links between documents. Please use additional entries or manual journals for any changes you may feel are necessary to the system generated journal entries. (12.10.6) B-43570 TFS-145653-B Prior change inadvertently prevented new additions (rows) to a system generated journal. Code has been modified to permit this while still preventing changes to the system generated entries. Additional change to consider possibility of NULL values and change to how we determine an automated entry vs. an added entry. (12.10.11) B-43570 TFS-150672-P D-40949 - General Ledger, Close Cycle - Non-standardAn error in the calculation of the current non-standard ledger cycle would prevent the closing of the most recent completed ledger cycle (prior month). Non-standard ledger provides the capability to define the start and end of each cycle as well as offering the ability to have more than the standard thirteen (13) cycles for the fiscal year. This option is only available to companies who are new and/or aren't already using the standard ledger option. (12.10.9) D-40949 TFS-149053 (BETA) D-46767 - General Ledger / Reports / Journal ReportThe checked state on the menu item indicating a "preset" date selection was not being set. This has been corrected so that the date "presets" (quick menu) can be used for date range selection. (12.10.19) D-46767 TFS-151772-P D-41984 - General Ledger / Reports / Journal ReportThe scheduled report was not processing using the selected dates preset (using the menu marker). (12.10.19) D-41984 TFS-151664-P TFS-150741 - EOD - Inventory Journal ErrorCorrection made to the stored procedure named EOD_GL_Inventory. This procedure is responsible for creating ledger entries for the automated "system" journal named "Inventory." The "surplus" account (index 4) was being referenced instead of the "accrual" account in cases where the "surplus" mapping had never been completed. The default in this case should be accrual (index 3). This caused issues for certain types of inventory activity when generating ledger entries for EOD. This issue was introduced with release 12.10.6, identified during BETA testing, and was not present in the 12.9.x production versions so most customers were not affected. (12.10.11) TFS-150741. |
Changes to the billing cycle (EOM) and End-of-Day (EOD) times are no longer permitted except by support personnel on "pre-production" systems. D-39796 - Branch SetupAfter making changes to a branch record, and choosing Process (F12), there were cases where the "Database Updated" message would not be shown even though the form settings would actually be saved. The issue was caused by an error authenticating the Spruce ProLink instance where if the authentication failed, a background exception was causing an issue displaying the message. D-39796 B-42134 - Devices, Stations - Cash Drawer MaintenanceSupport for the "disable alarm" option has been included for cash drawers being used along with the remote client / RDP add-in feature. B-42134 B-42809 - Maintenance / Database / Parameters - Receivables - Invoice Reprint Type for StatementsThe "Invoice Reprint Type" selection will now be used for "single file" statements as well as the standard separate file option. Single file combines the invoices and statement pages in one print job per customer. There is no longer a need to manually update these parameters for "single file" directly in the database by support. (12.10.19) B-42809 TFS-152534-P D-42512 - Maintenance / Database / Devices - Remote Client - DeactivateThe call to the deauthorize web method is now wrapped in a Try/Catch to prevent exceptions from being thrown if SpruceWeb web services are not available. Instead, we now log the exception to the UniversalLog table with a log source of RmtClient. Previously this call would cause a "snap dump" exception if SpruceWeb was inaccessible. (12.10.22) B-45154 - Mobile UpdatesWe re-factored the FTP routine to prevent database transaction locking. (12.10.22) D-42815 - Maintenance / Utilities / Bankcard MaintenanceThe Bankcard Maintenance form when used for Verifone PAYware Connect was not functioning. This has been corrected. (12.10.23) |
D-42213 - Data ConnectionsWe corrected a problem where the database connection could be nothing and cause an exception for the user data object necessary for establishing a data connection. This was primarily occurring with applications that integrate with SpruceWeb (web services). (12.10.19) D-42213 TFS-152262-P TFS-148718 - Release Expiration Warning TimingThe release expiration message was originally triggered 10-days prior to the expiration date of a release. Releases currently expire after approximately 150 days (subject to change). Releases always expire on Wednesdays to avoid weekends; however, the initial warning started appearing on a weekend. For this reason, we have modified the warning to begin 14-days prior to the expiration date of the release. Additionally, other "one-day" expiration warnings triggered on the 20th and 30th days have been modified to be triggered instead on the 21st and 28th days so that all release messaging happens mid-week rather than on weekends. This is primarily being done to ensure support availability in the event of questions. Release expiration warnings don't apply to our cloud-hosted customers as we are responsible for their updates. (12.10.11) TFS-148718 D-37845 - Help - PrintingChange to use the printHelper class for printing Help. Will resolve some issues printing Help from the cloud when using remote client. SPDebugOpt of HelpNoPrint to disable and use native print method. When using the Remote Client Service, this will only work when printing using the RDP method to print, but not when using IIS method (via an Alias). Added some additional checks to see if the form is closing when handling key press and other events to avoid potential errors when the application is closed independently of the help but after commands are issued. (12.10.19) D-37845 TFS-151396 When application scaling (size) was set above 100%, the maintenance form used for setting up the image list would report an error. If a user attempts to access the form while the application scaling is above 100%, a new message will be shown. As soon as the dialog is closed, the maintenance form will close instead of causing an error. To access the maintenance form, temporarily set the "size" (scale) to 100%. D-41403 - Product NameWe have updated various messages and dialogs that displayed some form of product identification to use the ProductName parameter value in place of words such as ".Net" and others. For users of the "Spruce" software, they will see the word "Spruce" displayed whenever possible. Likewise, users of the "RockSolid MAX" brand will see that word in places where the product name is referenced. This is being done to more clearly identify the application source of windows dialogs displayed to the user. (12.10.9) D-41403 TFS-150058 B-44301 - Windows 10 Creator Update - SlownessCode changes were made to work around issues identified with the Windows 10 Creator Update and .NET Framework 4.7.1. (12.10.19) B-44301 TFS-151488-P D-42000 - Maintenance > Task SchedulerTask Scheduler wouldn't allow changes to scheduled reports using the Schedule (F7) function. Code that enables key was commented out improperly while attempting to restrict changes to EOD, EOM, Billing, etc. Schedule (F7) will only be enabled while in Calendar (F5) mode for reports, not where checklists can be changed. (12.10.19) D-42000 TFS-151684-P |
The open credits total in the Receivables section will now use the customer account's AR Branch if set. If not, it will use the document branch to determine whether or not to include the amount. The query was checking for a NULL value instead of a blank value. This has been corrected. D-40242 D-41477 - Footage Calculation on DocumentsCode used for calculating the footage values for documents (Orders, Quotes, Tickets, and Sale Invoices) would sometimes error due to an improperly referenced object. This could cause delays in document processing. In addition, the code has been changed to replace hard-coded values for the board and square footage measures with the code definitions values for default measures. If a company's default measures did not match the string values used, the footage calculations would not be done. They should now be done regardless of the abbreviations a company chooses for their footage-based measures (for example, "BF" vs. "BFT" vs. "BDFT"). (12.10.9) D-41477 TFS-150321 D-41234 - Invoices & Tickets ReportWhen running the report using the filter "Tickets Only," the unit price was not being set when running the report using the "with Details" option selected (checked). Unit prices are now included. (12.10.9) D-41234 TFS-149727 (BETA) D-42125 - Point of Sale / Reports / Invoices & Tickets ReportDue to changes to permit the invoicing of Open Tickets to non-charge customers using the new "Invoice Ticket" (F8) function, changes were made to filter out any "open ticket" documents where the status is not open. Tickets that are invoiced using the new function are not removed or directly converted to invoices; however, the status of the document is changed. Corresponding changes were made to the Item Tracking inquiry. (12.10.19) D-42125 TFS-152103-P PO Purchase OrderComments entered from the Entry folder tab were only being displayed on some PO document styles. Comments now print on all styles. D-40481 D-41152 - Point of Sale - Dispatch Copy - Location CodesWhen obtaining location codes for printing on the dispatch copy of certain Point of Sale, Sale or Ticket documents, the code would sometimes error due to an invalid index specified for an array of locations. This would cause a non-fatal (silent) exception which could cause locations to not print properly. The issue has been corrected. (12.10.9) D-41152 TFS-149383 (BETA) PrintingChanges were made to better handle situations where we are unable to retrieve the default page settings for a Windows printer. D-40142 PS InvoicesOn certain multi-page documents, the card payment information was being printed multiple times in some cases. This has been corrected. D-39626 Products Sold by Date Range (Report)The report now offers subtotaling based on any of the three (3) sort options: vendor, dept (department), and branch). This report is located on the Management sub-menu on the Point of Sale area's Reports menu. D-40234 Fine Print and Multiple PrintersFor transactions where more than one printer selection is provided and the first printer had "fine print" enabled, but the second printer selection did not, the fine print was being printed regardless. This has been corrected so that whether or not we print the fine print text or image is checked for each printer selection. D-40484 |