Longview v23.1 Software Release Notes
This document describes enhancements and changes to Longview version 23.1.
This document contains information on these main topics:
- Announcements in Longview 23.1
- Enhancements in Longview 23.1
- Issues Resolved in Longview 23.1
- Hardware and Software Requirements
Announcements in Longview 23.1
- In this release we have included additional of BEPS 2.0 Pillar Two functionality to meet the new Global Minimum Tax reporting requirements. New functionality includes: updates to constituent entities, editors for GloBE accounts, support for temporary differences, and automation for GloBE income and GloBE covered taxes.
- The Longview applications continue to undergo significant rebranding to create a more modern look and feel, and to align our solutions and user experience with the broader solution set of insightsoftware.
- A new API, ConnectWithSingleSignOn, has been added to the API functions available in Longview Add-In for Office. This API allows the connection to the Longview server to be coded using SSO authentication.
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.
In addition, we communicated the updated support schedule to coincide with the new version numbering that has been adopted by the Longview Product as part of our acquisition by insightsoftware.
To recap that schedule, see the table below:
Release Version | Calendar Release | Oldest Support Version | Version No Longer Supported |
|---|---|---|---|
10.7 | Nov-20 | 3.5.7 |
|
21.1 | May-21 | 3.5.7 |
|
21.2 | Nov-21 | 3.5.7 |
|
22.1 | May-22 | 7.3 | All versions < 7.3 |
22.2 | Nov-22 | 7.3 | No new versions |
23.2 | May-23 | 10.6 | Versions 7.3 – 10.5 |
23.4 | Nov-23 | 10.7 | 10.6 |
24.2 | Apr-24 | 21.1 | 10.7 |
24.4 | Oct-24 | 21.2 | 21.1 |
25.2 | Apr-25 | 22.1 | 21.2 |
25.4 | Oct-25 | 22.2 | 22.1 |
26.1 | Feb-26 | 23.1 | 22.2 |
For more information on any of the above updates, please contact your Customer Success Manager, Account Executive, or Longview Support.
Enhancements in Longview 23.1
Longview 23.1 contains enhancements in the following areas:
Longview Add-In for Office
Enhancement | Description |
|---|---|
LV-6337 | Longview Add-In for Office has been updated to remove IE dependencies when using SSO configurations. |
LV-7143 | A new API, ConnectWithSingleSignOn, has been added to the API functions available in Longview Add-In for Office. This API allows the connection to the Longview server to be coded using SSO authentication. This API can be used with the new function Connection.SetLongviewInfo which can be used to set the SSO connection properties of the connection object before passing it to API.ConnectWithSingleSignOn. For more information see the Longview Add-In for Office Guide. |
Longview Platform
Enhancement | Description |
|---|---|
LV-7025 | Longview has improved the security of the forget password functionality in Longview Dashboard to prevent user’s email boxes from being spammed. |
LV-7026 | Longview has improved the security of the forget password functionality in Longview Dashboard by reducing the ability to determine which email addresses are valid. |
Longview Tax – Pillar Two
Enhancement | Description |
|---|---|
LV-6640 | Pillar Two now includes hierarchy editors for GloBE income and GloBE covered taxes accounts. |
LV-6758 | Pillar Two now includes an account hierarchy, hierarchy editor, input app, and report to support GloBE revenue. |
LV-6759, LV-6970, LV-6974 | Pillar Two now supports automation, including:
|
LV-6785 | Pillar Two manage constituent entities now supports export and import. |
LV-6881 | Pillar Two now supports managing temporary differences including:
|
Issues Resolved in Longview 23.1
Longview 23.1 contains issues resolved for the following components:
- Installation and Supported Platforms
- Longview Add-In for Office
- Longview Application Framework
- Longview Data Servers
- Longview Designer
- Longview Platform
- Longview Smart Client
- Longview Close
- Longview Solutions Framework
- Longview Tax – Multi-Regional Provision
- Longview Tax – Pillar Two
- Longview Tax – Tax Provision
- Longview Transfer Pricing
Installation and Supported Platforms
Issue | Description |
|---|---|
LV-6363 | Users were able to enter an invalid character in the French Dimension Description field in the Longview Installer. |
LV-7668 | The license agreement in the Longview Installer was not displaying correctly for some special characters. |
LV-7675 | A Microsoft runtime library was missing in our TCP web installation which was included to avoid issues if that library file was missing from a customer's system. |
LV-7689 | A Microsoft runtime library was missing in our Longview Web Services installer which was included to avoid issues if that library file was missing from a customer's system. |
Longview Add-In for Office
Issue | Description |
|---|---|
LV-6312 | Data extract would result in an unexpected error when querying schedule leaf data. |
LV-6695 | In some cases, Longview Add-In for Office workbook refresh took longer to complete than expected. |
LV-6961 | Connecting to a Tidemark system through Longview Add-In for Office without entering a username or password returned an unexpected error message. |
LV-6697 | Longview Add-In for Office was falsely showing as connected to the server in the status bar when a saved workbook was opened. |
LV-7239 | When connecting as a Tidemark authenticated user after connecting with a SSO authenticated user, the user received a general error and was not able to connect. |
LV-7570 | Longview Add-In for Office displayed an improper error message when connecting with a SSO user that did not exist in the Longview database. |
Longview Application Framework
Issue | Description |
|---|---|
LV-6511 | Longview Application Framework OnError command would generate subfolders when no errors occurred. |
LV-7140 | Longview Application Framework would crash when the procedure contained invalid commands. |
LV-7656 | In some cases, the SYNCHIER command would cause corrupted memory issues which would cause the Longview Application Framework procedure to crash. |
LV-7669 | The Application Framework commands GET DATAAUDITTRAIL, GET METADATAAUDITTRAIL and GET MAPS have been updated to create the specified target folder if the target folder does not exist. |
Longview Data Servers
Issue | Description |
|---|---|
LV-1507 | The DELETE DATA command did not delete the schedule data when TOTAL was used in the data area spec. |
LV-7586 | Workflow schedule data area was locked when the SWFLockScheduleData attribute was set to FALSE. |
LV-7604 | Import and export were importing and exporting the LV_AUDIT_METADATA table when the USE_AUDIT_METADATA parameter in the lvsrvr.cfg file was set to FALSE. |
Longview Designer
Issue | Description |
|---|---|
LV-1537 | Import Apps in Longview Designer displayed the warning message for the Field Delimiter on the wrong field. |
Longview Platform
Issue | Description |
|---|---|
LV-1733 | The Sign On dialogs were not fully translated to French when launched from the Start Menu. |
LV-6190 | In some cases, Longview Application Administrator displayed an incorrect error message when the connection was lost during a restatement. |
LV-6639 | When changing the password, server returned “Old password does not match” error if the old password contained a percentage sign (%). |
LV-6932 | The listing of single apps in a panel (<%[[APP, AppName]]%>) would not display the single app in the legacy dashboard when the FILES_CUSTOM_ROOT_PATH was set. |
LV-6963 | When resetting the restatement warning in Server Manager, the message displayed did not indicate it was successful. |
LV-7141 | Large Journal Entry queries took a long time to complete. |
LV-7333 | Setting the server configuration parameter DOCUMENTATION_DEPLOYMENT to EXTERNAL would cause Longview Dashboard Designer to crash when working with the Documentation card. |
LV-7427 | A blank file was opened when attempting to view import/export logs through Longview Server Manager. |
Longview Smart Client
Issue | Component | Description |
|---|---|---|
LV-6614 | Report Viewer | When typing in the field to change symbol selection, the field autocompleted before the user completed typing the name of the symbol. |
Longview Close
Issue | Description |
|---|---|
LV-6906 | The discontinuation of an operation app was causing a duplicate value in the (DiscOps_Calc) data view for the beginning and ending cash flows. |
Longview Solutions Framework
Issue | Description |
|---|---|
LV-7135 | Generic data PUT REST API now correctly executes using the FULL method, replacing all data in the target area with the data supplied in the request body. |
Longview Tax – Multi-Regional Provision
Issue | Description |
|---|---|
LV-6687 | In Tax Multi-Regional Provision (ASC/US GAAP), the rate reconciliation would not correctly calculate in cases where an entity had no net income before tax, but had one or more temporary differences. |
LV-6743 | In Tax Multi-Regional Provision (IAS/IFRS), default TARF account mappings for net benefit of region elements have been corrected to MSP_DefTax_IAS. This affects new installs only. |
LV-6813 | In Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), current tax forecast automation would reverse the current tax amount for accounts which were not automated but had a forecast method of 'Annualize' or 'Prior Year'. |
LV-7010 | In Tax Multi-Regional Provision (ASC/US GAAP), interim deferred tax classification would clear the classification values of other entities in the same regional group, when the calculation was triggered by a subset of entities in the regional group and the regional group is using group-based classification. |
LV-7032 | In Tax Multi-Regional Provision (ASC/US GAAP), interim discrete item automation event rules, for changes in tax rates and apportionment factors, have been corrected to trigger on period IPTAXPER instead of CYTAXPER. This affects new installs only. |
LV-7205 | In Tax Multi-Regional Provision (ASC/US GAAP), the rate reconciliation event would fail with a lock conflict if input app SS0201 - Current Provision was kept open after data was submitted. |
LV-7532 | In Tax Multi-Regional Provision (ASC/US GAAP and IAS/IFRS), an error would occur when deploying tax planning while assigning reports and apps to planning categories. |
LV-7566 | In Tax Multi-Regional Provision (IAS/IFRS), netting adjustment for long-term recognised deferred tax liabilities and assets were sometimes not calculated for partnership entities, requiring the calculation to be manually triggered. |
Longview Tax – Pillar Two
Issue | Description |
|---|---|
LV-6928 | In some instances, changing the Ultimate Parent Entity in the MNE Group Parent setting for multiple entities would result in an incorrect validation error. |
Longview Tax – Tax Provision
Issue | Description |
|---|---|
LV-6554 | When Entities were imported into Longview Tax, the symbol priority was incorrectly set to 0 if the symbol already existed in an alternate hierarchy. |
LV-6813 | In Tax Provision (ASC/US GAAP and IAS/IFRS), current tax forecast automation would reverse the current tax amount for accounts which were not automated but had a forecast method of 'Annualize' or 'Prior Year'. |
LV-6972 | In Tax Provision (ASC/US GAAP), the Interim Accounts editor incorrectly displayed the TaxIncomeBeforeLoss_ASC hierarchy in the Regional tab. |
LV-7566 | In Tax Provision (IAS/IFRS), netting adjustment for long-term recognized deferred tax liabilities and assets were sometimes not calculated for partnership entities, requiring the calculation to be manually triggered. |
Longview Transfer Pricing
Issue | Description |
|---|---|
LV-7503 | Profitability analysis automation would incorrectly calculate when group and entity override existed for the same entity with different source settings, and the calculation was triggered independently for the group and entity override source. |
Hardware and Software Requirements
This chapter contains information on these main topics:
Note: Third party components and versions, such as operating systems, browsers, etc., no longer in mainstream 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
- Data Server OS and RDBMS
- Web Server
- Data Server Web Services
- Longview Grid Server
- HTTP Proxy Server
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 2019 Oracle 19c |
| Windows Server 2019 | 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 19 or OpenJDK 19 |
Windows Server 2019 | Oracle JDK 17 (LTS), Oracle JDK 19 or OpenJDK 19 |
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.16 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 | SQL Native Client 11.0 |
Windows Server 2019 | SQL Native Client 11.0 |
Note: You must install the SQL Native Client 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 19 or OpenJDK 19 | Oracle JDK 17 (LTS) Oracle JDK 19 or OpenJDK 19 |
Web browser | English | French |
Server operating system | English | English |
RDBMS | English | English |
Web server | English | English |