CostGuard Version 21.5 Resolved Known Issues

CostGuard web modules use time zone and daylight savings (DST) data in a third party library to calculate dates and times. The data in this library was only valid through 2020. Once the first DST shift in 2021 occurred various times were displaying as off by one hour. This PR resolved the issue by updating the third party library to have current DST data to correctly take into account daylight savings time.

The following areas were known to have issues with time/date time stamps:

• Customer Care
  • Journals & Follow-ups
  • E-Pay transactions
  • Billing tab posting and transaction date information
• Trouble Tickets information (open dates, close dates, etc.)

These areas had the potential of being impacted (suspected but not observed):

• Order Information – Order History bill order date, complete date
• Customer Care Orders > Retail History time stamps
• Equipment Inventory time/date stamps

On attempting to test CostGuard’s automatic E-Pay retry functionality, the recurring triggers were not running as expected in some cases. These recurring triggers were encountering an object reference error that was traced back to a time zone issue. The recurring triggers were not properly handling cases when the time zone and offset created a positive value.

This solution was originally provided in CostGuard version 21.4 to correct this functionality in Communications. With CostGuard version 21.5 this has been corrected in Customer Care as well. The OData used to get the recurring triggers has been updated to handle the positive time zone offset values.

When using the Set Start Date workflow action, the Contract End Date was not auto-updating after the Start Date had been reset. For example, if a Start Date was updated to one month later, the End Date should automatically be pushed out, as well (to match the Contract duration since the Start Date), but this wasn’t happening.

Orders now matches CostGuard Client functionality to correctly update End date.

This issue is related to workflow-based provisioning orders where users are attempting to edit a list-based POD property. If the list contained more than 100 items, only the first 100 items were available for selection in the list.

This has been corrected to properly search and return all items in the list.

When returning a retail item in the Orders web app originally sold under a service, the return incorrectly put the item at the account level.

The system now finds missing service order line item information and correctly returns the item at the service level..

• |Communications DLM| Archive messages associated to disconnected customers
• |Communications DLM| Archive messages associated to closed tickets
• |Communications DLM| Archive messages associated to completed workflows
• |Communications DLM| Archive unlinked messages

In systems where these triggers did not exist, the data installer file would run, see that the triggers were missing, and install them. To address the performance issue IDI Support has been working with customers to disable them.

With this PR, the data installer no longer installs the triggers if they’re missing.

If a provisioning request gets an error from Calix – the error message returned in the XML, does not match the error message in the UI.There was a problem with how errors were passed from a message up to the provisioning request which lead to an incorrect error message. The returned error message was not applicable to the actual error message from the switch. This has been resolved by returning the switch error is being.

This issue is related to workflow-based provisioning orders where users are attempting to edit a list-based POD property. If the list contained more than 100 items, only the first 100 items were available for selection in the list.

This has been corrected to properly search and return all items in the list.

An FK error iocurred on deleting a service from a cart that had its Provisioning Object Definition (POD) data changed. This has been corrected.

Adding a new service for MetaSwitch and Calix services requires a password that is used to connect the two providers. The password format has new minimum requirements to make passords complex and minimize security/fraud exposure risks:

• Minimum length = 12 characters
• Must Include at least:
  • 1 Capital letter
  • 1 lower case letter
  • 1 number
  • 1 special character

This was corrected to store a default SIMClassID value of 3 (SIM Card) when not defined.

After signing onto their account an OnlineBill, a customer was able to access the account for another customer.

To prevent this, a check has been added on the OnlineBill main landing page. If the check finds the user is logged in as OnlineBill system user rather than their actual user account they are logged out and required to log back into OnlineBill. Note: This issue has not been found to occur frequently and is not reproducible, so the impact on users should be minimal .

Dynamic charges set up to calculate a fee that is a percentage of the total charges for contributing products did not take into account any credit amounts for the contributing products. This resulted in the dynamic charge (calculated at the time billing) to be higher than expected.

The logic for Dynamic Charges configured as Tier Units = Currency and Amount Type = Percent has been updated to include negative charge amounts when calculating contributing product amounts.

The Admin Console > Data Management > Parse Lookup screen was preventing users from inserting entries with the same FileFormat and Lookup String values.

The Parse Lookup page has been updated to allow for FileFormat, Keyname, and LookupString as the unique key.