IDI Platform Version 24.12 Core Bulletin
Change Orders
Functional Area | AR/FR | Description |
|---|---|---|
Provisioning | FR 3633 | Provisioning request processing improvement When a default value is configured for a variable, the default value will be sent to the provisioning provider when no matching variable outcome/SKU combination is found on the order. |
Resolved Known Issues
Functional Area | PR | Description |
|---|---|---|
Customer Care | 84641 | List values not showing under a POD property in Customer Care Users were not seeing list values under a POD property when viewing a service in Customer Care as they can be viewed on orders. This was due to an issue with list records look-up in the system. This has been fixed by a Provisioning platform update. |
Customer Care | 84748 | Incorrectprorated dates for recurring products on invoice preview The wrong bill period was used for a preview invoice after a customer changed bill cycles but had not been billed in the new cycle yet. This resulted in incorrect charge dates on recurring products. This has been fixed. |
Customer Care | 84774 | CPNI verification not logging failed attempts The validation functionality for the Account Password, Account Password Prompt, Security Question, and Security Question Prompt has been updated. The Verify button is now enabled after entering at least one character in the respective fields. If you enter an incorrect value and attempt to verify, the verification will fail, an error message will be displayed, and the failed attempt will be logged in CPNI History. This update ensures that failed attempts are appropriately handled and recorded. |
Orders | 84810 | Handset ID set to serial number from non-handset retail product FR 3517 deployed with version 23.4 supports auto-populating a service’s Handset ID on the Equipment Information tab using the handset’s serial number. However, the solution did not confirm a serialized retail product was actually a handset (by checking the Product Class). Consequently, if a serialized non-handset product was added to a service before a handset was added, the application would try to set the Handset ID to the non-handset retail product’s serial number and throw an error similar to: Length of HandsetSerialNumber (20) is not a valid ESN or MEID length for either decimal format (11 or 18) or hexadecimal format (8 or 14). This was fixed by adding a check of Product Class to ensure the application only sets the service’s handset ID when the retail product being added to the service is a handset. |
Tickets | 84764 | Incorrect time on journals/follow-ups in Tickets web module When viewing tickets via the Tickets web module, the time stamps for a ticket’s associated journals and follow-ups were not using the correct localized timezone. The time stamps were showing in Eastern Time instead of the user’s actual timezone.
Now, when using the Tickets web module to view tickets, time stamps on associated journals and follow-ups accurately reflect the local time zone. |
Advance Pay | 84812 | Advance Pay Automated Renewal orders not completing Some recurring transactions were prevented from completing (remaining in On Hold status). This issue was related to the assignment of transaction IDs, which caused errors and halted certain transactions. With this release, transaction IDs are now assigned correctly, ensuring that all recurring transactions can proceed smoothly. |
Provisioning _ Metaswitch | 84799 | Add/Update Individual Line not setting Maximum Permitted Contact Refresh Interval to configured value This issue is related to AR 9317, delivered with version 24.4 to enhance Metaswitch Add/Update Individual Line, Business group Line, and Business Group actions. The Maximum Permitted Contact Refresh Interval parameter was not being sent during a provisioning command which forced the Refresh parameter to be 24 hours in Metaswitch. The parameter will now be sent during provisioning commands such that the refresh will occur as configured. |
Provisioning _ Metaswitch | 84803 | Error on unsubscribing from Meta Subscriber Calling Name This issue is related to AR 9135, delivered in several earlier versions to support Ala Carte provisioning. The Meta Subscriber Calling Name was always being set to false even when not configured, preventing the accurate settings from being displayed. The Meta Subscriber Calling Name Delivery will now send the intended data with the correct settings when provisioning. |
Provisioning _ Metaswitch | 84813 | Mandatory Account Codes not provisioning properly This issue is related to AR 9135, delivered in serveral earlier versions to support Ala Carte provisioning. The Max Incorrect Code Attempts and Max Incorrect Code Attempts Per Call fields were being conflated which caused errors surrounding incorrect codes being used. These have been updated to function as needed, such that the errors occur only when appropriate. Additionally, the code length was not being sent during the call and will now be present and sent during provisioning. |
Provisioning _ Metaswitch | 84817 | Service notregistering in Metaswitch This issue is related to AR 9317, delivered with version 24.4 to enhance Metaswitch Add/Update Individual Line, Business group Line, and Business Group actions. The CFS Customer Info6 field and EAS Display Name were not required to match which prevented the service from registering. These fields are now required to match with a maximum of 32 characters. This will ensure services are able to be registered successfully. |
Platform System Deployment Updates:
Module | Target Deployment Updates |
|---|---|
Provisioning – Metaswitch | 12/03/2024 |
Provisioning Platform | 12/12/2024 |
Document Storage | 12/05/2024 |
Security | 12/09/2024 |