CostGuard Version 19.12 Core Release Bulletin
Change Orders:
Functional Area | AR/FR | Description |
|---|---|---|
Payments/Refunds | AR 8519 | E-Pay payment and credit card refund enhancements:
|
Product Catalog – Grant Discounts | FR 3119 | Serving PMN criterion for grant discounts – Lets GSM wireless providers discount roaming traffic served on a specified Partner Network. Note: The system already supported Serving SID in grant discounting for CDMA wireless providers. This enhancement provides the same grant discounting option for GSM wireless providers. |
POS – Coverage Service Area (CSA) Check | AR 8533 | New APIs and support for updating the CSA table via Bulk Data web app New APIs:
For more on CSA APIs, see Web API Documentation for Service and Feature Management Service under Developer Support in the IDI Knowledge Center. For more on CSA update via Bulk Data app, see the knowledge article on Bulk Data Module, and the Bulk Data Specification for CSA Table Update. |
Orders | FR 3056 | Direct Invoicing Incremental Enhancements:
|
Configurable Terms & Conditions | FR 3121 | Resolved unique name issue when making multiple copies – When you make a copy of an agreement, the system adds Copy of to the name to make it unique; however, this only worked for the first copy. If you attempted to make another copy of the original service agreement, the system would simply add Copy of again resulting in a unique naming error. Now the system adds a sequential number to the end of the name to enforce the unique naming convention. The system allows up to 100 copies before forcing a new name to be entered. |
Resolved Known Issues
Functional Area | PR | Description |
|---|---|---|
Customer Care | 83238 | The Customer Web Service was firing Workflow triggers twice on a Modify Customer action when paymentAccount logs were provided on the request. The triggers would fire when the customer information was saved, and then again when payment logs were saved. Because the payment logs need the customer information to be saved first, the set of triggers to be fired will now be cleared after the customer information is saved. This prevents the triggers from being fired again. To test, modify a customer through the Customer Web Service(for example, add an E-Pay account) and include the paymentAccount logs (property on the Modify Customer call). Then check in Workflow to confirm the triggers only fire once. |
83279 | Updated Customer Care to display most recent Payment Date (instead of the highest Payment ID) for Last Payment on the Account Summary page. | |
83295 | Updated Customer Care to successfully open an Invoice that has more than 99 disputes. | |
Retail Installment Plans | 82809 | In the following exchange scenarios, the Future Installment tender type was not being applied correctly, resulting in General Ledger system errors: Installments fully paid on return item, no installment plan on new item Installments partially paid on return item, installment plan on new item No installments paid on return item, installment plan on new item Now, in the above scenarios the Future Installment tender type is correctedly applied, and General Ledger journal entries correctly balance with no system errors. |
RateBill | 83277 | Production Incollect Transfer Batch files failed to process when the file’s sequence number had also been used on a test file. The system no longer includes test files in sequence number checks to ensure production files no longer fail for this reason. |
83322 | Cost on usage file – Fixed WL2 Parser to pull Cost from CDRs as a 6 (not 4) decimal place value | |
Address Validation | 83310 | Core Logic validations were failing under certain circumstances. Now, if a validation fails at Core Logic (other than for invalid credentials), the system will use USPS validation. |
OnlineBill | 83289 | Previously, when making a payment in OnlineBill and after the successful transaction, users couldn’t preview the PDF receipt when clicking the PRINT RECEIPT button. Instead they would see a white screen on the page. This was due to not passing receipt or cart information to the final step of the process. This information is required for receipt operations and so receipts could not be printed. This solution ensures the required information is passed to the final step of the process so that the receipt operation can print them. |
83294 | There was a need to facilitate state code entry, and add GU (Guam) and MP (Northern Mariana Islands) to the state list – OnlineBill users are required to enter their state in the Authorize.Net payment iframe. OnlineBill validates the gateway response to ensure the State value is two characters (as required by CostGuard). The iframe does not enforce this requirement. If a full state name is entered, OnlineBill displays the Invalid Address Information dialog that lets users select a two-character state code from a drop down menu and enter their zip-code. Prior to this solution, the list of states was hard-coded and did not include GU or MP. This solution updates this dialog to use the Tax State table which is kept current and includes GU and MP. As the Tax State table requires a Country value, this field has been added to the dialog. The Country field defaults to the value configured in the Manage Contacts – Default Country setting in OnlineBill.
This solution also enhances the flow to let users avoid the Invalid State dialog if an exact match for state name in the default country is entered in the iframe (e.g. New York, instead of NY). CostGuard will auto-match and replace New York with NY and let validation proceed as usual. This solution also resolves a display issue with the credit card image for Japanese Credit Bureau (JCB). |
Platform System Deployment Updates:
Module | Target Deployment Updates |
|---|---|
Payment Gateway Application | 12/09/2019 |
.png?sv=2026-02-06&spr=https&st=2026-08-05T23%3A55%3A28Z&se=2026-08-06T00%3A10%3A28Z&sr=c&sp=r&sig=pNgabJX8g%2FCyBF5VwkM0yx%2BMQUeaX1ilJZsk8UFiQ2E%3D)