Longview v24.2 Software Release Notes
This document describes enhancements and changes to Longview version 24.2.
Announcements in Longview 24.2
In this release we have continued to focus on performance. Querying batch and event tables has been improved for the SQL Server Longview Database.
For Longview Tax customers, the National Combined calculations has been updated to improve performance within Longview Tax Multi-Regional Provision (IAS/IFRS) and the deferred tax calculation has been improved in both versions of Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS) when there are a large number of accounts, entities, and currencies but sparse data.
-
We continue to add further BEPS 2.0 Pillar Two functionality. In 24.2 we introduce:
Scenario maintenance and initialization specifically for Pillar Two scenarios
Optional support for constituent entity data to be input and calculated in functional currency. Constituent entity data will be then translated to reporting currency for jurisdiction level inputs and calculations.
A dedicated Manage Constituent Entity Elections app for constituent entity elections. Input apps and calculations have also been updated to take into account these election settings.
From release 24.2, Longview natively supports SSO using SAML and/or OpenID/OAuth protocols. Longview supports Longview REST sessions using OAuth ClientID/secret and Longview Application Framework also supports OAuth connections.
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.
A recap of the recent decisions, the following features have been de-supported over the past few releases:
Longview Desktop – Version 10.7 (Fall 2020)
Longview Input – Version 21.1 (Spring 2021)
Longview Component Manager – Version 22.1 (Spring 2022)
Legacy Longview for Excel component – Version 22.1 (Spring 2022)
No additional components are deprecated as part of the current release.
Enhancements Added in Longview 24.2
Longview 24.2 contains enhancements in the following areas:
- Longview Application Framework
- Longview Platform
- Longview Solutions Framework
- Longview Tax – Multi-Regional Provision
- Longview Tax – Pillar Two
Longview Application Framework
| Enhancement | Description |
|---|---|
LV-9358 |
In addition to TLS 1.2, Longview Application Framework connection now also supports TLS 1.3 when using HTTP Proxy. |
Longview Platform
| Enhancement | Description |
|---|---|
LV-8657 |
Longview now supports SSO using SAML and/or OpenID/OAuth protocols. Users can now create Longview REST sessions using OAuth ClientID/secret. Longview Application Framework also supports OAuth connections. For more information see Longview SSO Service Installation Guide. |
| LV-9291 | Changes have been made to the SQL Server Longview Database to improve the performance of querying batch and event tables. |
| LV-9362 | Security improvements were made by removing support for TLS 1.1. |
Longview Solutions Framework
| Enhancement | Description |
|---|---|
LV-9308 |
The generic PUT data REST API now supports content in application/json with both concise and verbose formats. For more information see Longview Integration Guide. |
LV-9310 |
The templated PUT data REST API now supports content in application/json. You will need to save existing templates via Longview Designer to update them to be compatible with application/json. New and existing templates are still compatible with content in text/csv. For more information see Longview Integration Guide. |
LV-9312 |
The generic GET data REST API now supports response body in application/json in both a concise and verbose format. For more information see Longview Integration Guide. |
LV-9314 |
The templated GET data REST API now supports response body in application/json in both a concise and verbose format. You will need to save existing templates via Longview Designer to update them to be compatible with application/json. New and existing templates are still compatible with content in text/csv. For more information see Longview Integration Guide. |
Longview Tax – Multi-Regional Provision
| Enhancement | Description |
|---|---|
LV-7763 |
Longview Tax Multi-Regional Provision (IAS/IFRS), updates have been made to improve the performance of National Combined calculations. |
Longview Tax – Pillar Two
| Enhancement | Description |
|---|---|
LV-6591 |
Longview Pillar Two now includes support for scenario maintenance and initialization. |
LV-9175 |
Longview Pillar Two has been updated to optionally support constituent entity data input and calculations in functional currency. Constituent entity data will be then translated to reporting currency for jurisdiction level inputs and calculations. This is enabled by setting the system attribute ASP2FX (Translate Pillar Two Constituent Entity Data) to TRUE. |
LV-9263 |
Longview Pillar Two now supports elections for constituent entity elections via the Manage Constituent Entity Elections app. Input apps and calculations have also been updated to take into account these election settings. |
Issues Resolved in Longview 24.2
Longview 24.2 contains issues resolved for the following components:
- Installation and Supported Platforms
- Longview Add-In for Office
- Longview Application Administrator
- Longview Application Framework
- Longview Close
- Longview Dashboard
- Longview Data Servers
- Longview Designer
- Longview Documentation
- Longview Platform
- Longview Report Viewer
- Longview Smart Client
- Longview Solutions Framework
- Longview Tax – Global Transparency
- Longview Tax – Multi-Regional Provision
- Longview Tax – Pillar Two
- Longview Tax – Tax Provision
- Longview Web Services
Installation and Supported Platforms
| Issue | Description |
|---|---|
LV-9338 |
In some cases, the Longview Installer upgrade did not replace files with their latest version. |
Longview Add-In for Office
| Issue | Description |
|---|---|
LV-9301 |
Tidemark users that were not owners or administrators of an application would receive errors upon connecting to Tidemark using the Longview Add-In for Office. |
LV-9336 |
View Query dialog did not display correctly when the user’s scaling and layout settings were set to 150%. |
Longview Application Administrator
| Issue | Description |
|---|---|
LV-9448 |
Longview Application Administrator would crash when setting symbol access in systems with a large number of symbols in the Accounts dimension. |
Longview Application Framework
| Issue | Description |
|---|---|
LV-9369 |
Running a Longview procedure that has only whitespace characters on the last line would cause an error. |
LV-9415 |
Numbers were rounded to 6 decimal places instead of 9 when they were imported in JSON format. |
Longview Close
| Issue | Description |
|---|---|
LV-9361 |
In Longview Close an error would occur when upgrading a system from a version prior to 22.2 to 22.2 or later if allocations had never been deployed. |
Longview Dashboard
| Issue | Description |
|---|---|
LV-9334 |
The Longview Session Timeout page had the wrong window title. |
Longview Data Servers
| Issue | Description |
|---|---|
LV-8980 |
In some cases, the data servers would generate an error message “Unable to delete user entry in shared memory.” |
LV-9394 |
Locks were not being created as persistent locks when USE_SESSION_LOCKS was set to FALSE. |
LV-9433 |
A user without the modify data authorization was able to create locks. |
Longview Designer
| Issue | Description |
|---|---|
LV-8653 |
Longview Apps were not generated correctly by Longview Designer when the file contained %{ in its content. |
Longview Documentation
| Issue | Description |
|---|---|
LV-9558 |
Longview Designer documentation for free form apps has been updated to include details on creating tabbed apps with the UI document. |
LV-9681 |
Longview Developer's Guide was updated to include a note for how the StrValue(), and Value() functions handles a value when the returned value is not the type it is expecting. |
Longview Platform
| Issue | Description |
|---|---|
LV-9581 |
In some cases, sessions remained in the Longview Data Servers for single sign on users after closing the components. |
Longview Report Viewer
| Issue | Description |
|---|---|
LV-9569 |
In some cases, when a report's orientation was changed to have all the dimensions displayed down and/or across, the lvwag.exe would crash. |
Longview Smart Client
| Issue | Component | Description |
|---|---|---|
LV-9449 |
Forms |
The Longview Smart Client would crash intermittently when a custom form button was clicked multiple times. |
LV-9612 |
Data Grids |
The Longview Smart Client would crash when opening a data grid that contained a ConditionalCellStyle with the same foreground and background color. |
Longview Solutions Framework
| Issue | Description |
|---|---|
LV-9363 |
In cases where a customer is using time period specific allocations and thousands of area definitions have accumulated over time, Manage Allocations, and Run Allocations would take minutes to open.
Note: For Manage Allocations, changes will need to be applied to the UpdateAreas document in the Calculations section. You can review the changes in the out of box version of Manage Allocations in Longview Designer (lines 1-15). The change is to build a list of allocation ids prior to retrieving the areas. |
LV-9424 |
In a multi-tabbed data view input app, if import was enabled on more than one tab using different data areas, import would work successfully the first time and then could fail with an error if executed on a different tab. In cases where it was executed on the same the tab twice, import would succeed but it would import the same file that was selected for the first execution. |
Longview Tax – Global Transparency
Issue |
Description |
|---|---|
LV-9388 |
During an install of Global Transparency into a Tax Provision or Tax Multi-Regional Provision system with multiple time periods, the attribute AZTaxGTReturnSourcePeriod (Time Period - Return Source Period) was not set correctly for all return year symbols. |
Longview Tax – Multi-Regional Provision
| Issue | Description |
|---|---|
LV-9368 |
In Longview Tax Multi-Regional Provision (ASC/US GAAP, IAS/IFRS), the performance of deferred tax calculation was improved when executed against a large number of accounts, entities, and currencies with sparse data. |
Longview Tax – Pillar Two
| Issue | Description |
|---|---|
LV-9328 |
During a Longview Pillar Two upgrade the current period for Pillar Two was switched to be the same as the current period for Tax Provision. |
LV-9337 |
In Longview Pillar Two (IAS/IFRS), the cumulative translation adjustment for temporary differences was mapped to equity instead of OCI, creating a mismatch when comparing Pillar Two and Tax Provision. |
LV-9340 |
In a standalone Longview Pillar Two instance, deploying the transitional safe harbours starter kit would fail with an error. |
LV-9341 |
In a standalone Longview Pillar Two instance, the P2310- GloBE Temporary Differences input app would fail with an error when opened. |
LV-9345 |
In Longview Pillar Two, a lock conflict could occur in the recast calculation if a user had the P2310 GloBE Temporary Differences input app open. |
LV-9408 |
In Longview Pillar Two, Manage Constituent Entities would allow import with election values set to blank or NULL. This would cause an issue when an app or event referenced these election settings. Any blank or NULL value settings imported for elections will now be set to 0. |
LV-9680 |
In a standalone Longview Pillar Two system, performing a year end rollover would not update the current period symbol attribute AZTaxCP for the new periods. |
LV-9757 |
When adding Longview Tax Provision to an existing standalone Longview Pillar Two system the deployment process would fail. |
Longview Tax – Tax Provision
| Issue | Description |
|---|---|
LV-8716 |
In Longview Tax Provision (IAS/IFRS), when an opening balance is entered into the adjustment account of a temporary difference for an entity using deferred tax scheduling and the closing balance is zero, the deferred tax would erroneously calculate an additional rate change amount resulting in a non-zero closing balance. |
LV-9298 |
Longview Entities Editor UI did not display correctly when the user’s scaling and layout settings were set to 150%. |
LV-9661 |
The Longview Entities Editor was always displaying the Entity Level for Interim ETR column, regardless of the system settings. |
Longview Web Services
| Issue | Description |
|---|---|
|
LV-9317 LV-9318 |
Security vulnerabilities related to third party software that was using Log4J libraries were fixed. |
Hardware and Software Requirements
This section contains information on these main topics:
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.
| (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.85 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: 1 Chrome browsers require a Chrome extension to launch ClickOnce components. For example, the Windows Remix ClickOnce Helper to launch Longview ClickOnce components.
Caution: 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 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 Windows English Microsoft Office |
French Windows French 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. As of the Longview 24.2 release date, Oracle has still not announced the release date for Oracle 23c 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) as of 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 21.1 and newer are supported.
- Longview 21.1 will no longer be supported as of July, 2024.
- As of 24.1 our standard support life cycle will be 3 calendar years from the month of release.
See the below table for more details:
| Version | Release Date | End of Support |
|---|---|---|
| 10.7 | November, 2020 | February, 2024 |
| 21.1 | May, 2021 | July, 2024 |
| 21.2 | November, 2021 | February, 2025 |
| 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 |
For more information on any of the above updates, please contact your Customer Success Manager, Account Executive, or Longview Support.