Corporate Hierarchy display enhancements – On the Corporate Hierarchy view on the Invoice page, the heading My New Charges has been changed to My Charges. The My Charges value will only represent the new charges on the invoice for the customer being viewed. It will not contain any charges for child accounts. (Previously this included child charges when corporate roll-up was done on the invoice). In addition, informational text has been added to the My Charges and Corporate Charges headings.
Orders
FR 2853
Wireless service order enhancements – Enhancements in the Order Details pane where you can view and edit order item details for a wireless service let you:
Mark the service as primary
Determine which services on the account will receive usage notifications
View and edit equipment details
Tickets
FR 3092
Allow resolution note to be edited – Previously, you were only able to edit the resolution note on changing the ticket status. Now you can edit the resolution note anytime one is present.
Workflow
FR 3024
Search for triggers based on System-Defined or User-Defined – The Trigger search page now supports filtering of user-defined versus system-defined triggers. System-defined triggers are not displayed by default but can be displayed by changing the new Type option in the search criteria. When viewing a system-defined trigger, a System Defined label is displayed.
FR 3092
Added Datalook up for customer attributes by key and by name.
Customer Management
FR 2744
Managing Service Agreements – Lets authorized users edit parts of Service Agreements directly in the Client without requiring an AR. Areas that can be edited are: Title, Acknowledgment (Financial Responsibility) and Terms and Conditions.
AR 8491
Contact management enhancementson services – When editing a service in Customer Management, the selected Contact will display at the top of the Contact Field on the Contact Information tab. The drop down sorts contacts alphabetically by Display Name, which includes MI, Last Name, Company Name, and Address if available. This accounts for scenarios where the first or last name are not provided as they are not required fields.
Treatment
AR 8527
Fire Collections Information Modified trigger on collections workbook updates – With this enhancement, changes to collections information that occur when the workbook runs will fire the Collections Information Modified trigger. Previously this trigger would only fire when changes were made through the Web API.
Product Catalog
FR 3086
Product Catalog configuration supports taxes for Dynamic Charges and Contract Penalties (new Taxes tab on the Add/Edit dialog).
RateBill
AR 8446
New monthly billing cutoff option for In Advance – No Prorate products – A new Customer Care setting provides alterative billing cutoff logic to ensure transactions for Products and Packages with Prorating Type = In Advance – No Prorate are billed within the bill period in which they occur, regardless of when billing is run.
Note: The setting defaults to disabled. This will result in no impact on billing for these Products/Packages (current functionality is maintained).
RateBill
AR 8497
Use Grace Period End setting for account-level grant discounts – When an account-level discount is disconnected on the same day the customer is disconnected, and the Grant Discount Ignore End Grace Days setting is OFF, the Grace Period End setting is applied to the discount, pushing the end date out by the specified number of days. This allows usage to use the discount for this extended time. (These are Console Configuration settings that must be set by an authorized IDI associate.)
Grace will not be applied when a discount has been disconnected in a previous billing period and the discount does not have units in the current period, since the discount will not be loaded.
Note: Previously, this functionality only applied to service-level grant discounts.
Payment Processing
AR 8530
Added Payment Return Reason to Customer Care & Client – Updated ACH Return File Import to capture the Payment Reversal Reason from the import in the Description field on Payment Reversal in the system.
Resolved Known Issues
Functional Area
PR
Description
RateBill
83217
Updated Rate Plan Detail entry to prevent adding duplicate entries (same distance type).
OnlineBill
83200
The OnlineBill User Import screen that lists domains just shows the domain description, if the domain has no description a null would be displayed. This was updated to show <Description> (<Name>) if a description is populated, If one is not populated, just the <Name> of the domain is shown.
83234
Resolved an issue where Hyperlink Attributes were not displaying correctly for billing orders in Customer Care.
Payment Gateway
83149
Long-Running PCI Payment Gateway Transaction Processing Job – Created a thread-monotoring process to ensure a single thread doesn’t run for longer than a specified time. The time is hardcoded and not configurable.
83182
Credit card payment settled in Auth.net but has a processing error in Care:
Added additional logging to PCI Scheduled job to track all transactions it processes or tries to process. This is to see if the system is trying to process a transaction twice.
Added hash table check to ensure the system is not processing a transaction that was already processed or the system started to process.
83196
Fixed Back Dating of an Adjustment Reversal – Previously, when the Customer Web Service created an Adjustment Reversal via the modify Adjustment Operation, it set the adjustment date to the original adjustment date. Now the web service will set the adjustment date to the current date.
Workflow
83194
Updated the Add Note dialog in Workflow to check for Manage Workflow Instance.
83204
Fixed error handling for the following Workflow Actions: Web API, Update Billing Status, Create Ticket, Modify Follow-Up
Workflow tasks will only get set to Error if a web service error is returned with a logging message (non-correlation) OR some other action validation fails (ID does not exist).
If an action fails with either a correlation ID from a web service, or an otherwise unhandled exception, that exception will escape to the action so that it is retried.
83208
Updated graphing engine to correct drawing issues in Workflow Designer.
83230
Extended Data not Passing to Sub Workflow Properly – Fixed Splitter Subworkflow activation logic to correctly compute the extended information when doing replacement using @[SplitGrouping.MemberName].
Services – E911 Information
83229
Resolved some issues with E911 information being removed:
When adding a new service, if you edit the service from the order tree and then add a single service address:
If you do not click on the e911 tab, the service is created with the service address and the e911 address is set
If you do click on the e911 tab the service address is pre-selected in the dropdown and the service is created with your selection.
When adding a new service, if you edit the service from the order tree and then add a multiple service addresses:
If you do not click on the e911 tab, the service is created with the service address and the e911 address is set to the first service address entered
If you do click on the e911 tab, first service address entered is pre-selected in the dropdown and the service is created with your selection.
Edit Service that has no service addresses and no e911 address:
Add single service address don’t click the e911 tab – e911 address should be set to the service address entered
Add Single service address click the e911 tab – e911 address should be set to the service address entered
Add Multiple service addresses, the first entered service address should be saved/defaulted as the e911 service address
Edit a service that has a service address but no e911 address:
if there is 1 service address, go to the e911 tab and the one address should be selected in the dropdown
If there are more than one addresses, then going to the e911 tab will not have any pre-selected
Edit a service that has a service address and e911 address:
Add another service address, should get a confirmation prompt when saving to confirm that the e911 service address is correct.
Work Plans
83221
The Journal Grid Control applies user limit-tos when loading journals. Since the journals on a Work Plan are not associated to a customer, they were getting filtered out by the user limit-to logic. Now, journals on a work plan will not have limit-tos applied. If you are able to get to the work plan you will be able to see the journals on it.