IDI Platform Version 24.3 Details

Customer Management – CostGuard Client

84559

Usage Summary Other Charge & Total Charge show doubleamount

In CostGuard Client when you view usage details for an invoice (by right-clicking on Usage Total) the usage summary query was summing the wrong columns from Toll, Other, and Total Charges. Consequently, amounts for Other Charge and Total Charge on the usage summary Wireless Usage tab showed double the actual amount listed in the invoice usage total. This was due to how the amounts were summed.

The query has been fixed to calculate and display the correct amounts.

Orders

84468

Potential issue when reconnecting an AdvancePayproduct

Under certain (rare) circumstances, reconnecting an AdvancePay product could result in attempting to reconnect a different customer’s products and cause xml generation/billing errors downstream. This was ocurring only when making these selections in the Reconnect wizard:

• Reconnect these services and all children and

• Reconnect final billed items

This has been fixed.

Orders

84591

Do not auto-delete signed service agreement on order updates

With Web Sales FR 3412 provided in CostGuard version 23.12, when an order is modified, signed service agreements are deleted to account for changes in the order that may affect the agreement.

Now you can choose to not automatically delete agreements based on a new document template property. The property defaults to False – not automatically delete signed agreements at checkout. This behavior can be changed on a service agreement basis (to have an agreement by submitting a service request to update the document template.

Orders

84594

E911 Class and Type of Service not auto-populating when updating an existing E911service

Enhancements to E911 functionality provided with FR 3463 in CostGuard version 23.11 let you populate values for E911 Class of Service and E911 Type of Service as set on the order rather than use defaults as set for the service type in the CostGuard Client Product Catalog. This PR fixes two issues related to this functionality:

• When an existing service whose service type is configured in the CostGuard Client Product Catalog to Enable E911 Support is automatically staged on an order (for example when adding a feature or starting the order through the web API and then finishing the order in the Orders web module), those values should be auto-populated as they had been set when the service was originally added; however, this was not occurring. Consequently, the order would fail to complete. This has been corrected to pull in E911 Class of Service and E911 Type of Service values from the service as they had previously been set.

• When a service that does not support E911 and has at least one service address with either an MSAG Community or MSAG County is Billing Service Updated, the first service address with MSAG values on the service was being designated as the E911 address. This has been fixed to not designate the address as E911.

Payment Processing – Paymentus

84596

Paymentusrestrtictions limit ability to handle some payment codes

Payments coming in from Paymentus were restricted be one of the Payment Type Codes registered to that customer. This can cause issues when the payment type codes associated to that customer changes.

These restrictions have been removed so the system can handle any Payment Type Code sent from Paymentus regardless of the initial Payment Type Code associated with the customer.

Payment Processing

84604

Create recurring transactions job not updating statuscorrectly

The create recurring transactions process was not setting the bill period status to Partial when transactions were created and there was also a future dated due date for transactions that had not yet completed.

This has been fixed by updating the logic to set the status to Partial when not all transactions are created.

Usage Processing

84589

Unable to Parse PGW records with VoWiFiCalling

An error was occurring when attempting to parse PGW records that contained new VoWiFi calling. This was due to an incomplete definition file that was not incorporating all defined fields for PGW. The definition file has been updated to include all necessary defined fields. This ensures the PGW records are parsed as intended.

Usage Processing

84592

International roaming calls were mistaken as international calls

The originating and terminating numbers were not being properly set when making International Roaming Calls. This was due to the logic used for the country codes.

The logic has been updated to set the originating and terminating numbers properly for International Roaming Calls.

Customer Management – E911

84606

Missing header and trailer on E911 file export

The E911 file export previously would not write header and trailer records for all file formats.

The E911 export has been updated to create files with the header and trailer records for all current formats