These Help Files were last Updated on 06/24/2013
<< Click to Display Table of Contents >> Navigation: STARK Version 5.1.35.XXXX New Features > Previous Versions of New Feature Information > Version 5.1.33.X CorrectionsThese Help Files were last Updated on 06/24/2013 |
❑Welcome to the Corrections Chapter for 5.1.33.X which contains the changes implemented after the MKMS Version 5.1.33.5 Release.
•This chapter provides a brief explanation of the anomaly Corrections (and some Additions) that were re-programmed after 07/07/2012 when the 5.1.33.5 Release was officially shipped.
✓The entries are generally listed in the order these Corrections ("bug fixes" and processes that should have worked this way in the first place) were implemented within each Module.
✓Some MKMS and MKMSCS Users may have received an interim upgrade which already included one or more of these Corrections.
❑Understanding the Corrections Chart:
•Program Module(s) Affected are listed.
•Chapter Links are provided to locate the instructions, illustrations, and details of the proper operation of the feature.
•A brief Description of the Anomaly is included along with the Corrections information, where appropriate.
Program Module(s) Affected |
Chapter Links |
Description of the Anomaly & Correction |
---|---|---|
|
Various Reports |
The following Reports were updated to address intermittent issues: ▪Accounts Receivable Report - Receipt ID error fixed. ▪Cash Receipts Report showing random Refunds when printed By Division has been fixed. ▪Attrition Report - New (Additional) options ▪Accounts Receivable As Of Aging Report - By Division option added. ▪Leads by Salesperson - The error - displayed when the Leads by Salesperson report option for One Lead Type was selected - has been corrected. ▪Leads by Salesperson - One Person option issue corrected. ▪Leads Report - Syntax error if One Lead Source and/or One Lead Type was selected. ▪System Audit Report - Error occurring when a specific User is selected, has been corrected. ▪The Dealer Breakdown Report now displays the appropriate data when the Detail options is selected. ▪The Panels With No Signals Since report now excludes all of the Deleted and Off Line accounts. ▪The Month and Year fields on the General Journal Report Options tab now default to the current Month and current Year. |
The right side of the Calls Form was expanded to reveal the Alt+F9 (Date & Time + "No Answer" message) option. ▪The Navigator Arrows for the Previous Calls List now work correctly. ▪Print function error on Date/Time corrected.
The Options Tab on the Proposals Form now correctly supports a 70 character Description. ▪When defining a Recurring Revenue Fix Term Item on the Recurring Items tab of the Proposals Form the Frequency Rate Amount was improperly calculated, but is now calculated correctly. |
||
Transferring Receipts |
▪The issue where a Sales Invoice with a Credit Line Item was not updating the Balance Due field (within that Invoice Line Item table) has been resolved. ▪The issue where the name of the Balance field was not displayed on the Sales Form has been corrected. ▪The issue where the Balance Due was updated incorrectly after a Credit Memo had an Itemized Allocation has been fixed. ▪An Invoice (Sale) created from a Job Task now properly records the Sales Tax Code information. ▪When an Invoice Detail Line Item has its Department Number changed, that revised Department Number is now properly recorded in the General Ledger module's Account Register. ▪When the Amount of a Receipt record is Modified the Description information is now properly recorded in the General Ledger module's Account Register. ▪The error that sometimes occurred when Transferring Receipts within the Receipts Form has been eliminated. ▪The issue where the Balance Due was updated incorrectly after a Receipt had been Unallocated has been fixed. ▪While performing an Unallocation, the error presented during that Unallocate procedure is now fixed. |
|
The Control "" Has no parent window error presented during a modification of an existing Subscriber record has been corrected. |
||
Reminders Start Date issue resolved. |
||
▪Requiring that a Vendor ID be identified when a new Sale type of Sale-Purchase Item was entered has been eliminated. ▪The foreign key 'SaleItemID' error displayed on the Sale-Purchase Items Form when a Vendor Item ID is entered has been fixed. ▪When adding or modifying a Non-Inventory Sale-Purchase Item, the system will no longer prompt for an entry in the Price In field. ▪If a User changes the Item Type field of an Inventory related Sale-Purchase Item to Sale rather than Both, the record cannot be saved without Un-Checking the Inventory Item box on the Sale-Purchase Item Form, and confirming that it is no longer an Inventory Item.
▪The Kit Components tab on the Sale-Purchase Items Form will now accept up to 40 character Sale-Purchase Item Codes. ▪The Kit Price In on the Sale-Purchase Items Form is now properly calculated. ▪The Sale-Purchase Item Form's Kit Components tab (displayed when the Inventory Item and Kit Designation boxes are Checked) no longer allows a blank Component line entry to be saved. |
||
▪An error occurring when a New Auto Bill record is added was fixed. ▪The incorrect Quantity (based on whether the entry was created before or after Noon - honest) on a Pro-Rated Invoice created after an Auto Bill record was defined has been corrected. ▪For Pro-Rated Invoices created after an Auto Bill record was defined - if a Department Number was assigned to the Sale-Purchase Item used to create the Pro-Rated Invoice, the appropriate Department Number is now correctly identified. ▪Fixed Term Auto Bill items are no longer displayed in Red unless the End Date has passed. ▪The Format Error on Description error that occurred when using the Authorize.net service for Auto Draft has been corrected. |
||
When Billing Recurring Revenue, the issue where the End Date information on an Invoice line item showed a different number of Days than what was shown in the Invoice's Comment area is resolved. |
||
Regulus Import Payments Acquisitions
|
▪The Regulus Import Payments procedure error when MasterCard® and/or Visa® payments were posted has been eliminated. ▪Acquisitions Form save error on CoSigner is fixed. ▪The other issues with the Acquisitions Form not saving certain data correctly have been fixed. ▪The error displayed when saving an entry in the Drivers License field (Drivers Lic #) on the Acquisitions Form has been resolved. |
|
▪When Printing Invoices, the Print to File Text options now works correctly. ▪When a Color version of an Invoice is Printed, the Purchase Order Number is now printed in Yellow with a blue background to make it more visible. ▪The PONumber field error has been corrected when the Email option for Printing Invoices is selected. |
||
▪The Invoice Listing dialog now sets the Form dimensions to the appropriate size. ▪Subscriber's Total Sale Amount issue corrected. |
||
|
When adding or modifying a Non-Inventory Sale-Purchase Item, the system will no longer prompt for an entry in the Price In field. |
|
The Show Deleted Service Accounts? option on the Bill Payor Listing is now reporting those accounts correctly. |
||
▪The Select a Division Drop-Down Selection Box on the Sales Analysis Report Options tab now displays the correct information, without presenting an error message. ▪When the Detail version of the Sales Analysis Report is selected for All Divisions, the data is now correct presented. |
||
▪The Cut / Copy / Paste / Delete menu choices accessed with a Right-Click on the Note and Division fields - on the Subscriber Statements Options tab - now functions correctly. ▪Emailed Subscriber Statements with the Use Pre Printed Form option selected now Emails the Statement with the Name/Address information entered in the Company tab on the User Options Form. |
||
▪The Comments field on the Invoice Form now allows a Double-Click to open the Invoice Comments Editor without an error. ▪This issue of modifying a Detail Line Item of an Invoice, and not having the Totals recalculated properly, has been fixed. |
||
The Invoice Line Item error that occurred when Converting a Proposal to an Invoice has been corrected. |
||
|
|
|
|
▪When printing an Open Service Requests, if the Technician (Employee) assigned to a Service Request has an End Date entered, that Technician will now properly be printed on the Work Order. ▪When printing a batch of Work Orders using the Open Service Requests report, certain details for the first Account (e.g., warranty, phone, comments) printed on every Work Order is resolved. |
|
▪Service Requests which are Chained to a new Work Order will now properly transfer the Scheduling Instructions to the new Service Request. ▪Service Request assigned a Serviced On Date now auto-completes the Work Order. ▪When deleting a Service Request, the Inventory Must be Cleared before deletion error has been fixed. ▪The Error which occurred when Printing a Service Request with a Signature, and using the Custom Report option, has been fixed. ▪When opening a Service Request Form, Warning Messages are displayed based on certain circumstances (e.g., Outstanding Balance Due, open (i.e.,unfinished) Service Requests exist, their Service Contract has Expired) - even if the only open Service Requests were created automatically using the Auto Service feature. oThis functionality may now be changed by setting the new Company Settings option "IncludeAutoServiceWO" to False ("F") to eliminate those Warning Messages when the only open (unfinished) Service Requests were those that were created automatically using the Auto Service feature. oSetting this "IncludeAutoServiceWO" option to True ("T") will turn on Warning Messages (if appropriate) regardless of the origin or type of any existing Service Requests. |
||
Installed Equipment Codes Form now accepts and properly saves up to a 40 character Sale-Purchase Item Code and it's associated 70 character Description. |
||
The issue that occurred when a specific Tech Group was selected for the Services Performed Report has been fixed. |
||
▪A Technician Status Note is no longer are saved as Rich Text Edit entry. ▪The Technician Activity Report no longer displays Rich Text Edit characters. |
||
▪The Quick Work Order Form now remains open when a Subscriber Account is still under Warranty and/or Under Contract and no manually created Work Orders have been opened. ▪The Quick Work Order error for wrong number of values for insert is fixed. |
||
|
|
|
▪The Generate Invoices option on the Job Task tab of the Job Costing Form no longer presents a Transaction conflict error. ▪Job Costing Form now is able to support a 40 character Sale-Purchase Item Code. ▪Inventory Used on the Job Costing Form now correctly updates the Committed On Hand field in the Sale-Purchase Item Form. ▪Inventory Used on the Job Costing Form now properly supports a 40 character Sale-Purchase Item Code. ▪Inventory Used on the Job Costing Form when added to the Installed Equipment Form for that Subscriber will now use Today as the Installation Date and properly calculate theWarranty Expiration Date as one year from Today. ▪The Inventory Reserved problem - which caused an Inventory Item's Description to change when a different Warehouse was selected - has been corrected. |
||
|
|
|
▪Purchase Order - The Email Button now works. ▪The issue with a Purchase Order having a Sale-Purchase Item Code longer than 16 characters not populating a Bill line item and/or the General Ledger Inventory account properly when the Purchase Order is converted to an Invoice has been fixed. ▪A Purchase Order which has a Department Number changed on a Line Item during the Check In / Bill It process now properly records the correct Department Number in the General Ledger module's Account Register. ▪Bills being modified within the Accounts Payable System, which have an original Billing Date in a closed period, the General Ledger System will now be properly updated. ▪Bill creation with a Department assignment change made prior to saving it no longer presents a GL Month Closed error message. ▪The issue with a Bill Line Item being created without a Department Number has been fixed. ▪The issue created - specifically when Allocating Payments and the Bill ID and Payment ID are (coincidentally) the same - has been resolved. ▪The error when Allocating Payments that occurred when Double-Clicking an Outstanding Bill has been eliminated. |
||
The inability to Void a Payment was corrected.
The right side of the Calls Form was expanded to reveal the Alt+F9 (Date & Time + "No Answer" message) option. ▪The Navigator Arrows for the Previous Calls List now work correctly. ▪Print function error on Date/Time corrected. |
||
▪The Bank Reconciliation Form has been substantially revised and is now functioning as anticipated. ▪If the Refresh button on the Bank Reconciliation Form is Clicked, the Transactions displayed on the Transaction List section Grid are no longer doubled. |
||
Payments made using ePay will now be saved as Printed as so will no longer appear on the UnPrinted Checks Report. |
||
▪The cause of a Sales Tax related error on Credit Memos has been corrected. ▪The Credit Memos issued for Bills VendorIDInvoiceNumber error message is now resolved. |
||
▪The Import Payroll paycheck Values were not, but are now being displayed correctly in the Bank Reconciliation Form. ▪The Pay Import Regulus Import now accepts MasterCard® and Visa® entries without error. |
||
In the Bank Transactions Form, Bank to Bank Transfers 'From' and 'To' information has been corrected |
||
The updated Purchase Order Listing dialog now includes selection options for the Status of the Purchase Order, Which Orders will be listed, the Order Dates to be reported, and the ability to specify which Vendor's Purchase Orders will be included. |
||
|
|
|
▪The Other contact button (see the Quick Dial Button chapter), when used during Dispatch and/or Notification procedure, now records the Call as a Notification instead of a Verification contact. ▪When the Other contact button is used twice during Dispatch without a Resolution Code being selected, the Operator will be prompted to enter a Resolution Code or to Redial and will now be recorded a Notification. |
||
▪When the CSID Zone being processed by an Operator requires a Dispatch - Other response, the Operator Note Form now displays when required. ▪When the CSID Zone being processed by an Operator requires a Dispatch - Other response, the F4 History function now works without error. |
||
▪An Operator who is not a Central Station Supervisor now has access to the Default Priority Level Sort Order in the Alarm Stack. ▪The first Click on the Priority column's header (the Default Priority Level Sort Order) returns the Alarm Stack to the Default Priority Level Sort Order. A second Click reverses that Default Sort Order. |
||
▪During a Shift Change procedure when a Temp Note is added, the Operator's Employee Code is now recorded accurately. ▪During a Shift Change procedure when a new User is logged in, the Monitored Signals and CS Users dialog boxes are now updated properly. |
||
The RestartActionPlanfromOnHold company setting is initiated. ▪The default setting for this option is False ("F"). ▪For those companies which need it, setting this option to True ("T") in the Company Settings dialog accessible through the Company tab on the User Options Form will restart the Action Plan - that was in effect when an Alarm Signal was placed On Hold - when it is taken Off Hold - from the beginning. |
||
The PanelConnection error on the Panel Connections Maintenance Form has been corrected. |
||
▪The Quick Work Order Form now remains open when a Subscriber Account is still under Warranty and/or Under Contract and no manually created Work Orders have been opened. ▪The Right-Click functionality (to Copy and/or Paste data) has been activated on the Quick Work Order Form and the Operator Notes field within MKMSCS. ▪The Quick Work Order error for wrong number of values for insert is fixed. |
||
▪When Placing an Account on Test, any additional CSID identified during that procedure may no longer be modified. ▪The Place an Account on Test dialog's Look Up Account & Dealer Password functions now display correctly. |
||
▪The Terminated/Not Connected to Database error presented when exiting the Central Station Monitoring module has been fixed. ▪When exiting the Central Station Monitoring module an error 301 connection was terminated message has been fixed. |
||
▪The Alarm History was displayed incorrectly because Operator Notes were being incorrectly time-stamped. These Notes are now assigned the Server Time. ▪The Alarm History will store and report the GPS (Geo Tag)coordinates of the Premises if the Alarm System has that capability to transmit that location and the Receiver has the capability of interpreting that location information. |
||
Subscribers assigned an Off Line Date on the Central Station Data Form will no longer be included in the Failed To Test Report. |
||
When the Chart option is chosen on the Dealer Breakdown Report, the reported data now properly matches the report's selection criteria. |
||
When an Operator is performing a Dispatch for a Medical related emergency, the Permit Number field is no longer displayed. |
||
While Processing an Alarm, the issue with having the Temp Notes tab disappear when the Operator moved between the Signal Processing tabs has been corrected. |
||
When a Condition Code - identified in the Conditions Call List - is sent by a Specified Subscriber Panel(s) CSID, the customized People To Call List that was previously defined as such in the CSID Zones Form is now properly displayed. |
||
Resolutions Codes may be identified as Inactive. ▪The issue with Inactive Resolutions Codes being included in the Drop-Down Selection Box list - used by an Operator for choosing the appropriate Resolutions Code while Completing an Alarm - has been corrected. |
||
The Alarm History Lookup Options tab's Date Range selection now correctly defaults the Specify Date Range From and To fields to the last 24 hours, instead of the next 24 hours. |
||
When the Other type of Event was defined with a Start Time before 9:00AM, an incorrect Next Scheduled date was displayed. This problem has been corrected. |
||
▪When a new Action Plan's Action Steps were defined, the problem where the entries - once saved and then viewed again later with only the first two lines being displayed - has been corrected. ▪The issue - where the Email Contacts Action Step did not include the defined Message when the Email was created during the Notification Process - has been fixed. ▪When Processing Alarm Signals and an Action Plan is in effect: the Alarm Signal displayed during a Verification procedure will now properly display the Premises telephone number's Extension. ▪When Processing Alarm Signals and Dispatching a Fire Alarm Signal, the resulting Field Fire Permit Number error has been fixed. ▪The title bar in the Dispatch screen area no longer includes the CSID. ▪A CSID containing a Quote (") is now properly processed when entered using the Manual Signal (F7) option. ▪The (Shift+F5) Temp Notes dialog is again available to the Operator while Processing Alarm Signals even if there are currently no Active or Expired Temporary Notes. ▪The (F4) Alarm History dialog is again available to an Operator while processing an Invalid Alarm Signal. ▪An Operator may - at any time - view the Signal History for the Subscriber who currently has an Alarm Signal displayed on the Signal Processing Form (and therefore is being processed by that Operator), by Pressing F4. ▪If there are no active Temporary Notes, the Temp Notes tab will not be displayed. ▪However, while Processing an Alarm, the Temp Notes dialog may be accessed at any time by an Operator by Pressing Shift+F5. |
||
The Subscriber Information Report now correctly displays the Letter Code for each Day of the Week above those Check Boxes. |
||
▪The Panels with No Signals Since report now all Deleted and Off-Line Accounts ▪The Dealer Breakdown Report now displays the appropriate data when the Detail options is selected. |
||
The Scheduled Reports Form for defining the required reports to be sent via the Communications Module now saves a new entry with no errors. |
||
A CSID Zone Default Call List (CALL DEF) record is now presenting the correct People To Call information for the Alternate Call List and Dealer Call List when these type of Call Lists are defined. |
||
When a Condition Code - identified in the Conditions Call List - is sent by a Specified Subscriber Panel(s) CSID, the customized People To Call List that was previously defined as such in the CSID Zones Form is now properly displayed even when no Signal ID or Panel Zone is defined. |
||
|
|