CostGuard Version 22.2 Details

Adobe Acrobat Reader must be installed on the local workstation to support viewing applicable PDF documents in the CostGuard Client. Prior to this solution, the client required a specific executable named AcroRd32.exe. In August 2021, Adobe released the 64-bit version of the Acrobat Reader with a different executable name: Acrobat.exe. If users upgraded to the 64-bit version they would incur errors when attempting to generate and display PDFs including Service Agreement (per a Contract) in a Sale, Installment Plan Agreement in a Sale, and Payment Statements.

With this solution, instead of opening PDFs using a specific executable name, the system will now open them with the associated system-default handler for the PDF file type. This has the benefit of not being dependent on a specific executable name which could change over time, and leverages the system-default handler rather than requiring a specific software program.

In CostGuard Client, submitting a swap equipment order without actually changing the handset or SIM ID correctly results in an error; however, submitting the same order in Customer Care did not result in an error.

The Order Placement web service validation was updated to bring it in line with CostGuard Client validation such that an error is now thrown in Care if the Handset ID or SIM Card ID have not changed and the order is prevented from being submitted.

In Customer Care adding more than 70 extended exemptions caused an error. The error stated that the JSON request was too large to be deserialized. The default query limits for this object was too small.

The limit has been increased to 250,000.

When listing information for file attachments in Customer Care, the value for the file size was incorrectly displayed. The value was not converted correctly to the proper units for display. This occurred in the grid on the Resources tab of the MANAGE > Sales Associate Configuration page.

This was also an issue for customers using Document Storage in Customer Care. Files displayed from the Documents menu item displayed the incorrect size in the grid.

Customer Care has been updated to correctly display the file size on these pages.

In CostGuard Client, errors on orders related to a parent (root) order roll up and show the parent in an errored state; however, this was not the case when viewing orders in Customer Care.

This has been corrected so that the errored count on descendants roll up to their parent to show the correct state of the order.

This PR addresses some performance and display issues for Web Sales functionality delivered in FR 3410 (Milestone 1 released with CostGuard version 22.1).

The following error occurred on finalizing an order: Violation of UNIQUE KEY constraint ‘AddressValidationTaxJurisdictionLink_AK’. Cannot insert duplicate key in object ‘dbo.AddressValidationTaxJurisdictionLink’. The duplicate key value is (1174431, 39507).The statement has been terminated.

This was happening when multiple contacts were being updated at once (due to splitters, sub workflows, etc); The code was updated to help prevent simultaneous contact updates from stopping orders.

When processing of Recurring E-Pay transaction files, some files showed a Partial status. The queries used to determine which invoices needed a transaction to be created were not performing efficiently. The queries were running for a long time and seemed to pull excess information, which led to timeouts.

These queries have been optimized. With the optimizations the files should complete and not be left in a Partial status.

This issue is isolated and only occurs for a corporate invoice-responsible (IR) account that has both a non-invoice-responsible (NIR) child and grandchild, where the child NIR account is set up as billing inactive. In this case, the NIR grandchild that is under the billing inactive account is not included in the XML for the IR account at all. The new charges for the missing account are also not included in the total New Charges amount for the invoice. In this case Total Amount Due in the XML is correct, but the Balance Forward + New Charges will not be equal to Total Amount Due.

CostGuard has been updated so that invoice XML is correctly generated to include all NIR charges for a corporate IR account in this scenario.

An issue was experienced when an account with an outstanding balance was moved into a corporate account structure as a non-invoice responsible (NIR) account when Total Rollup is enable for the CostGuard environment. A payment made by the invoice-responsible (IR) parent account was incorrectly allocated to the NIR child account balance, causing the IR account to appear past due. Because the NIR balance will roll up to the IR parent account the next time the corporate structure is billed, all payments should apply to the IR parent’s balance.

Costguard has been updated to correctly allocate payments to the IR parent account when a balance exists on an NIR child account and Total Rollup is enabled.

Customers with products that bill more than one cycle in-advance did not have their in-advance charges (after the first month) contribute to the total evaluated amount. This negatively impacted minimum guarantee contracts. It resulted in a lower total evaluated amount which could increase the contract penalty for that customer if it caused them to fall under their contract’s minimum guarantee currency.

The Billing operation was updated to keep track of in-advance charges more accurately.

The Wireless Minutes Summary and Wireless Discount Summary XML invoice optional reports were missing the primary number indicator for discounts that share based on associated SKU.

The XML optional reports were updated to show the primary number for grant discounts configured to be share based on associated SKU.

The protection plan screen (AR8795, released in CG 21.7) was using an incorrect date format, resulting in the activation date defaulting to one day later than it should when the user is in GMT.

This has been fixed to default correctly in this case.

This PR addresses two issues related to permissions in OnlineBill:

The user administration page in OnlineBill is accessible to users with either OnlineBill\Admin or OnlineBill\Impersonate permissions. However, the page was only honoring the OnlineBill\Impersonate permission and users with the OnlineBill\Admin permission were being logged off and were not able to access the page.

This was corrected such that users with either permission can access the page.

Also there are areas in OnlineBill that require both an OnlineBill permission and a corresponding Security web application permission. In some cases OnlineBill was not checking that users had the corresponding Security permission, which would result in an authentication error.

This was fixed for the following areas in OnlineBill to give a better user experience when using custom roles:

Unblocking users: Requires OnlineBill\Admin AND Security/Company Management/Manage Users

Impersonate – Requires OnlineBill\Impersonate AND Security/Company Management/View users OR Security/Company Management/manage users

Change PWD – Requires OnlineBill\Admin AND Security/Company Management/manage users

Unlock – Requires OnlineBill\Admin AND Security/Company Management/manage users

Edit Notification – OnlineBill\Admin AND Security/Company Management/manage users