Longview v25.3 Software Release Notes
This document describes enhancements and changes to Longview version 25.3.
Announcements
Generative search is now available on the Longview documentation site. This AI-powered search capability allows users to enter questions or phrases in the search bar and receive instant, concise AI-generated answers without clicking through multiple search results. It also includes the ability to provide feedback to continuously improve answer quality.
-
Longview continues to enhance security and performance:
The Longview data server now logs all configuration parameters during startup for improved audit capabilities, with sensitive information automatically masked for security purposes.
Performance improvements have been made to the User Submissions app when working with large volumes of submission data.
Enhanced performance monitoring capabilities have been added to help diagnose bottlenecks, including event execution time tracking, wait time monitoring, and concurrent event logging to provide administrators with comprehensive performance insights.
A new Password attribute type has been introduced for the SAccessToken and SSMTPPassword system attributes, ensuring these sensitive values are automatically masked and not displayed to users for enhanced security.
-
For Longview Tax Pillar Two customers specifically:
-
The Adjusted Covered Taxes hierarchy has been updated to better align with the GloBE Information Return.
Note: If you have customized the P2300 or QD300 input apps, you may need to modify them to work with the updated hierarchy.
The option to create separate compliance periods has been introduced. This allows customers to isolate Pillar Two compliance data from provision estimate data, and gives greater flexibility in compliance workflows.
-
Significant enhancements have been made to align with GloBE Information Return requirements:
Enhanced ownership calculations and jurisdiction elections
Attributing top-up tax to entities other than the Ultimate Parent Entity (UPE),
Collecting Tax Identification Number (TIN) information and support for transition year balances and disposals
-
insightsoftware continues to focus our efforts on providing the greatest value in our product investment. As part of this effort, we began an initiative in 2020 to deprecate certain features that were legacy in nature and could be replaced with newer components that offered greater functionality and improved user experience.
The following components are deprecated as part of the current release:
Longview Legacy Non-HTML5 Dashboard: Deprecated as of version 25.2 now that cards on the HTML5 Longview dashboard can be manually or automatically refreshed.
Third-party authentication: Deprecated as of version 25.3 as Longview now supports the Longview SSO service, which provides a more industry-standard approach to Single Sign-On authentication.
Enhancements Added in Longview 25.3
Longview v25.3 contains enhancements in the following areas:
Longview Application Framework
| Enhancement | Description |
|---|---|
| LV-12413 | Longview Application Framework now supports connections using a service account. |
| LV-12414 |
Connecting to Longview Application Framework using the batch command now supports all connect commands allowing system administrators to more easily automate. The batch command can now execute Single Sign-On (SSO), ISW Platform AAD, and ISW Platform OPENID connection commands that were previously available only using the Longview Application Framework connect command within a Longview Procedure. For more information see the Longview Developer Guide. |
Longview Data Servers
| Enhancement | Description |
|---|---|
| LV-12408 | A new Password attribute type has been added specifically for the SAccessToken and SSMTPPassword system attributes. These attributes, which store sensitive text values, are now automatically masked and not displayed to users for security purposes. |
| LV-12415 |
The following logging has been added to the lv_dataserver.log to help diagnose performance-related issues when DIAGNOSTIC_SERVICE_DETAIL is set to TRUE: Event execution time from fired to completed. Example: (lvmgm_spawn_5300130_56) Total execution time for event 5300130: 00:00:00.688 Event wait time from triggered to fired. Example: (lvmgm_spawn_5300130_56) Total wait time for event 5300130: 00:00:20.276 Additionally, when DIAGNOSTIC_EVENT_PROFILING is enabled, the system now logs:Number of concurrent events in progress. Example: 5 events in progress |
| LV-12442 |
Support for third-party authentication has been removed from Longview. This includes the removal of the following server configuration parameters:-
Additionally, Single Sign-On (Web) option will no longer appear on the Longview sign-on screens unless Native SSO has been configured. |
| LV-12443 | The Longview data server now logs all lvsrvr.cfg configuration parameters and their values to the lv_dataserver.log file during server startup for audit purposes. Parameters are written in a consistent order with password parameters, DBO, and Host automatically masked for security purposes. |
| LV-12596 | Longview import logs now include timestamp information for imported files to help system administrators verify that the correct files were imported. The impdata.log and impsys.log files now include the recorded date and time of when the export was taken from the export control file. |
| LV-12621 | Longview Data Server utility processes now include connection retry logging and implement a delay between database reconnection attempts when the database becomes unavailable. The DATABASE_INITIATION_TIMEOUT parameter is now used with a 5-second delay between each retry attempt, providing consistent behavior between main processes and utility processes, and improved logging for connection retry attempts. |
| LV-12673 | Performance improvements have been made when opening the Longview User Submissions app with large volumes of user submissions. |
Longview Solutions Framework
| Enhancement | Description |
|---|---|
| LV-12688 |
Out of box Solutions events now support enabling troubleshooting mode using a configuration library. For more information see Customizing Calculations online documentation. |
Longview Tax -- Pillar Two
| Enhancement | Description |
|---|---|
| LV-12133 | The Income Inclusion Rule (IIR) calculation now supports attributing top-up tax to parents other than the Ultimate Parent Entity (UPE), including the calculation of the IIR offset. |
| LV-12239 | Longview Pillar Two now supports the details of allocation of income and taxes between constituent entities required for the GloBE Information Return. |
| LV-12288 | Longview Pillar Two now supports the collection of additional Tax Identification Number (TIN) information required for the GloBE Information Return, including the country the TIN was issued by and the type of the identification number for each constituent entity. |
| LV-12390 | Longview Pillar Two now supports collection of transition year balances and disposals information required for the GloBE Information Return. |
| LV-12395 | Ownership input and Ownership - Controlling Interest apps now display two decimals. Ownership - Controlling Interest now displays all owner relationships, but blocks the controlling interest flag if the owner is a POPE. |
| LV-12396 | The effective ownership calculation was updated to round to two decimal places to match the GIR requirements, and to handle cyclic ownership scenarios. |
| LV-12446 | Longview Pillar Two now includes the jurisdiction elections for non-allocation of deferred taxes and simplified reporting. |
| LV-12447 | Longview Pillar Two now includes the constituent entity elections for simplified calculations for non-material constituent entities and the GloBE loss election for the UPE. |
| LV-12450 | Longview Pillar Two now supports the collection of election year and revocation year for five-year jurisdiction level elections. |
| LV-12451 | Longview Pillar Two now supports the collection of election year and revocation year for five-year constituent entity level elections. |
| LV-12503 | Longview Pillar Two now supports compliance periods which allow for the isolation of Pillar Two from Tax Provision when preparing year-end data. Compliance periods work similarly to scenarios and execute steps that have the Type set to Pillar Two and the Return Rollover flag set. |
| LV-12510 | The adjusted covered taxes hierarchy has been updated to better align with the GloBE Information Return. If you have customized the P2300 or QD300 input apps you may need to modify them to work with the updated hierarchy. |
| LV-12570 | Longview Pillar Two now supports the capture of allocation details related to substance-based income exclusion. |
Issues Resolved in Longview 25.3
Longview 25.3 contains issues resolved for the following components:
- Longview Add-In for Office
- Longview Analysis and Reporting
- Longview Application Administrator
- Longview Application Framework
- Longview Data Servers
- Longview Designer
- Longview Journal Entries
- Longview Platform
- Longview Report Viewer
- Longview Server Manager
- Longview Smart Client
- Longview Tax
- Longview Tax -- Country by Country Reporting
- Longview Tax -- Pillar Two
Longview Add-In for Office
| Issue | Description |
|---|---|
| LV-12696 | LVLOCK function failed to create locks when used in Excel IF statements that were created with English regional settings and then used with regional settings where the decimal separator is a comma. |
| LV-12699 | In Longview Add-In for Office, users with passwords beginning with the @ symbol were unable to connect directly from the ribbon and received SSO or platform authentication errors. The @ symbol is no longer allowed as the first character in passwords. |
Longview Analysis and Reporting
| Issue | Description |
|---|---|
| LV-12376 | In the French version of Longview Analysis and Reporting, the thousands separator label was ambiguous about which separator character would be used. |
| LV-12781 | When using French regional settings, exporting reports with thousand separators to Excel as displayed resulted in numbers not being recognized as numbers in Excel. |
Longview Application Administrator
| Enhancement | Description |
|---|---|
| LV-11922 | Longview Application Administrator did not support more than 32,000 characters for modifying Rule Dependencies, Persistent Rules, Rule Merging, or Parallel Rules. |
| LV-12078 | Longview Application Administrator would hang when querying large volumes of data audit trail. |
Longview Application Framework
| Issue | Description |
|---|---|
| LV-4959 | Longview Application Framework Import didn't work when using decimals within a Range method expression for a mapping table. |
| LV-9080 | The Get JEDetails Longview Application Framework command exported symbols that users did not have access to. |
| LV-11433 | The Copy Data command in Longview Application Framework did not work on schedule data when DataType was set to CALCLEAF. |
| LV-11742 | The Longview Application Framework export spec filter expression did not support temporary symbols. |
| LV-12691 | Longview Application Framework list variable names were limited to 30 characters including the brackets, when the brackets should not have been counted toward the length limit. |
Longview Data Servers
| Issue | Description |
|---|---|
| LV-1374 | Longview Data Server export included app table records that referenced deleted symbols. |
| LV-12228 | Data server failed to start if the Longview identifier suffixed with underscore followed by numbers and MATH_POOL was set to 1 in the server configuration file. |
| LV-12262 | Some LVMGRL commands did not work correctly when not entered in lowercase. |
| LV-12564 | The Oracle SCHEMA_LV_DATASERVER.sql generated using DBSCRIPT contained an INSERT statement that was missing a value for a system attribute. This impacted new installations for Oracle systems. |
| LV-12671 | The run command to execute procedures from the Longview Dashboard did not honor the specified group parameter. |
Longview Designer
| Issue | Description |
|---|---|
| LV-12577 | Longview apps created in Longview Designer with trailing spaces in the name would cause errors. |
Longview Journal Entries
| Issue | Description |
|---|---|
| LV-11987 | Journal Entry detailed reports could not be generated when the creator's name/description was too long. |
| LV-12780 | In the French version of Longview Journal Entries, number fields in the Details section would only accept English-formatted numbers, causing issues when users tried to enter French formatted numbers. |
| LV-12863 | In an English operating system, launching the French version of Longview Journal Entries would result in an error when saving journal entry details. |
Longview Platform
| Issue | Description |
|---|---|
| LV-9748 | The LongviewClientID parameter was not validated in Session API requests. This parameter is no longer required and will be ignored if included in the request. |
| LV-9964 | The Longview Dashboard 'Login not Available' screens displayed inconsistently between IPC and TCP connection types. |
| LV-11075 | The Longview Dashboard Change Password page styling was inconsistent with other Longview Dashboard pages. |
| LV-12585 | In some network environment configurations, users were unable to sign onto Longview using Single Sign-On. |
Longview Report Viewer
| Issue | Description |
|---|---|
| LV-12145 | In some cases, users would receive an error message when opening a report with scheduled dimensions, causing the report to not open. |
| LV-12382 | File attachments containing special characters could not be opened from Longview Report Viewer. |
Longview Server Manager
| Issue | Description |
|---|---|
| LV-12509 | Saving the server configuration in Longview Server Manager caused extra carriage feed characters within the lvsrvr.cfg. |
| LV-12518 | Longview Server Manager was unable to connect to multiple data server instances with the same Longview ID but different host names. |
Longview Smart Client
| Issue | Description |
|---|---|
| LV-2979 | In Longview Input Apps, dynamic models using RANGE variables would report an error on first execution. |
Longview Tax
| Issue | Description |
|---|---|
| LV-11482 | Updating regional modification parameters via the Regional Modifications editor or using the parameters import for regional modifications now correctly assigns the modified accounts as writable or read-only. In addition, override is handled correctly when applying FALSE or blank for the automate setting when importing the regional modification parameters. |
| LV-12507 | Corrected the calculation of NBR Rate Change in the combined report for prior year change in deferred tax recognised in IAS/IFRS Multi-Regional Provision. |
| LV-12614 | An error could occur when specific updates were made after applying newly added symbols, without refreshing in the Manage ETR Disclosure Accounts App. |
| LV-12693 | The tax account roll forward transfer would skip calculations for a custom timeframe that was not created in all uppercase. |
Longview Tax -- Country by Country Reporting
| Issue | Description |
|---|---|
| LV-11130 | Improved performance of current tax change calculation in IAS multi-regional provision when a large number of segments are in use. |
| LV-11131 | The performance of the national current provision calculation was improved in Multi-Regional Provision (ASC / US GAAP) systems with a large number of segment and/ or detail symbols. |
| LV-12255 | HMRC XML output for country by country reporting was updated to output the correct issuedBy value for entities with NOTIN, and to output the correct code when the TIN is issued by a country that differs from the country of residence. |
| LV-12622 | Country by Country Automation now hides the details and segments source symbols if they are configured as pass-through dimensions in Tax Provision. |
Longview Tax -- Pillar Two
| Issue | Description |
|---|---|
| LV-12644 | Top-up tax percentage is now correctly set to 0, when a jurisdiction has negative GloBE Income. |
| LV-12661 | In some cases, the temporary difference net transfer could fail with an error when foreign currency exchange is enabled in Pillar Two. |
Hardware and Software Requirements
This chapter contains information on these main topics:
- Supported Server Platforms
- Supported Client Platforms
- Upcoming Unsupported Server and Client Platforms
Note: Third party components and versions, such as operating systems, browsers, etc., no longer in support by the third-party provider are not supported by Longview as well.
Supported Server Platforms
Supported platforms are defined as the Operating System and RDBMS "families", and minimum patch/point level on which the application is supported under the terms of the Customer's maintenance Services Agreement. Assistance with issue investigation and resolution is available through Support Services. Any platform related software issues identified will be addressed based on Longview's standard issue prioritization criteria.
Longview reserves the right to end support for supported platforms with subsequent releases of the application.
Should a customer choose to use current versions of Longview software on non-supported platforms, Longview will continue to provide the application support under the terms of the Maintenance Services Agreement with the following exceptions:
Issues encountered which cannot be replicated on a currently supported platform will not be addressed.
For issues that exist on both supported and non-supported platforms, fixes will be verified only on supported platforms and may or may not address the issue on the non-supported platform.
No support is available for platforms (OS or RDBMS) that are no longer supported by their respective vendors.
This section contains information on supported platforms for the following items:
Updating Windows Universal CRT
Improved security and compatibility of Longview means that older server machines must install Windows Universal C Runtime (CRT) update 2999226. You can determine whether your server requires this update and download this update, if needed, from the following link: https://support.microsoft.com/en-us/kb/2999226
Data Server OS and RDBMS
The following combinations are supported for all servers in the application. For details on the term Supported, see Supported server platforms.
| Server operating system(x64 architecture) | Server RDBMS (64-bit) |
|---|---|
| Windows Server 2022 |
SQL Server 2022 SQL Server 2019 Oracle 19c |
| Windows Server 2019 |
SQL Server 2022 SQL Server 2019 Oracle 19c |
Note: If you are using a separate Database server, any platform and Operating System supporting the database versions can be used.
Web Server
The following combinations are supported for the Web Server. For details on the term Supported, see Supported server platforms.
Note: The Web Server supports only x64 Server hardware architecture.
| Server operating system (64-bit) | Web Server (64-bit) |
|---|---|
| Windows Server 2022 | Microsoft IIS 10.0 |
| Windows Server 2019 | Microsoft IIS 10.0 |
Data Server Web Services
The following combinations are supported for Data Server Web Services. For details on the term Supported, see Supported server platforms.
Note: Data Server Web Services supports only x64 Server hardware architecture.
| Server operating system (64-bit) | Java |
|---|---|
| Windows Server 2022 |
Oracle JDK 17 (LTS), Oracle JDK 21 (LTS), OpenJDK 17 or OpenJDK 21 |
| Windows Server 2019 |
Oracle JDK 17 (LTS), Oracle JDK 21 (LTS), OpenJDK 17 or OpenJDK 21 |
Note: Apache Tomcat is deployed as part of the Data Server Web Services install process. If you have already installed Apache Tomcat, you must have version 9.0.102 installed.
Longview Grid Server
The following combinations are supported for the Longview Grid Server when Grid Processing Type is selected in Longview Server Manager. For details on the term "Supported", see Supported server platforms.
Note: Longview Grid Server supports only x64 Server hardware architecture.
| Operating system (64-bit) | ODBC |
|---|---|
| Windows Server 2022 | ODBC Driver 18 for SQL Server |
| Windows Server 2019 | ODBC Driver 18 for SQL Server |
Note: You must install the ODBC Driver 18 for SQL Server on the grid node that corresponds to the RDBMS that the Longview application server is configured for.
HTTP Proxy Server
The following combinations are supported for the HTTP Proxy Server. For details on the term Supported, see Supported Server Platforms.
| Server hardware | Server operating system (64-bit) |
|---|---|
| x64 Architecture |
Windows Server 2022 Windows Server 2019 |
Note: You must have .NET 4.8 installed to run HTTP Proxy Server.
Supported Client Platforms
This section contains information on Supported platforms for the following items:
Longview Client Components
The following platforms are supported for client computers. For details on the term Supported, see Supported Server Platforms.
| Client operating system(64-bit) | Web browser | .NET version |
|---|---|---|
| Windows 11 |
Microsoft Edge Google Chrome1 |
.NET 4.8 |
| Windows 10 |
Microsoft Edge Google Chrome1 |
.NET 4.8 |
Note: Chrome browsers require a Chrome extension to automatically deploy and launch ClickOnce components. Alternatively, an organization can use Enterprise Deployment to deploy components via IT.
Important: Longview recommends a DPI display setting of 100%. Using a DPI mode other than 100% can cause display issues ranging from incorrect and inconsistent font sizes to interface elements not being visible on the screen.
Microsoft Excel
The following Microsoft Excel versions are supported.
Note: Both Microsoft Office and Microsoft Office 365 are supported; however, you must use the fully deployed version of Microsoft Excel to work with Longview Add-In for Office.
| Longview Add-In for Office |
|---|
Office 365 -- 32-bit and 64-bit |
| Excel 2024 -- 32-bit and 64-bit |
| Excel 2021 -- 32-bit and 64-bit |
| Excel 2019 -- 32-bit and 64-bit |
Supported Languages
Longview client components are language consistent. For example, for a French client system, this update supports the French version of the Longview client, with the default regional settings, running with the French version of the respective operating system, and the French version of Microsoft Office.
However, for the servers, this update supports English versions of the respective RDBMS, server operating system, or Web server, regardless of the client language.
The following table outlines the language requirements for your Longview system.
| English | French | |
|---|---|---|
| Windows requirements | English WindowsEnglish Microsoft Office | French WindowsFrench Microsoft Office |
| Java |
Oracle JDK 17 (LTS) Oracle JDK 21 (LTS) OpenJDK17 or OpenJDK 21 |
Oracle JDK 17 (LTS) Oracle JDK 21 (LTS) OpenJDK17 or OpenJDK 21 |
| Web browser | English | French |
| Server operating system | English | English |
| RDBMS | English | English |
| Web server | English | English |
Upcoming Unsupported Server and Client Platforms
Server Platforms
| Platform | Note |
|---|---|
| Windows Server 2019 | The last version of Longview that will be supported on Windows Server 2019 will be 26.1 (January 2026). |
| Oracle | Longview will continue to support Oracle 19c until it's EOL of April 30, 2027, Oracle has still not announced the release date for Oracle 23ai for Windows. Longview is currently reviewing the future of ongoing support of Oracle. |
Client Platforms
| Platform | Note |
|---|---|
| Windows 10 | In line with Microsoft EOL of Windows 10, Longview will only support Windows 10 LTSC 2021 (21H2) until October 14, 2025. |
| Microsoft Excel 2019 | In line with Microsoft EOL of Office 2019 extended support, Longview will only support Office 2019 until Oct 14, 2025. |
Longview Support Schedule
- As of this release, only Longview version 22.2 and newer are supported.
- Longview 22.2 will no longer be supported as of February 2026.
- As of 24.1 our standard support life cycle will be 3 calendar years from the month of release.
See the table below for more details:
| Version | Release Date | End of Support |
|---|---|---|
| 22.1 | June, 2022 | July, 2025 |
| 22.2 | November, 2022 | February, 2026 |
| 23.1 | March, 2023 | April, 2026 |
| 23.2 | May, 2023 | July, 2026 |
| 23.3 | August, 2023 | October, 2026 |
| 23.4 | November, 2023 | February, 2027 |
| 24.1 | February, 2024 | February, 2027 |
| 24.2 | May, 2024 | May, 2027 |
| 24.3 | July, 2024 | July, 2027 |
| 24.4 | October, 2024 | October, 2027 |
| 25.1 | January, 2025 | January, 2028 |
| 25.2 | April, 2025 | April, 2028 |
| 25.3 | July, 2025 | July, 2028 |
For more information on any of the above updates, please contact your Customer Success Manager, Account Executive, or Longview Support.