Home → Support Center → Change Logs → CN!Express CX-6000SU Change Logs

CN!Express CX-6000 Single User

Change log for CN!Express CX-6000 Single User application.

19 January 2006 Version 3.38.5.1

Corrected range-check error in third-party database code. Problem is related to large databases over 200 MBytes. This problem has been reported in other software using this database -- not CN!Express Single User -- since it is exceedingly rare that a CN!Express Single User database grows to this size.

Found problem in ASTA communications compression algorithm used to communicate between the two portions of CN!Express). Addressed by turning compression off. This compression problem is data-specific.

Comment fields now accept up to 128 characters.
A user's permission to enter a refund transaction is now separate from the user's ability to process the transaction. The Privilege Settings tab on the Edit User dialog now has both 'Allow Refund' and 'Allow Refund Processing' checkboxes. Both boxes are unchecked by default when a new user is defined.

Minor update to the Paymentech Orbital Gateway. Now, if we receive a blank response from the Orbital Gateway, we automatically retry the transaction one time. Paymentech sees this as a duplicate transaction and returns the data that is already in their cache.
Fixed problem updating two-year old databases. After update, field that should be a float was still a BCD.
Improved archiving speed.

The Paymentech Orbital Gateway has started to occasionally return a blank HTTP response. The response itself is labeled as valid, but there is nothing in it. When this occured, the CN!Express Single User interpreted this as an 'invalid' response and incremented an internal counter used to support duplicate detection. As a result, when the transaction was resubmitted, Paymentech did not detect this as a duplicate. Now, when this condition occurs, the internal counter is not incremented. Resubmitting the failed transaction is seen as a duplicate by Paymentech and processed properly.
The problem with the Orbital Gateway returning blank responses has been reported to Paymentech.
This version has been tested under Windows XP Service Pack 2.

Address Verification (AVS) information was being sent in two different branches of the Orbital Gateway XML specification. This confused the Gateway and resulted in higher Interchange rates.
Checks can now be sent to Paymentech without full address information. NOTE: Full address information is still required for proper check processing.
Report by Credit Card type was not recognizing credit cards that had non-numeric characters.

Correct problem where special characters such as & and < were not being properly 'escaped' when written to the XML. This would cause a failure when checking the XML before sending it to processor.
Allow ability to edit the Order Number on Refunds.
Corrected faulty totals in reports by card type.
Address now defaults to Billing section.
Resize 'Confirm Void' dialog.
Prevent archiving to future date.
Remove ACH from filter choices in Tender Type
System Setup now allows user to set next generated Order Number.
Corrected sporadic problem with manually closing batches.
Corrected problems with multi-currency reports.
Fixed report summation and filtering problems.
Checks were printing as 'unknown card type' in reports. Now properly identified as checks.

Comment 1 and 2 fields now available on main data entry screen.
Under Processor Settings, you can set whether or not you want Comment 1 to be sent to the processor. NOTE: This is processor dependent--not all processors support this ability. If transmitted, this is simply a comment for tracking in processor reports. Comment does not appear on customers bill.
Added two new reports: Flagged Records and Flagged Records with Currency Breakdown.
Fixed timeout bug where default timeout for server-side was 1 second vs 70 seconds shown on client side. Problem occurs during clean installation.
Improved handling of retry warning header.
Minor modifications of XML document submitted for full voids.
Fixed account number verification bug related to truncated account numbers in database.
Removed automatic retries on timeout failure.
Corrected sporadic import problem in client/server communications where import fields would be improperly cleared.
Ability to archive active as well as completed transactions.
Ability to allow specific users to archive, vs just administrator.
Improved handling of data entry for expired or bad expiration date entry field.
No longer able to enter negative values in Amount field.
Ability to enter next auto-generated Order Number in System Setup.
Corrected problem with date filters where > would equate to >=

CN!Express is proud to be the first product to be certified for the new Paymentech Orbital Retry/Duplication Detection functionality. (Version 1.00 dated Feb 26, 2003)
TrustCommerce certification is complete.
Documentation for all fields (per Processor) is available on-line through the help menu.
Support HTTPS Proxy Servers that require UserID/Password authentication.
Creating a refund for a previous Purchase Card Level II transaction now copies the tax field to the new refund transaction.
Various UI and code-review improvements.
General improvements in multi-threading.

Found problem in ASTA communications compression algorithm. Turned off compression between CN!Express client and CN!Express Server. This problem was sensitive to the precise datastream delivered.