Skip to main content

2024-09 Release Notes

Iteration: 2024-09​

August 5th, 2024

Improvements

6317 Automated generation of Customer’s Name Key
6356 Added validation for Service_State_Code column under Sales Importer (Only accepts USPS standard abbreviations)
\(＾▽＾)/ Improved LDC validation under Sales Importer.
\(＾▽＾)/ Improved email address validation message on quick enrollments.
\(＾▽＾)/ Added validation for maximum file size on Sales Importer.
\(＾▽＾)/ Performance improvements for Utility Charges UI.
\(＾▽＾)/ Performance improvements for Plans Manager.
\(＾▽＾)/ Performance and refactor improvements for Old Enrollment UI (System Logs).
\(＾▽＾)/ Performance and Refactor improvements for automated jobs that involve Renewals as well as PPUs.

Fixes

5671 \ 5673 Adjustments to enable using the same ESID for different customers
6210 Adjustments for the Linking Accounts functionality
6332 Fix for issue when attempting to unsubscribe an account from Autopay.
5614 Corrections under Customer Support to display the most recent confirmation number to agents, specially for scenarios where cancellations occur.
6359 Resolved bug that caused acceptance emails to be sent to customers when doing updates through Enrollment Details.
6380 Adjustment for error message at the time of saving TDSP Delivery Charges.
6314 Solved issue that prevented users from submitting enrollments to the billing system due to an incorrect autopay validation.
6343 Corrected conflict in autoresponder logic that triggered invalid communications.
6398 Adjusted automated renewals job that was submitting accounts to the wrong billing system.
6397 Updated error message on Sales Importer for missing recurring billing mandatory fields.
6393 Resolved inaccurate filtering functionality under System Logs.
6399 Correction for error message tied to Renewal notification logs.
6401 Solved defect that would cause renewals to be exported multiple times.
6413 Fix for “error creating a customer” message on Sales Importer.
6414 Sales Importer - Revamped email address validation.
6415 Solved “Account already exists” issue when updating an LDC on the Enrollment Details page.
6423 Adjustment for Renewal Notifications that were not displaying current plan data.
6199 Adjustment for automated job that mistakenly updated a dropped account to Accepted + Fix for System logs registry tied to this job.
¯\_(ツ)_/¯ Several corrections to automated username generation.
¯\_(ツ)_/¯ Corrected an issue when attempting to update enrollments whose username is an email address.
¯\_(ツ)_/¯ Adjusted automated job for winbacks export that would fail with an error message.
¯\_(ツ)_/¯ Fixed column display defect under System Logs.

Features & Fixes Details

Automated generation of Customer’s Name Key​

It is possible to have the customer’s name key automatically generated without having customers entering this value manually during the enrollment process with the possibility of making a mistake when entering the value.

For Residential Customers, the name key is generated with the first four characters of the last name. For Commercial customers, First four characters of the Firm Name.

Adjustments to enable using the same ESIID for different customers: Force Move Out​

A new setting can be found under Market Manager: Allow force move out. The purpose of this setting is to allow the scenario of the same ESIID for different customers, since in markets such as Texas, the ESIID is tied to an address and not to a customer, so it’s very common that the same ESIID is tied to different customers over a period of time.

The validation looks for the email address, phone number, firm name and first/last name (In this order).

This functionality affects the Web Enrollment Journey, Quick Enrollments, Winbacks. This is why these processes have been updated to enable these scenarios and some steps are now inverted.

Sales and Renewals importers were modified as well to cover these scenarios.

Other affected functionalities are the import rejection process, autoresponders, link accounts, customer manager as well as the API endpoint GetTransactionOptions.

Adjustments for the Linking Accounts functionality​

When attempting to use the Link Accounts functionality, the selected account from Customer Manager is now the **destination **account, and the account selected from the Link Account interface is the source account. This is an important improvement because in the past, users could not select an account without enrollments as the destination, making it impossible to revert or unlink accounts.