2021-11 Release Notes
Iteration: 2021-11
September 10th, 2021
Index
Whats New?
| ¯\_(ツ)_/¯ | Rejected Enrollments: Added received date column. |
Improvements
| 4635 | Better error messages for Reset Password functionality. |
| 4558 | Updated ESG Datamart to Release 7. |
| 4583 | Drop Reason Code no longer mandatory for Texas Market. |
| 4602 | Limited the credit check date of birth selection to a minimum age of 18 years. |
| 4619 | Added disclosure for Door To Door Sales. |
| 4625 | Slight My Account presentation improvements. |
| ¯\_(ツ)_/¯ | Added configuration to indicate the maximum amount of database backups to be stored. |
| ¯\_(ツ)_/¯ | Repositioned cancellation fee value in Quick Enrollments. |
Fixes
| 4556, 4584 | Multiple fixes and adjustments to prevent deposits without an associated enrollment. |
| 4620 | After updating the My Account preferences, the customer is logged out. |
| 4628 | Failed to import drops from ECI when an LDC has more than one associated enrollment. |
| 4616 | ECI Renewals have the contract dates switched. |
| 4642 | Error trying to enroll an existing LDC with a different utility. |
| 4562 | PPUs made from the Call Center assigned the old enrollment Id instead of the new one, making it look as if they were duplicated. |
| 4586 | Service task error trying to make the renewal switch. |
| ¯\_(ツ)_/¯ | My account shows multiple incorrect documents. |
Features & Fixes Details
Multiple fixes and adjustments to prevent deposits without an associated enrollment
There is an edge case when the enrollment is saved, in which after the deposit payment has been processed, the enrollment wouldn’t be stored if there was an error sending an email.
Several adjustments have been made to prevent this, but if this situation repeats in the future, when the enrollment isn’t stored, the system will log the situation so an agent can perform the refund using the payment vendor site.
Initially we planned to solve this problem automatically, by making OpsAdmin make the refund, but we found out that iCheck allows refunding the same payment more than once, and in order to prevent any problem with duplicated refunds, we decided to make this a manual process.
Another fixed issue associated with this bug is that a payment profile for the customer username was generated and never used since the enrollment was never created; this led to conflicts when trying to use the same username with other customers.