2021-15 Release Notes
Iteration: 2021-15
December 22nd, 2021
Whats New?
| 4434 | Setup more than two renewal notifications. |
| 4440 | Setup contract start notifications. |
| \(＾▽＾)/ | Global Price Changes updated to 2.0 UI. |
Improvements
| 4745 | Adjusted Transfer Of Service to inform Move In as Enroll Type and no Special Meter Read Date. |
| \(＾▽＾)/ | Massive database restructure for increased performance and reduced system requirements. |
| ¯\_(ツ)_/¯ | Improved service tasks performance to prevent situations in which the task would crash if it ran for too long. |
| ¯\_(ツ)_/¯ | Better returned information for Door To Door API method. |
| ¯\_(ツ)_/¯ | Removed unused Market Manager fields. |
Fixes
| 4741 | Error when saving document bundles. |
| 4780 | Can’t process iCheck payment when System Setup is configured to capture payments in a second step. |
| 4768 | Price Plan Updated ignores Full Plan Price Reasign and Edit Customer Plan Info roles, hiding older plan versions when they should be visible. |
| 4769 | Error when trying to complete a Door To Door sale without the date of birth. |
| 4747 | Several fixes to prevent errors when storing the credit card and processing the payment in iCheck. |
Features & Fixes Details
Setup more than two renewal notifications
Currently, OpsAdmin only allows a maximum of two renewal notifications to be sent to customers prior to their contract expiration. Since the Texas Market requires a third notification to be sent as well, this release includes a new feature that will give the user the possibility to set up as many notifications as needed to satisfy the requirements of Texas and any other market. To accomplish this, several changes were made to the OpsAdmin UI.
The renewal notification settings under Market Manager have been removed. Now, under the Autoresponder Package interface, when the Renewal Notification trigger is selected, the user can set a number of days in advance for this notification to be triggered as many times as needed. For example, the same autoresponder can be sent 15, 20, 30 days before the contract expiration date arrives.
The renewal notices UI has been improved to display this new adjustment.
The existing Autoresponder configuration has been migrated. The autoresponders have the day's value configured based on the market old configuration. Also, since the amount of notifications is variable, both the old log triggers and old autoresponder triggers have been replaced with a single log trigger and autoresponder trigger.
Setup contract start notifications
This new feature allows sending notifications to customers before their contract starts, as opposed to existing renewal notifications where the correspondence is sent based on the contract end date. The trigger “Contract Start Date Notification” should be used to create autoresponder packages and autoresponders to send correspondence to customers before the arrival of their contract start date. As Renewal Notices, this trigger also allows sending multiple notifications.
Global Price Changes updated to 2.0 UI
The Global Price Changes interface has been updated to match OpsAdmin 2.0 UI style
Massive database restructure for increased performance and reduced system requirements
Once again there is a big under the hood change for OpsAdmin. In this release it has been optimized how the plan data is stored in the database. Because plans are related with most of OpsAdmin features, this change will help in the stability and performance of the system with tasks like document management or plan versioning. These processes are incredibly taxing for the system, with extreme cases that could take up to an hour and now should require just a few minutes.