Orders intended to disconnect both child and parent services would sometimes disconnect the parent service prematurely. This occurred on Orders where:
child services were to be disconnected immediately and the parent service was to be disconnected at a later date (e.g. end of month).
The parent and child services had different service types, and the Workflow had sub workflows that split on service type.
The child service type Workflow was adding disconnect records for all child services and for the parent (where it should have added just a placeholder for the parent). Then when the parent service type Workflow was processed it added a second disconnect record for the already disconnected parent service.
With this solution, the child service type Workflow now adds a placeholder for the parent service rather than a disconnect record so as not to disconnect the parent prematurely. The parent is properly disconnected by the parent service type Workflow.
83417
Removed Boolean IsAccountLevelReadOnly key from database of OrderSummary OData, where it was accidentally left in after being automatically added in a past change.
Customer Care
83389
This PR is related to AR 8308 – Notifications for expiring credit cards (CostGuard 19.7). Two separate issues were resolved under this PR:
The Odata created to identify and filter out E-Pay accounts with expiring credit cards was sometimes unable to get through the full list of accounts. The Odata was making two separate calls – one to gather the list of accounts and one to get account information for filtering. The Odata now performs both functions in a single call. The improved efficiency enables it to run through the full list of accounts.
The code reversed the settings for months in advance to notify and months after expiration to notify. These settings now properly perform their respective functions.
Payment Gateway Application
83430
Azure changes to TLS protocol caused an outage in the PGA and required IDI to make an update. This PR updated the PGA to connect to Azure search service using TLS 1.2.
E-Pay
OnlineBill & Customer Web Service
83399
When using Authorize.Net in the PCI 3.0 configuration (Iframe), E-Pay Accounts created through OnlineBill had an expiration date set for the first of the month. This was causing payments for those cards to fail because they were showing as expired when they should have been valid until the end of the month. The Payment Gateway Application has been updated to set the expiration date to last day of the month to prevent this.
Note: The Customer Web Service does not automatically set the expiration date to the end of the month, so any accounts created this way should have the dates explicitly set to the end of the month as needed.
Address Validation
83383
Removed an Address Validation web service that skipped address validation based on country. Now all addresses are validated regardless of the country value.
83416
When a POS order used a taxable address based on the shipping contact, and that address was validated using the Address Validation Mgmt web service, the returned tax state was not being saved in the address validation result, causing sales tax for the POS order to be incorrectly calculated. The returned tax state is now saved so that sales taxes can be correctly calculated.
Bulk Data Feature Import
83410
Attempting to add more than 20 features sometimes failed with an error indicating the request size is too large. Bulk feature import has been modified to send batches of no more than 20 features at a time.
Notes:
This only applies to add feature imports (not modify).
This PR is in the CostGuard bundle and requires customers to take 20.3.
RateBill
83380
Prebill invoices were not being deleted for customers who were changed to billing inactive after a prebill run, and prebill results were improperly being included in actual billing XML and PDF. This solution updates Billing to properly delete all prebill invoices for the bill period as part the actual bill run.
83382
The General Ledger usage query was updated to get usage data from the UsageRecord and UsageRate tables rather than the usage view. This makes the query faster and helps avoid time outs.
83387
Billing logic has been updated so that a loyalty discount set up to apply only to the first month will not discount again on the second month. This occurred when a loyalty discount was added the last day of a 31-day bill period, and the discount was set up to only apply to the first bill period after the discount was added.
83397
FR 3142 (CostGuard 20.1) changed how the percent for proration is calculated to be accurate month to month; however, the calculation was not accounting for different charge cycles. The proration logic has been updated to use the correct number of days based on the month of the charge. Note: This PR has been removed as of release 20.3 R2.
83419
An AR introduced an issue causing Account Posting to fail. The AR required database changes related to default handling of payment Create Date. These changes conflicted with Account Posting default logic for Create Date and caused Account Posting to fail. This PR syncs default Create Date logic so Account Posting no longer fails.
Workflow
83396
Error Saving a Lot of Additional User-Defined Extended Data – Updated the Workflow page for adding extended data under the Additional User-Defined section to allow an unlimited number of extended data items. Note: This was only an issue if the amount of user-defined extended data exceeded 490 items.
