jbilling Changelog

What's new in jbilling 3.3.1

Dec 29, 2014
  • Fixed bug: Object is not an instance of declaring class
  • 11115: Fixes for Two error message while user try to save enumeration without entering data
  • 11114: Fixes to disable cancel button while Save Changes is working
  • 10700: Exception occurred on viewing invoice report with period breakdown week/month.
  • 11096: Product with no price do not add properly in an order.Description gets missing.
  • 11043: Refreshing spinner keeps revolving at order creation page
  • 10720: Exception occurred on API test.
  • 10704: Product details do not open if there is no price associated.
  • 11068: Exception occurred on edting metafields
  • 11067: Adding currency don't save successfully
  • 10699: Exception occurred on accessing 'Inspect customer screen'
  • 9860: fixed issue of Inconsistent start/end date representation between excel report and Pdf format.
  • Changes done to create customer
  • 10697: Customer gets created without data in mandatory 'Email' field . Email address do not save
  • IMPROVEMENT:
  • Added a new constructor
  • Fixed changesets in 3.3.xml
  • Fixed changesets in 3.2.xml
  • Test Case Fix
  • Test Case fixes
  • Improvement
  • Improved changesets
  • Changed the run-time hsqldb version
  • Improved changesets
  • Fixes to HSQL Queries
  • Improved changesets in xmls
  • Correct value for app.version
  • Edit product is working fine
  • Unable to save a Product
  • DESIGN:
  • 8163: Commit for fixing mark all required fields as required in GUI
  • Resolved issue when next invoice date giving error when permission is not there while edit customer.
  • 8099: Discounts menu is not visible on master or telco branch instances.
  • Replaced constructor call with the static method invocation.
  • 9786: Description of order not displayed
  • 9539: jBilling User passwords logged as clear text in jbilling.log
  • Fixed some errors
  • Added New LOG.Debug
  • Resolved most compilation errors
  • Added community Licensing Jar
  • Replaced with jBilling GNU Affero GPL
  • Replaced with Community License.
  • Removed unwanted import
  • Name of the API changed. Also the line removed will be complemented by removing the target classes folder before running this script.
  • 9653: Defunct payment fields displayed on Billing Process Configuration screen
  • Changes added in xmls
  • Field does not belong to the object
  • Required changes for community branch edition
  • Test Case Fix
  • Fixed failing test case

New in jbilling 2.2.0 (Sep 9, 2010)

  • Enhancement Exclude suspended users from the billing process.
  • Bug fix Fixed bug where additional contact types could not be created for a customer.
  • Bug fix Avoids loading all the customers of a company for the billing process.
  • Enhancement New API methods to manipulate items and rate orders.
  • Bug fix
  • Enhancement Queries related to contract fulfillment work now on invoices (paid and not paid).
  • Bug fix
  • Bug fix Several fixes to post­paid contract support
  • Enhancement New internal event for invoice generation
  • Bug fix Fixed bug related to custom fields in PDF invoices.
  • Bug fix Fixed bug where the item number was ignored when creating a new item.
  • Bug fix
  • Enhancement Makes the client API thread safe
  • Enhancement Conversion of Contact entity beans to JPA.
  • Enhancement Conversion of Permission and Preference to JPA
  • Enhancement
  • Enhancement Migration of User, Entity to JPA
  • New feature
  • Fixed the rules 'file' plug­in parameter to work with multiple files again, whether
  • the path/s are absolute or relative from 'jbilling/resources/rules'.
  • Invoices with credit balances can have their credit payments delayed until the
  • next invoice.
  • Fixed bug where calling 'payInvoice' would create a payment without a date.
  • Fixed bug where the customer 'exclude from ageing' can not be unchecked.
  • Fixed RefundOnCancelTask to correctly calculate percentage item order line
  • amounts for refunds.
  • Fixed bug where the servlet up check was not working, it did not have a
  • transaction context.
  • Payments not attempted due to lack of a payment instrument (expired cc),
  • should still increase the attempts on the invoice.
  • Fixed currency symbol/code mixup.
  • Changing an credit card should invalidate pre­authorizations.
  • Added an 'integer' version of getQuantity, to simplify rule writing
  • Blacklist: Fails payments for users that are present in a list of known bad credit
  • cards.