Release Summary
Change Orders/Enhancements
The following change orders and other enhancements are included in this release.
AR/FR | Description | |
|---|---|---|
Orders Web Module | FR 3780 | Effective date enhancements for add/swap item transactions These enhancements facilitate setting the effective (start) date when adding or swapping an item on an existing service.
|
Orders Web Module | FR 3781 | Item availability and restriction rules based on Credit Class This is supported by a new optional Assignment Template selector when you configure Credit Classes in Admin Console Data Management. The selection will be observed during transaction assembly in web transactions. |
Orders Web Module | FR 3785 | Facilitate adding account-level Items This enhancement ensures account- level Items are listed and available for selection when Assignment Templates are applied, as long as no rules with Account Level Categories are configured to restrict them. Before this change, applying an Assignment Template without a Rule with an account-level Category prevented users from finding and adding account-level Items. |
RunCenter | FR 3705 | Usability Enhancements This release provides several feedback-driven improvements covering the Dashboard, Bill Cycle/Bill Period search, and the bill run process. Details are provided in What’s New in the RunCenter user guide. |
Resolved Known Issues
The following known issues have been resolved in this release.
PR | Description | |
|---|---|---|
Address Validation – Desktop Client | 85152 | Validation issue when Required Validation Type = None Required Address validation now properly handles cases where Required Validation Type is set to None Required. |
Address Validation – Desktop Client | 85160 | PO Box Validation Enhancements Improvements were made to more accurately define what qualifies as a PO Box. |
Core Reports | 85163 | Market Change Audit report error Sales Channel changes made through the Customer Management API were not being recorded in the audit history. This could cause the Report Explorer > Audit > Customers & Services > Market Change Audit report to fail with a validation error. Market changes are now correctly tracked, and the report runs successfully. |
Web Orders | 85178 | Assignment templates from Pricing Zones not being observed This fix ensures the system includes the Assignment Template from the Pricing Zone and correctly determines and enforces its rules. |
Customer Portal – Subscriber View | 85162 | Correct values presented under Plans & Services in Customer Portal The Plan card in Customer Portal > Plans & Services has been updated to show the correct monthly plan amount. |
Customer Portal – Subscriber View | 85192 | Proper handling of zip codes with more than 5 digits Self-registration no longer truncates postal codes to 5 characters. This update supports international postal code formats and preserves the full value entered by users. |
Billing Tax Calculator | 85165 | Enhancements This release adds:
|
Billing Tax Calculator | 85173 | New fields for exemptions The tax exempt fields have been added to the Tax Customer model to ensure tax-exempt customers are not erroneously displaying taxes. |
Provisioning | 85166 | Nokia AMS – Error on Add Service action Add Service provisioning actions will now use boolean true or false options that will be serialized as TRUE or FALSE. Note: This field must be capitalized to be recognized by Nokia. This will allow all provisioning actions to be submitted and processed as desired. |
Treatment & Credit Scoring | 85141 | Automated Write Off updating accounts before bill period is approved Automated write-offs now only check invoices from approved bill periods when determining if a customer has been billed since disconnect. |
Treatment & Credit Scoring | 85157 | AppleCare Disconnect error Fixed an issue where the system could fail to authorize a web service call for certain users. |
Service Address Management | 85184 | City/State missing on Service Address validated with Zip Code Fixed an issue where a new address could validate successfully using the Zip Code, without populating City/State values. |
Notifications | 85179 | OnlineBill Mailer incorrect due date The OnlineBill Mailer Wizard now uses the correct date and time, regardless of the user's time zone. |
Platform Application Target Deployment Dates
Module | Target Deployment Date |
Customer Portal | 09/08/2026 |
Provisioning - Nokia AMS | 09/16/2026 |
Facilitating Setting Effective (Start) Date on Add/Swap Item Transactions
Web add/swap item transactions now observe the related Product Catalog settings for Effective Date and When Contract is Sold. This applies to Contracts, Discounts, Dynamic Charges, Packages, Pricing Plans, Products, and AdvancePay Products.
Also, Orders Field Configuration lets you set Effective Date rules and restrict user groups that can modify the default value for add/swap transactions. Order Field configuration will apply when the item’s Effective Date is set to Default.
Note: This functionality only applies to existing services. It does not apply to a new service being added in a transaction.
Product Catalog Settings for Effective Date
Effective Date settings for a catalog item are specified on the Product Catalog Add/Edit form Behavior tab.
These options will apply for:
Adding an item to an existing service - When the selected option does not cause the removal of an existing item on that service due to exclusivity.
Swapping an item on an existing service – When the selected option causes an existing item on that service to be removed due to exclusivity.
Add On Effective and Swap On Effective Options
The Add On Effective Option and Swap On Effective Option selectors provide the same options:
Default | This sets the Effective Date according to the Order Field configuration. A selector is provided during transaction assembly to change the Effective Date as shown below.
|
Today | The Effective Date is automatically set to the current date and cannot be changed during transaction assembly. |
Back Date | The Effective Date is automatically set to the start of the current billing period and cannot be changed during transaction assembly. |
Forward Date | The Effective Date is automatically set to the start of the next billing period and cannot be changed during transaction assembly. |
When Contract Is Sold Settings
When a contract is added to the same service on the same transaction where an item is being added or swapped, you can use these settings to override the above settings and force the item Start Date to match the Contract Start Date. This applies regardless of which is added first, the contract or the item. Note: If more than one contract is added to the same service in the same order, the item will be updated to match the earliest Start Date of the newly added contracts.
The following message will appear in the top-right corner of the page either when a contract is added and one or more items are in the order configured to match contract Start Dates, or when an item is added that is configured to match contract start dates and one or more contracts are in the order.
Workflow Processing Considerations
Depending on workflow configuration, the Start Date set when the order is processed may be different than the time when the order is submitted. For example, if you submitted an order with Start Date = Today selected on August 1st, but the order isn’t processed by workflow until August 10th, the system will calculate Today at the time of processing, on August 10th and set the Start Date accordingly. This also applies when backdating to current bill period and forward-dating to a future bill period. Note: If you set the Start Date by selecting a specific date from the date selector, it will always be set to the selected date (not impacted by when the transaction is processed).
Examples:
Add Transaction, Exclusivity Not a Factor
Item Effective On Add = Back Date
Item Effective on Swap = Forward Date
In this example there is no other item in the same exclusive group as the item being added, so the Start Date is set to the start of the current bill period according to the item’s Effective On Add setting.
Swap Transaction Triggered by Exclusivity
In this example the same item as above is being swapped with an item in the same exclusive group that already exists on the service. In this case, the Start Date is set to the start of the next bill period according to the item’s Effective On Swap setting.
Set Start Date According to Order Field Configuration
In this example the item’s Effective on Add setting is set to Today.
Note: In all three examples above, Start Date cannot be changed, because these values are set in the Product Catalog.
Defaulting to value set by Order Field Configuration
When the item’s Effective On Add setting = Default, the Start Date is preset according to the Default value specified in Order Field Configuration. In this case, the value can be changed if the submitter has no restrictions.
Decision-making Hierarchy of parent-children items
When observing the configurations of items in a parent-child structure, some effective dates might apply differently, based on the scenario.
When an item with children below it is staged (but the children themselves are not manually staged), and the child items have an Add On/Swap Effective Date of Default, the children will inherit the start date value from the parent; if, however, the children are staged, they will look to the Order Field Configuration default value and preset to that, even if they are different from the parent item.
If children are configured with an Add On/Swap Effective Date of Today, Back Date, or Forward Date, they will be calculated separately of the parent item, regardless of if they’re staged or not, since these values cannot be modified.
Order Field Configuration
You can add fields for Feature Effective Date on Add and Feature Effective Date on Swap. Below shows both fields added.
When you edit either field you can set the default to Current Bill Period, Next Bill Period, or Today and restrict by User Group. Users in restricted user groups are not allowed to modify the applied OFC default value
Item Availability and Restriction Rules Based on Credit Class
This is supported by a new optional Assignment Template selector when you configure Credit Classes in Admin Console Data Management. The selection will be observed during transaction assembly in the Orders web application.
Facilitate Adding Account-level Items
When an Assignment Template with an account-level association (Account Type or Market) is applied to a transaction, items become available for account-level selection without requiring a rule that uses an account-level Browse Tag Category.
Example Account-level Browse Tag Category
Available Account-level Items
