Longview v24.3 Software Release Notes
This document describes enhancements and changes to Longview version 24.3.
Announcements in Longview 24.3
Introducing an AI Assistant for Longview on the ISW Platform, with its initial Doc Assist function designed to streamline your documentation search. The AI Assistant will expand to more capabilities in future releases.
-
Pillar Two:
An update to foreign currency translation when it is enabled, where all automation and other calculations for constituent entities are applied in both functional and reporting currency. Only manually entered data is translated using the Pillar Two foreign exchange rate.
-
Various updates to the GloBE Temporary Differences following customer feedback including:
Support for specific detail and segment symbols as sources when transferring temporary difference balances from Tax Provision.
Support for automation and input of values for temporary difference adjustments across all details, and manual adjustments to temporary differences per provision to account for edge cases in determining the impact of temporary differences on covered taxes.
In order to align Pillar Two and Provision more closely and facilitate correct calculation of the recast adjustment, rate change has been broken out into its own element, plus change in deferred tax not recognised for IAS and CTA for ASC.
Introducing a new app to set jurisdiction level elections and other settings. In the next release, it will replace settings in the current Manage Constituent Entities app.
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.3
Longview 24.3 contains enhancements in the following areas:
- Installation and Supported Platforms
- Longview Application Framework
- Longview Designer
- Longview Solutions Framework
- Longview Tax – Pillar Two
Installation and Supported Platforms
Enhancement | Description |
---|---|
LV-9639 |
Longview on the ISW Platform now features an AI Assistant, accessible via the Longview Dashboard and Client, with its initial Doc Assist function designed to streamline your documentation search. The AI Assistant will expand to more capabilities in future releases. |
LV-10501 | The ClickOnce software package (ClickOnce-LVSoftware.kar) file is now solely located in the software folder, eliminating the need for duplication in the en and fr directories. |
Longview Application Framework
Enhancement | Description |
---|---|
LV-9906 |
When using an import spec with a JSON source in the field name, it will now map the field name to the property name rather than using the field number to map to the index of the the property. |
Longview Designer
Enhancement | Description |
---|---|
LV-9815 LV-10294 |
In Longview Designer, field names are now exposed in the UI-based import and export specification documents. The following designer templates are updated:
|
Longview Solutions Framework
Enhancement | Description |
---|---|
LV-10207 |
Generic REST APIs now use dimension names and ‘value’ for the property names when working with application/json content. For more information, see the integration guide. |
Longview Tax – Pillar Two
Enhancement | Description |
---|---|
LV-8855 |
Longview Pillar Two now allows automation and input of values for temporary difference adjustments across all details. |
LV-9621 |
In Longview Pillar Two, a new app to set jurisdiction level elections and other settings has been included. While it is not fully integrated for this release, it will eventually replace settings in the current Manage Constituent Entities app. At that point there will be a step in the upgrade process that will convert settings applied in Manage Constituent Entities to the new app. |
LV-9780 |
In Longview Pillar Two, Temporary Differences input has been updated to allow manual adjustments to temporary differences per provision to account for edge cases in determining the impact of temporary differences on covered taxes. |
LV-9781 | In Longview Pillar Two, Temporary Differences has been enhanced to include the configuration of detail and segment symbols used as the source when transferring temporary difference balances from Tax Provision. |
LV-9782 | In Longview Pillar Two, Temporary Differences has been enhanced to separate rate change into its own element. In addition for IAS, change in deferred tax not recognised has been separated into its own element. Finally for ASC, CTA has been separated into its own elements. These changes align Pillar Two and Provision more closely and facilitate correct calculation of the recast adjustment. |
LV-9936 | In Longview Pillar Two, when foreign currency translation is enabled, all automation and other calculations for constituent entities are applied in both functional and reporting currency. Only manually entered data is translated using the Pillar Two foreign exchange rate. |
Issues Resolved in Longview 24.3
Longview 24.2 contains issues resolved for the following components:
- Longview Add-In for Office
- Longview Application Framework
- Longview Data Servers
- 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 Add-In for Office
Issue | Description |
---|---|
LV-9959 |
The wrong icon was used for the default Refresh button in the Longview Add-In for Office toolbar. |
LV-10694 |
In some cases, subsequent SSO prompts would display in a small window when a SSO user was connecting using Longview Add-In for Office. |
Longview Application Framework
Issue | Description |
---|---|
LV-9809 |
The LongviewAction Run did not look in the Custom Files Location. |
LV-9873 |
Some parameters were missing from the history file in the SSO-connect Longview Application Framework command. |
Longview Data Servers
Issue | Description |
---|---|
LV-1306 |
Query rules that crossed partitions prevented partition recalcs from being performed. |
LV-6817 |
The Longview Servers would not start when the CTA account for Integrated method was not set when using eliminations. |
LV-9971 |
Longview server export did not re-index symbols for mirrored schedule dimensions. |
LV-9329 | In some cases, there was no warning displayed on servers start up when there were NDD mapping errors. |
LV-10206 | When using batchwait on a data submission, a server agent (lvagent.exe) would crash. |
LV-10318 | In some cases, the Longview servers would crash when running REST API with a service account user. |
LV-10362 | Setting the SJED1Symbols system attribute to over 31 root symbols caused the journal entries server (lvjent.exe) to crash when turning maintenance off or when the servers were started. |
LV-10503 | The web agent (lvwag.exe) would crash when launching a report where symbols were being passed in, but not all the fixed dimensions had symbols selected. |
Longview Documentation
Issue | Description |
---|---|
LV-10241 |
The Longview Server Manager Guide contained incorrect steps for setting up in memory cache. |
Longview Platform
Issue | Description |
---|---|
LV-9925 |
When TCP web setup was used, incorrect text was displayed on the Longview Dashboard Sign-on page when the servers were stopped. |
LV-9932 | Longview Single Sign-On service did not check the scope defined in the configuration file. |
LV-10166 | Service account users were not able to launch REST API apps. |
LV-10483 | Single sign-on users were unable to connect to Longview using Longview Add-In for Office and Longview Applications from the start menu with some IDP configurations. |
Longview Report Viewer
Issue | Description |
---|---|
LV-9988 |
Reports using symbol attributes did not resolve the attribute based on the selected symbol when the report was published with a default symbol. |
Longview Smart Client
Issue | Component | Description |
---|---|---|
LV-10165 |
Data Tables |
The filter pop-up menu was incorrectly removing underscores in the value display strings. |
LV-10330 |
Data Grids |
An error occurred when opening a Longview Data Grid containing data suppression and blank symbols. |
LV-10493 | Forms | Long validation messages were truncated in Longview Forms. |
LV-10494 | Forms | The “Required” label was not translated to French. |
Longview Solutions Framework
Issue | Description |
---|---|
LV-9835 |
The confirmation form for replacing existing process maps during import has been updated to reduce the vertical space used. |
LV-9836 | When modifying the next steps for a process map step, if the next steps included a step whose name was contained in the name of another step (e.g. S1 and S11), it would check both steps in the form. |
LV-10046 | Log and error files generated by REST APIs are now stored in the logs\restapi folder within the custom files folder. |
Longview Tax – Global Transparency
Issue |
Description |
---|---|
LV-9497 |
When a return rollover was executed for Global Transparency in a system using the return period for input, non-financial data was not copied. A new 'Source Return - Non-Financial Data' step has been added to Rollover and Scenario Setup to copy this data during a return rollover. This step should be enabled for the 'Return Rollover' column with the other Global Transparency steps disabled for the 'Return Rollover' column in systems where the return period is used for Global Transparency. |
Longview Tax – Multi-Regional Provision
Issue | Description |
---|---|
LV-1619 |
In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), scenario initialization was not properly applying the clear data flag for steps using the system process method, such that when a previously initialized scenario was reinitialized it would contain residual data. |
LV-9751 | In Longview Tax Multi-Regional Provision (ASC/US GAAP, IAS/IFRS) when performing a rollover the user submission comment was repeating the previous step's comment when the step performed a copy. |
LV-10041 | In Longview Tax Multi-Regional Provision (IAS/IFRS), the Multi-Regional Change Deferred Tax Recognised/Deferred Tax Not Recognised calculation would fail with an error when triggered by a large number of accounts. |
LV-10297 | In Longview Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), the performance of deferred tax classification and combined deferred tax classification was improved in cases where a combination of accounts, entities and regions being triggered would result in a large area of data being processed at once. |
Longview Tax – Pillar Two
Issue | Description |
---|---|
LV-9934 |
Installing Longview Pillar Two on an existing Tax Provision system would result in an error if the system did not contain the user group "CorporateAnalysts" and the user "TaxAdmin". |
LV-10545 |
In Longview Pillar Two, the temporary difference recast adjustment calculation would fail with an error when triggered by a large number of accounts. |
Longview Tax – Tax Provision
Issue | Description |
---|---|
LV-1618 |
In Longview Tax Provision (IAS/IFRS), additional scenario initialisation steps have been added for new installs only. The added steps are:
|
LV-1619 |
In Longview Tax Provision (ASC/US GAAP and IAS/IFRS), scenario initialization was not properly applying the clear data flag for steps using the system process method, such that when a previously initialized scenario was reinitialized it would contain residual data. |
LV-9751 |
In Longview Tax Provision (ASC/US GAAP, IAS/IFRS) when performing a rollover the user submission comment was repeating the previous step's comment when the step performed a copy. |
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.3 release date, 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) 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 |
24.3 | July 2024 | July 2027 |
For more information on any of the above updates, please contact your Customer Success Manager, Account Executive, or Longview Support.