--- title: "IDI Platform Version 25.2 Details" slug: "idi-platform-version-25-2-details" updated: 2026-06-16T14:58:00Z published: 2026-06-16T14:58:00Z canonical: "help.idibilling.com/idi-platform-version-25-2-details" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.idibilling.com/llms.txt > Use this file to discover all available pages before exploring further. # IDI Platform Version 25.2 Details #### [IDI Platform Version 25.2 Core Bulletin](https://cdn.us.document360.io/3f7f8ade-bcb1-4ec8-af25-0c0ad8601afb/Images/Documentation/IDI-Solution-25.2-Core-Release-Bulletin(1).pdf?sv=2026-02-06&spr=https&st=2026-11-14T10%3A31%3A34Z&se=2026-11-14T11%3A31%3A34Z&sr=c&sp=r&sig=q6ir56BLEE%2Fryn%2FaSgn1G9kjs7rKK74iaWe7xGXhrog%3D) #### Change Orders | **Functional Area** | **AR/FR** | **Description** | | --- | --- | --- | | Customer Portal | FR 3626 | **Self service enhancements – Ticket integration and helpful links** Two self service enhancements in the Customer Portal can help you reduce call volume and related expenses for your service centers. - Integrating IDI tickets functionality lets your subscribers open and view tickets via their portals. Tickets are presented to subscribers as *support requests*. - The ability to add links (urls) on the Support page gives your subscribers quick access to helpful information. | | Customer Portal | FR 3645 | **Account lock indicators for port outs and SIM changes** In support of FCC compliance guidelines, this lets subscribers indicate when SIM changes and/or port outs are prohibited on their accounts. This is similar to the account lock functionality for Customer Care provided in the 24.11 release. With this functionality: - Providers can set up portal profiles to enable/disable subscribers’ ability to set and view account lock settings for SIM changes and port outs. - Subscribers can set and view account lock status when the functionality is enabled for them. > [!NOTE] > **Note:** > > These settings and corresponding indicators are for information only to provide a warning not to perform these actions. They do not prevent users from performing these actions. | | Orders – Port In | AR 9400 | **Making *Carrier Porting From* Required on Port-In ShortForm** This benefits providers that use the Port In short form in the Orders web module and need to capture *Carrier Porting From* when a service is ported in. This field is required on the long form but was not on the short form. Now you can make *Carrier Porting From* required through Order Field Configuration. | | Orders | FR 3647 | **Search enhancements** This release provides the following enhancements for web orders: - Searching by receipt number in the billing order Omnisearch. **Note**: All other Omnisearches already supported this. - Exporting the results of any Omnisearch in Orders. | | E-Rate | AR 9410 | **E-Rate date enhancement** To provide more flexibility, you can now override the date that billing uses for E-Rate processing. Prior to this, the last day of the bill period was always used as the E-Rate date (which is used for determining which FRNs are applicable and for logging utilization). With this enhancement, a new optional offset is available for your bill cycles. This new offset can be set independently for each bill cycle. When populated, this offset will be added to the last day of the bill period for all of your E-Rate processing for that bill cycle. The result date is then used for both purposes (the determination of the applicable FRN for eligible charges and the utilization date for E-Rate file creation). Additionally, the form for entering Manual Utilization, which defaults the utilization date once users select an invoice, has been enhanced to use the offset when applicable. > [!NOTE] > **Note:** > > Bill Cycle configuration is done by your IDI team. Please open a service request to have this capability enabled. | | Provisioning/ Workflow | FR 3616 | **Provisioning enhancements** This release provides significant enhancements to the variables functionality. The system now thoroughly analyzes the order’s context to ensure that the correct value is sent to the provisioning provider. The provisioning system allows multiple actions—such as adding or disconnecting services or features —to be executed within the same order, eliminating the need for workflow splitters or separate orders. All relevant SKUs are included in the provisioning request for Modify service actions when the POD is assigned at the feature level. | | Usage Processing | AR 9433 | **Ability to denote 5G usage for Periodic Rated Records (PRR)** New values for the *Recordtype* field in PRRs support denoting 5G usage. This is in compliance with the updated PRR Guide v13.1. | #### Resolved Known Issues #### Platform System Deployment | Functional Area | PR | Description | | --- | --- | --- | | Orders | 84820 | **Items already added to order are re-added after fixing staging error** When multiple items were staged and one was in error, valid items were added to the order but erroneously remained in staging. As a result, when the error was fixed, clicking **Add to Order** again, re-added all items, including those already added since they were not removed from staging. This has been corrected by ensuring items that pass validation and are added to the cart are removed from staging so only errored items remain. | | Customer Portal | 84822 | **Incorrect due date displayed in Customer Portal** Due dates were displaying incorrectly on the Customer Portal home screen. Previously, due dates were translated to your time zone based on system settings, which led to discrepancies, such as autopay dates appearing a day later than expected in some cases. This has been corrected so due dates align consistently across systems. | | Customer Care | 84798 | **Address update error** When attempting to validate a new billing address, the address would validate but it caused a *500 Internal Server Error* when the *Same as Primary* option was unchecked. This occurred only when adding a billing address for the first time, not when updating an existing billing address. The issue stemmed from missing information in the validation request, leading to a failed Address Validation call. With this fix, billing addresses can be added without errors. | | Customer Management – E-Pay | 84839 | **Unable to create recurring transactions** Users were unable to create recurring E-Pay transactions due to an error-handling issue in the E-Pay transaction process. The process has been fixed, ensuring that transactions can be created successfully. | #### Updates: | **Module** | **Target Deployment Updates** | | --- | --- | | Customer Portal | 01/27/2025 | | Document Storage | 02/10/2025 | | Provisioning | 02/13/2025 | | Communications | 02/21/2025 |