Emerald 2.5 Updates and Changes ------------------------------- v2.5.342 - 11/20/00 * Adding a static cost service to an existing MBR after the first invoice would casue the pro-rated amount to be based on the Service type cost, not the static service cost. * Quantity is now calculating before rounding a discount calculation. * Updated several queries, including DB creation, to be compatable with SQL Server 2000. * Tax was not being read if with 4 decimal precision, causing a rounding problem is you had a 4 decimal tax defined. (RQST00000008971) * Valued for Vendor Specific Attributes for Service Type Defaults where not being displayed/picked correctly. * If you do not have permissions to save/update an MBR, but did make changes, Emerald would still prompt you to save the account, even though the save button was disabled. (RQST00000009114) * When creating a new service, the Directory Limit Field was not being set. However, it was on an edit. * The max length of the Home Directory text field is now based on the size of the column in the database. (RQST00000009172) * If you unchecked show global in the Admin, both the Admin and client would complain about an incorrect setup for the group, although the group was setup correctly. * Pop up menu for the Invoice list was not being disabled if the user did not have access to those functions. (RQST00000009164) v2.5.339 - 9/15/00 * The PC Transact_IT format was changed to a generic CSV batch out of Emerald, and not includes batch in support. You will need to obtain the definition file and re-configure the out file for this to work. * Printing the radlogs report with a Database not named Emerald would display an error (new ralogs.rpt). (RQST00000008826) * Line items totals which included a tax in the emailed invoices were not displayed correctly, although the invoice total was correct. (RQST00000008780) * If you have Restrict client reports enabled, the auto-batch could not find the global reports. * Adding or changing the home directory of an existing service will now cause Emerald to create the new directory. (RQST00000008862) * Customers who had an unapplied charge could cause the SQL connections to block each other and hang the invoice creation. (RQST00000008834, RQST00000008891) * Deleting an operator in the Emerald Admin required hitting delete twice. (RQST00000008732) * Added Support for X-Stop Class definition in the Emerald Admin. * Taxes with an accumulative floor definition where not being cleared between customers. Floor definitions were not tracking per month correctly (ie, monthly floor, not pay period floor). (RQST00000008655, RQST00000008705) * Taxes for charges are not calculated until applied to an invoice, to allow for accumulative floor definitions to turn our correctly for pro-rate and setup charges. (RQST00000008655, RQST00000008705) * The billing engine now uses a blocking SQL connection when creating invoices. This can cause a slight pause in the display update, but offers a 50 times performance advtange with the DB-lib interface. * Added support for Telecheck EFT batch out. v2.5.337 - 7/11/00 * Added support for CSV PC Transact_IT 1.2 format. (RQST00000007808) * Reseller key types could not be mixed with direct purchased key types. (RQST00000008597). * You must add atleast one line item to a manual invoice before you are allowed to save it. * If a service has sendbill checked, but does not have a login or email specified, Emerald will now treat it as if sendbill is not checked. * Updated the client security to include support for read, add, edit and delete for MBR, services, invoicing, and incidents. If users in the EmeraldSecure group (the only one security applies to) can not do things they use to be able to do, then you need to double-check your Operator Group Access security settings for their operator group in the Emerald Admin. (RQST00000008465) * External Systems were not taking the ma Perm Extensions into consideration when exporting. * Password field on login form would not allow cut/paste of password * Creating more than 32768 invoices in one batch would cause an overflow error * You could add two services to the same account with the same login, although trying to add a third or more would give a duplicate warning. (RQST00000008563) * Trying to set an Email field on an incident type would cause an SQL error upon save (RQST00000008531). v2.5.336 - 6/21/00 * Calls Online was not clearing a roam call entry. (RQST00000008450) * When adding a line item to a manual invoice, you would receive an error stating no more line items could be added. (RQST00000008292) * If you defined an interval larger than 32768, you would receive an overflow error during consolidation for any user with that rate. (RQST00000008309) * If you defined a different standard and over interval, the overcharge was not taking the standard interval into consideration and could create a much larger charge than expected. (RQST00000008144) * Inactive services with SendBill checked would still receive a copy of an email. (RQST00000008235) * After batching in a CC result, you would receive a "52 bad file name or number" error when Emerald was trying to write the summary line into ccbatch.txt file. (RQST00000008256) * Services that did not have an associated tax, would error when being processed by the billing engine. (RQST00000008490, RQST00000008526) * Changing the Incident Type during an add would clear the email field, rather than set the email field to the incident type specific email address. The email field will only be changed from the default admin, if the email is not blank. If you do not want to have an email sent for an incident type, but do what the default, set the email field for the incident type to "NONE". v2.5.335 - 5/17/00 * When batching in Credit Cards, the DB is now updated before the receipt is sent to the customer, so that transaction reason can be included in the receipt. * When installing on an SQL7 server with a different SQL data path, Emerald was defaulting the program path, not the data path. * Bank Trans information could cause a type 13 mismatch when loading (associated to RQST00000008095). v2.5.334 - 5/9/00 * If a user did not have a paymethod of Bank Trans, but did have bank trans information, Emerald would not load the bank trans information when it loaded the MBR and when you selected the bank trans pay method, Emerald was not loking to see if there was any existing Bank trans information. (RQST00000008095) * Certain tax types would give a type mismatch error when trying to create invoices. * Some invoices were being created with the same start and end date, rather than the end date being for the full term. v2.5.333 - 5/5/00 * Added support for ceiling/accumulative tax limits (Texas internet tax laws). * Invoice numbers over 1,000,000 where not displaying correctly, and could not be edited from the main invoice search screen (RQST00000008050). * If multiple CC invoices exist for a customer, only the last invoice will be sent the CC processing system. (RQST00000007980) * Voiding a service pro-rate invoice would move the MBR information back, when it should not have. (RQST00000008020) v2.5.332 - 4/26/00 * When creating an incident, Emerald was not updating the email field to match the email of the incident type. The Email field will now change if you have a different email address configured for that incident type. * If you had two or more groups with different invoices defined for each group, some invoices might not have printed out for the second group, if the first invoice of the first group was higher than the first invoice of the second group. v2.5.331 - 3/7/00 * Updated the PC Transact_IT batch output format to include AVS support and include additional fields that were left out or being written incorrectly (RQST00000007609) * If the last entry in the CC batch set was a CCAutoBill=0, it would not get changed to renewal. * The Emailing of Incidents now includes the Customer in the subject and the Login and CustomerID in the body as well. * The Billing Group for a Discount was not being set correctly from the database when you where editing an existing discount. * Adding a Billing Group without specifying a Domain would cause an error when you tried to save the Group. * Adding a Pay Period without specifying a Discount would cause an error when you tried to save the Pay Period. * Single Clicking on a failed batch item would cause an error and Emerald would close. v2.5.328 - 2/10/00 * Some External Systems sync would fail with an error about not able to load ES information. This including adding, updating and deleting accounts that were associated to External Systems. v2.5.327 - 1/27/00 * A couple CC batch formats were not setting the processed date correctly. * Taxes were not being applied correctly on overtime and toll charges produced by a consolidation. * Voiding a invoice of type invoice was changing the balance, when it should not have. * The query for Payment updates for version 2.5.303 should have set to the minimum invoice, not the maximum: Update Payments Set InvoiceID = (Select Min(InvoiceID) From Invoices i Where i.CustomerID = Payments.CustomerID and Payments.Date <= i.Date) Where InvoiceID is NULL * Autobatch was missing some credit card and bank transfer transactions, although manual batch would process them. (RQST00000007336) v2.5.325 - 1/11/00 * Several parts of the Emerald Admin where not clearing the SQL connection, which could cause an overlapped results, depending on what path you took through the admin. * Updated the Views to allow for adding/editing invoices for the Emerald Secure Group. You need to replace all of your v* views (see the commented out set of drop statements at the top of instview.sql) with those in the instview.sql script and then re-apply permissions (see instperm.sql for the permissions for the EmeraldSecure group). * Credit card numbers were not being validated when you entered them. Emerald will now warn you if you enter an invalid credit card number. * When voiding an invoice, the PaidThru date was not being moved back. Since Emerald does not use the PaidThru date, it did not affect billing, but could be confusing when looking at the account afterwards. * If you have transactions in ICVerify that were manually inputted and the associated invoiceid/transid was a lare number (like a CC number), Emerald would give an error and stop reading the transactions. It will not ignore any transactions that are not of type C1, and also verifies the invoiceid/transid is not out of bounds. v2.5.324 - 1/7/00 * Transactions with a status of re-batch are shown in the failed batch window list until they are re-batched out. * Authorize.Net CC Batch Format support has been added. * Updated Crystal Report Engine Files for 7.0 MR1. * Expire dates could be re-set during a payment, even if the expire date was originally blank. v2.5.323 - 12/27/99 * When deleting an MBR, Emerald was deleting the invoices before payments, which failed if a payment was related to an invoice. The order was changed to delete payments before invoices. * If an invoice had a total for $1000 or more, when making a partial payment to it, Emerald would most likely mark the invoice paid (although the balance was correct) which prevented making another payment on the invoice. v2.5.322 - 12/13/99 * The auto-update on the on-line screen was updating for searches, when it should have only updated for the on-line listing. v2.5.320 - 12/10/99 * A manual batch was treating renewal users as Balance forward, and would continually create a new bill for the next billing cycle. This didn't happen with the autobatch checked, though. * Includes Crystal Reports Print Engine Version 7.0 in the distribution now. This was needed to take advantage of some functions available in 7.0 that are not available in 6.0 (for the history.rpt and several others). * Added the ability to show the drill down, and several additional buttons on the print preview window. * When added a Billing Cycle, the Sort Order was being set to 1 no matter what you typed into the Sort box itself. * The window information for the batch screen was not being saved correctly. * The credit card and address search numbers where not displayed correctly, although the actual search results itself where correct. v2.5.315 - 11/8/99 * Emerald can now automatically re-batch timeout transactions from IC Verify. If a transaction times out, it will mark the transactions for re-batch, the next time you do a batch out. * Editing RADIUS Attributes in the Admin would give an SQL error. The order of the attributes is also now displayed by VendorID, which will group the Vendor VSA attributes together. * Added a paymethod of "Closed" to the list. You need to add the payment closed to your PayMethods table using the following statement, or you will get an error if you try to save a user with that paymethod. INSERT INTO PayMethods(PayMethod, GrooupID, SortOrder) VALUES('Closed', NULL, 8) * If a user did not have access to the Operators table (which they should not by default) Emerlad could not load in your Operator information. It will now try to use the vOperators view as well to retrieve the information (like Email address, etc). * The Web User in the Admin is now always forced on (and will not show) to prevent confusion. Without that option Enabled, the Admin would not save most of the information (because it needed to save it in the Operators table, and unchecking the web user option tells it to not create an Operators table entry for that user). * When making a partial payment to an account and the account only had one invoice, Emerald would not find any previous invoices to base the ExpireDate on, and would set the expiredate to 1/1/00. Now, it will not touch the expired/paid thru dates if there is not any other invoices in the system. * If you tried to void and invoice, you would get an SQL Error, although the invoice itself would get voided. The error was when Emerald was looking to see if there are charges on that invoice. If there are charges on the invoice, you will be asked if you want to un-associated them to the invocie you are voiding, so that they can be re-applied during the next invoice run. * Creating a manual invoice with many line items was giving various errors. You can now add up to 99 line items on a manual invoice. v2.5.313 - 11/3/99 * The batch criteria was checking the maExpireDate rather than the billed thru date to determine customers that needed to be billed for certain autobatch processed. * Add a send method of "None". This allows you to configure an MBR to get billed, but does NOT send them a bill (no print or email). * In Radlogs, if you check show ports, Emerald will show the name of the server if it can match the IP address, rather than just the IP address. * Added an Email button to invoice window so that you could re-send an invoice in email without having to go to the Invoice seciton. * Enabled the Email CC receipt/decline during CC batch in. It was not reading the information correctly from the files and mixing it up with the CC batch in file. * Added ability to print the history from the history tab. This prints a CR report named history.rpt, and sets the CustomerID parameter in the report. * Invoice printing included the wrong name for MasterAccounts when trying to mark invoices as printed. * Printing invoices now only print those invoices for accounts that have their sent method set to Print. If you email invoices before printing and some invoices fail, Emerald will ask you whether you want to also print the failed email invoices, or just those for MBRs with sendmethod set to print. v2.5.303 - 10/2/99 * Emerald was NOT updating the InvoiceID in the payments table. This was causing the payments section of the Invoice to always be blank. You *MUST* run this scrip to update your database, or afer your first billing all payments for each customer will appear on their next bill: Update Payments Set InvoiceID = (Select Min(InvoiceID) From Invoices i Where i.CustomerID = Payments.CustomerID and Payments.Date >= i.Date) Where InvoiceID is NULL * The billing function has been optimized to handle billing faster by not having to check whether each user has charges (it gets the list at the beginning). This should speed up the invoice cycle quite a bit. * If you had the diffcost of a service set to 1 and the cost of the service was null/blank, Emerald would give a type mismatch error during billing. * Toll Charges were being rounded up a full unit over what they really should have been for cost and mins). * Fixed several SQL date formats problems that was not saving dates in ISO format (causing regional/locale problems). * Added an option to send Invoices via email as either text or HTML. Emerald looks for "h" prepended to the invoice name, and if that is not found, just uses the invoice file. * You can not set a default send method in the Administrator, including HTML. * Visanet POS Partner Export format was added. There is no import support yet, though. * The receipts option in the admin will set the default recipts check box option in the batch window. If receipts are enabled, Emerald will mail out a notice to the user during the import phase, with either a declined or processed notice. Three reports are on the ftp site (/emerald/reports) named ccreject.rpt (failed CC transactions), ccemail.rpt (approved CC transctions), and receipt.rpt (receipt to print on the payment window). * When creating a new Billing Cycle, the global group is now the default. It was blank. * The licenses toolbar option was not being show, and the help options all returned the about screen, rather than the browser content. v2.5.300 - 9/21/99 * Menu options for the invoices windows has been added, including a pop-up menu on the invoice list. * The Show toolbar setting is now saved to a registry setting. * The HELP URLs have been updates to reflect the current website pages. * The order of the name on the invoice search has been changed to lastname, firstname to better facilitate sorting the result list by last name. * Both the Admin and Client have been updated to better handle a mis-configured "show global" option for a group. The admin will not let you set that option unless you have a group specific entry for each list, and the client will tell you the group is configured wrong and set the "show global" option for that group until you correct the problem. * The restrict option (Password, Delete, Expire) when enabled will disable those buttons/options unless the user is SA or the user's group is EmeraldAdmin. * There is a new history procedure available to clarify the status of the invoice (void/normal) and to hide charges that have already been applied to an invoice. See the newhistory.sql script. * The payment screen now includes a cancel button. For those invoices that have a previous balance, when applying a payment to them, the first entry in the payment screen will be the previous balance. * Deleting an Service Type would fail is there were Server Access entries for that Service Type * The count displayed during an account search did not take into consideration the group or region selection (although the search itself did). * The Reports and Batch menu options did not bring the respective screen up. * The Window list has been moved to the end of the Window pull down menu, rather than a submenu off the window menu. * The manual invoice date was not being created/calculated correctly. * Paying a standalone invoice with an amount larger than the current MBR balance caused all other invoices to be paid as well. * When deleteing an MBR, forwards and aliases were not beinged deleted. * A manual charge with a tax associated with it was adding the tax into the base amount. * The call history entries were being entered into SQL in US format, rather than ISO, causing non-US regional date problems. v2.5.280 - 8/1/99 * Emerald Accounts -> Search shows the first and last name of the MBR if the values in the Sub-Accounts table is null. * Emerald User Edit. Max length of fields match database for new alias, new forward, new email, and new Radius data. * License key algorithm updated. * Emerald and Emerald Admin License Keys. Temporary keys handle the year 2000 properly. Adding new keys trims out spaces from the front and back to reduce user input error. * Emerald Admin -> Accounting -> Rates: Primary and Secondary Tool tips updated. Better error handling for input not in HH:MM format. * Emerald Admin -> Accounting -> Services. Adding a service. When the Add button is pressed, the message that tells how many defaults are defined for this service type is set to default. * Emerald Admin. prefix and suffix have been removed. Prefix and suffix are not used. The fields have been made invisible on the form. * Emerald Admin -> Client Configuration -> Accounting The Store number is now correctly stored. Merch ID is kept as a string so that scientific notation isn't used when the number of digits gets large. * Emerald Admin. Data entry in the Accounting, General, and Client Configuration forms. Single quotes are properly handled when used in text fields. * Emerald Admin. Client Configuration form. Tab order redone for items in each tab of the Client Configuration form. They now follow a logical path. * Emerald Admin. General Configuration form. Edit boxes made read-only for the following General Configuration form fields: Modem Speed, System Type. * Installation Program - Emerald Admin and Client Items are checked during program installation. If Internet Explorer 4.0 or higher is not installed in the system, then the user is notified that the integrated web browser function will be disabled. Verify installation of SQL client utilities. Registry entry must exist. Tell user that SQL Client must be installed first, then abort the installation. * Create Databases - Emerald Admin Temp DB size check for SQL 6.5. If the temp db is < 12MB a message in red is displayed to warn the user that it needs to be increased. Ask user and expand by given amount. SQL Server version check SQLVersion must be at least 6.5.258 (SP3). Physical memory check PhysMemory must be at least 64MB. SQL 6.5 memory check SQLMemory > 16MB. Suggest to user that it should be 50% of PhysMemory. If the value is 16MB (8192) warn the user that the value must be increased. Ask user and expand by given amount. * About Dialog Box - Emerald Admin SQL 6.5 Temp DB size check added. Print warning message in red if < 12MB. Physical memory. SQL 6.5 memory. Suggest to user that it should be 50% of PhysMemory. If the value is 16MB (8192) warn the user that the value must be increased. * Emerald Admin - Database Maintenance SQL 6.5 Space used in Emerald DB. If database is using 70% or more, allow user to expand the database size. Ask user and expand by given amount. SQL 6.5 Size of transaction logs in Emerald DB. If transaction log is using 70% or more, allow user to truncate the transaction log. Ask user and truncate. * Emerald Client - Startup Inspector Upon startup, these items are checked. Space used in Emerald DB. If database is using 70% or more, warn the user to expand the database size. Give the user an option to disable this warning message. If the database is 90% or more start warning again, ignoring the disable option. Size of transaction logs in Emerald DB. If database is using 70% or more, warn user to expand the database size. Give the user an option to disable this warning message. If the database is 90% or more start warning again, ignoring the disable option. SQL Client files. Don't start program if registry entries are missing. * Emerald Admin - Check Database - Post-Conversion Utility A new SQL script has been added to check the database for consistency. This is especially important after a conversion to make sure all links are setup properly. * Emerald Admin - Check Database - Update Ports Table A new SQL script has been added to automatically add port numbers to the database. v2.5.270 - 4/10/99 * Fixed several problems with adding/editing VSA entries in Admin. * Emerald was incorrecly saving money to four digits, rather than two. This could cause 1 cent balances to show up after a while. * Invoice Next Term should work for all customers now. * Sometimes a $0 charge was beeing applied to newly created accounts, when there wasn't a setup charge associated to the account. * Paying an invoice that was already paid would cause a looping "Invoice Already Paid" with no way to exit. * The Shift key was being incorrectly interpretted as the alt key for some keyboard shourtcuts on the accounts and invoices search screens. * Double-clicking on the top of a column in the Incident grid would cause contents of the grid to clear, rather than sort it. * Moving Services from one MBR to another would sometimes fail. * Added an option to show password in the RadLogs (whch is now not the default). To showthe passwords reuires a fairl intense join on larger systems that can take a considerable amount of time. You can only show passwors when looking for a specific user. * Added some logic in TS Graph to hadle USR Terminal servers. * Changed the debug to be in a new window rather than use the clipboard. This is enabled via the preferences or the debug option on the login window. * The setup charges where being ignored if they were a negative amount (credit). Some people wanted to use a setup charge as a coupon or discount (therefore, it would need to be negative). * Fixed SQL Date problem with RadLogs for non US Date formats. * Shortcuts where also using the shift key when they should only be using the Control or Alt key in the accounts window. * Credit Card Auto Bill was incorrectly changing some accounts from Credit Card to Renewal v2.5.262 - 2/19/99 * Voiding and invoice with a non-blank date was causing and SQL error and the MBR was not updated. * Credit Card Auto Bill should correetly handle the situation where AutoBill is set to 0 (will change the MBR to renewal after the first Credit Card invoice). * If you had a service defined with tax, Emerald would show the tax in the MBR edit, even if the MBR was not taxable. * If the MBR was not taxable and you added a service to the MBR with a monthly billing cycle, the pro-rate charge showed a tax of 0, whereas it should not have shown a tax at all. * The field lengths were not being checked correctly, which was restricting the length, even if you changed the size of the fields (like login, state, etc). * When paying an invoice, the default amount to pay was incorrect when the invoice paying included taxable line items. * Moved the Incremental Batch from the client preferences to a global option in the Emerald Admin, client section. * Window positions are not stored if the window is minimized. This resolves the problem of windows disappearing or not in the view when you re-start Emerald. * Removed an un-needed query from the billing routine, which should speed up the charge processing. * Changed the consolidation procedures to use the BilledThru date rather than the Expire Date. The consolidation was failing in situations where the ExpireDate of the user was blank and generating a type 13 mismatch. * You need to drop/re-add your consolidation procedure (see the updtcons.sql file) to correct the above problem. * If the Consolidation had no records to consolidate but the summary listed records to consolidation, an Invalid Property value error was being generated. * The consolidation would try to put two entries for each user in the CallHistory table and two charges in the charges table, for the for the same time. * If you changes information in the MBR and then selected invoice next term, Emerald would save the changes but still unload the account, causing the invoice next term to fail. * The manual batch was incorrectly including the first day of the next month for those accounts configured for balance forward. * The auto batch was limited to accounts 60 days old or less. It was also incorrectly excluding accounts where the billedthru/expired dates where the same as the last invoice end date (they can be the same, they can not just overlap). * Emerald will not warn you when changing the billing cycle from an balance forward to renewal and the expire date is blank. It will also warn you if you change an account from anniversary to monthly after you have created and saved it (you will need to manually adjust the dates to be monthly, along with any required charges). * The Emerald Admin was not tracking Vendor Specific Attributes correctly, which was causing problems when try to add new VAS entries or values. * Renaming a VSA caused all VSAa to be renamed regardless of their VendorID or VendorType. v2.5.249 - 1/28/99 * Option to show SubAccount expiration date added to the Administrator * Corrected problem with Preferences crashing the client * Users must have Invoice Add permissions to access many of the accounting fields like expire dates, balances, and the batch options. * When reactivating an account that was previously manually deactivated, the billed thru date is set to today. * If an operator username or password started with a number it was failing to be created. * Corrected Operator setup issues in the admin where is the Operator existed on SQL Server but not in the DB itself, you would get an error and fail to add/update the operator. * Added search by CustomerID in the Invoices search window. v2.5.236 - 1/22/99 * Creating a stand alone invoice should now work (tax problem). * Added Control-P as a shortcut for printing a MBR when you are editing the MBR. * Consolidation Procedure was not adjusting the Date based on the Acct-Delay-Time and Acct-Session-Time. This could cause mis-calculations when billing based on time of day. * Added four new advanced search options: Non-bill accounts - Shows those customers that will not be billed because they have an invoice end date that is after their billed thru date. Credit Accounts - Shows those customers that have a negative balance (credit). Diff Cost Accounts - Shows those customers with a service that has the static cost checked. Over Limit Accounts - Shows those customers where thier balance is equal to or larger than their credit limit. v2.5.236 - 1/19/99 * Printing in auto-batch should now correctly display the unsent invoices. There is still a performance issue when you have a large number of invoices, though. * Several fields (including Expire Date, Billed Thru, Creating adjustments, and select the setup charge) are only available if you have invoice add access for the group of the MBR you are editing. * Taxes on charges were causing the total of the invoice to be calculated incorrectly (the total amount was higher than it should have been, although all the line items were correct). * Emerald will now set the expire date equal to the last end date of the last invoice that is not void. This prevents the partial payment problem where multiple partial payments incorrectly set the expire date ahead each time. * When you bring an account to 0 or a credit with a payment, all outstanding invoices are marked as paid so that aging will work correctly. * The aging tab now correctly shows the account aging information based on the current balance, not on what invoices are marked as paid in the database. This is the true "aging" method. * If the receipt printing option was selected, a blank receipt was being printed. The receipt should now contain the proper paypment information. v2.5.234 - 1/15/99 * Updated security on the client to restrict accounting functions if the user does not have add on the invoice permissions. * A copy of the incident should not be emailed if the email field is not blank. * If the operator is not listed in your operators table, their Email is not defaulted to the admin email. It was defaulting to blank, which caused some of the emails to fail. v2.5.229 - 1/8/99 * When Emerald is creating invoices, it will automatically pay an invoice where the amount is 0 or less (the user had a credit on the account). This will automatically extend the account's expire/billed thru dates without requiring intervention. For those invoices creasted before this version, you can not pay a 0 amount on an invoice so that the dates get incremented correctly. * TS Graph should now work with Microcoms. v2.5.227 - 1/5/99 * The Over Limit was not being read in from the database when editing a user. * Corrected problem with time-on display for a user giving an invalid column error. * Corrected error when trying to create a database in the admin * The Billed Thru Date was being changed incorrectly (although not saved) when you edited an MBR. * Corrected line item calculation problems in the invoice.rpt * The service default attributes were not allowing you to add Vendor Specific attributes (it would give an SQL Error). It was not displaying the right vendor information when you selected the attribute either. * Emailed invoices were incorrectly included a content type of html and only sending one at a time. * IC Verify now sends the customers name, not the Company Name in the batch file v2.5.223 - 12/30/98 * Corrected problem with the PC Authorize batch in format that Emerald was trying to read from PC Authorize. v2.5.222 - 12/29/98 * Corrected problem with the PTC Credit Card Format not importing the results from PTC. * Added an update calls section to the Database Maitenance to allow manually updating the calls table so a consolidation can be ran (this is needed if you have not installed the task to do this). * Corrected an invoice problem that caused a type mismatch error is a user's balance was NULL. * Corrected Problem in the Emerald Admin that prevented modifying the server ports. v2.5.211 - 12/23/98 * The Accounts Mail Address in the admin was not being read in, therefore all mail was being sent out from the mail admin address. * The Email invoices only emailed one invoice for each time you pushed the email button on the batch tab, rather than all of them. v2.5.143 - 9/20/98 (ems25b8) Upgrade Notes: For Emerald 2.1/2.2 customers use the Emerald Admin, Update Database option to update your database. DO NOT update your production server. Update a copy as noted in the readme.txt file. If you are running an earlier version of Emerald (like 2.5b7) you will need to run just the noted end part of the updattabs.sql. Do NOT run the full updattabs.sql. It probably won't hurt anything, but itsn't neccessary (you already did it). * Security is currently not fully implemented and disabled for this release. * The install may complain about msvcirt.dll and shdocvw.dll. You should select ignore for both of these and the install will work fine. * The version of RadiusNT is a test version, and should NOT be used in production. We will have a seperate changes file at a later time discussing the additions of RadiusNT 2.5.200 and higher. * The SNMP concurrency control for this version has changed and requires additional configuration to work (this will be added to the docs for RadiusNT before the final release). In the Emerald Admin, there is an SNMP Type for the server to choose between a direct OID and a modified OID. * The ServerType is now stored and tracked in the Emerald Admin. * The rates have been updated to support an interval setting. This allows you to bill usage at any granularity you want. The interval is based in seconds and the default is 3600, which is per hour and what 2.2 and lower used. You should set the interval for standard/over the same for now. EMS25B7 ------- * Corrected setup problem with missing CR files causing E-Mail invoices to not work on systems that didn't have a full CR 6.0 install. * The Documentation is included and installed with each option chose. * Moved all acconting configuration from the General tab in the Emerald admin to its own area, called Accounting. This should make configuring the Accounting section easier and the general less cluttered. EMS25b6 ------- * Includes a fully revamped tax system that should satisfy the requested tax needs. These include single, dual, and piggyback taxes, and are fully trackable (for reporting) by type. The old taxes for each sub account will not be used any more. Once you upgrade to B6, you will need to go into the admin and re-configure all of your taxes. * Taxes are now available on charges as well. This includes custom setup charges as well. * The Emerald Admin has been given a face lift, including a MDI layout to match the Emerald Client, and a split of all Acocunting configurations to their own area. This should make configuration a little less cluttering and confusing. * A new tab in the Accounting area was created for defining taxes, as well as being able to select one of the pre-defined taxes for a service and charge. * Support for per-group FTP paths has been added. You can add a path per group to override the global path. If neither the global path nor the per-group path is defined, an FTP dir will not be created.