What’s new in this release?

LiveCompare 2024.1 patch 4

LiveCompare 2024.1 patch 4 includes the following new features:

Templates

Platform

  • For ALM Test Repositories, the Search Test Repository action’s Result dataset includes TEST_LIST_ID, TEST_LIST_NAME, TEST_LIST_PATH fields. These store the ID, name, and path of the execution list or test set for each test hit.

  • By default, the Execute Test Cases action waits for 30 seconds after it checks in the test event, and before it checks out the test execution to run it. You can adjust this value using a registry setting.

  • The Search Test Repository action includes a Test Set Fields property. This property allows you to retrieve USER_LABEL values for ALM test sets into the action’s Result dataset.

User interface

File uploads

Fixes

  • We fixed a problem which caused the Smart Impact app to report a ‘database is locked’ error if you ran more than one app variant in parallel using the same analysis system.

  • We fixed a problem with the Smart Impact app’s Find Most-at-Risk Objects workflow, where its Analyze Object Links action’s Recommended Threshold property had the value 10 rather than 0.

  • We fixed a problem with the Test Audit app which caused an error in the Execute SQL action if the app found no test executions.

  • We fixed a problem with the Test Audit app which caused the Treemap report to fail with a ‘more than one row with the same id’ error.

  • We fixed a problem with the Test Quality Audit app where the Search Test Repository action caused an Unknown Termination error.

  • We fixed a problem with the Collect Performance History Data action which caused an ’ invalid vector subscript’ error in some cases.

  • We fixed a problem with the Search Test Repository Cache action which caused the following error: ‘SqlTable. IRecSet already set’.

  • We fixed a problem with the Search Test Repository action for Certify Test Repositories where it returned only one test hit if more than one search term matched the same test.

  • We fixed a problem with the Search Test Repository action for Solution Manager Test Repositories, which caused the following error: The JSON value of length 413527848 is too large and not supported.

  • We fixed a problem where LiveCompare incorrectly identified RFC functions as programs in downloaded performance history data.

LiveCompare 2024.1 patch 3

LiveCompare 2024.1 patch 3 includes the following new features:

Apps

  • The Smart Impact app supports the processing of CDS View (DDLS) extension views. If your LiveCompare installation uses custom SAP roles, you will need to add table DDLS_RIS_INDEX to your custom roles to allow the Smart Impact app to support CDS View (DDLS) extension views.

Performance

Fixes

  • We fixed a problem with the Analyze Object Links action which caused a crash dump in the Smart Impact app.

  • We fixed a problem with the Compare Objects action and Quick Compare Wizard where they didn’t support Report Variants (VARX) with more than two parts in their name. For example, they incorrectly reduced Report Variant ZCD_COPY_N_IMPORT_NEW VARIANT1 ABC to ZCD_COPY_N_IMPORT_NEW VARIANT1.

  • We fixed a problem with the Search Test Execution action for qTest Test Repositories, which caused an ‘item already exists’ error if a qTest test covered more than one searched for executable.

  • We fixed a problem with the Execute Test Cases action where it returned 0 rows for Execution Lists that contained no automated tests.

  • We fixed a problem with the Search Test Repository action for Certify Test Repositories which caused a ‘Could not find file’ error.

  • We fixed a problem with the Search Test Repository action where it caused a low physical memory error when searching a large Tosca Test Repository.

  • We updated the Search Test Repository action to find modules with the SAPNW Control Framework when searching BSP Application (WAPA) objects using its legacy UI5 test search.

  • We fixed a problem with the Uses What and Uses What (Read Only) actions where they didn’t find links for BADI classes called dynamically in transactions.

  • We fixed a problem with the Uses What (Read Only) action where its LINK_TYPE counts in its Tree dataset did not match those produced by the Uses What action.

  • We fixed a problem with the Where Used and Where Used (Read Only) actions where they didn’t find links for BADI classes called dynamically in transactions.

  • We fixed a problem with the Where Used (Read Only) action where in some cases its Tree dataset was missing some LINK_TYPE entries.

  • We fixed a problem where the Tricentis LiveCompare Application Server service terminated during initialization, following an upgrade from LiveCompare 4.6 where the userdata directory included a ReleaseStreams.xml file.

  • We fixed a problem where some icons in the apps user interface were not visible if the LiveCompare server did not have access to the internet.

  • We fixed a problem with the SSO logout screen where its GUI components were misaligned.

LiveCompare 2024.1 patch 2

LiveCompare 2024.1 patch 2 includes the following new features:

Platform

Test Repositories

Impact analysis

  • The TypesToFind field in the Configuration - Impact Analysis screen includes a check box for the IDOC (Intermediate Document) object type. This is deselected by default.

Debug logging

Fixes

Miscellaneous

  • We updated the Product version and File version details for the Tosca.WGI.ToscaLocal.dll component in the <LiveCompare install dir>\server\bin\wgi\tosca_local directory.

LiveCompare 2024.1 patch 1

LiveCompare 2024.1 patch 1 includes the following new features:

Templates

Projects

  • When you create a new project, its Start Date is set to today’s date and its End Date is calculated based on the project’s type.

Platform

  • Collect Daily Usage Audit Data actions retrieve performance history data into the specified RFC Destination’s DUA tab, replacing the ‘Update Data’ button. This provides greater visibility, especially when retrieving a large amount of performance history data.

  • Collect Performance History Data actions retrieve performance history data into the specified RFC Destination’s PHD tab, replacing the ‘’Update Data button. This provides greater visibility, especially when retrieving a large amount of performance history data.

  • The Custom ALM Command action supports ApiKey authentication.

Test Repositories

  • The Local integration method for Tosca Test Repositories allows LiveCompare to connect directly to Tosca Commander installed on the LiveCompare server. This provides a performance improvement over the original REST integration method.

  • The Search Test Repository action has been updated to find Tosca Fiori tests by finding modules that use the SAPUI5 control framework, and then searching the modules’ associated test cases.

  • The Test Connection screen for a local Tosca Test Repository in the LiveCompare studio shows the number of modules and test cases in the Tosca workspace that are not synchronized with the common repository. Unsynchronized modules and test cases will not appear in the Search Test Repository action’s search results.

RFC Destination DUA tab

RFC Destination PHD tab

  • The PHD tab for RFC Destinations includes a ‘Save’ button to allow you to save the retrieval and schedule details.

  • The PHD tab for RFC Destinations no longer includes an ‘Update Data’ button. You can use the Collect Performance History Data action to retrieve performance history data for an RFC Destination.

  • The PHD tab for RFC Destinations allows you to schedule the retrieval of performance history data for the first day of each month.

Installation

Fixes

  • A problem with the Projects screen has been resolved, where a project’s start and end date were not saved.

  • A problem with the Compare Objects app has been resolved, where some HCPR objects could not be compared.

  • A problem has been resolved which caused LiveCompare to crash if a process tried to write to a log file while you were exporting log files.

LiveCompare 2024.1

LiveCompare 2024.1 includes the following new features:

Apps

  • The Test Quality Audit Learning app simulates a run of the Test Quality Audit app using a predefined set of data. It may be used for demonstration and training purposes and does not require LiveCompare’s SAP RFC libraries to be installed. The app is installed using the LiveCompareLearningApps.exe package in the LiveCompare distribution directory.

  • The sliders in the Adder app have been updated to have a minimum value of 0, a maximum value of 20 and a step value of 1. This prevents rounding of integer values (in the correct range) that are entered in the edit fields.

  • In the Cross System Impact Analysis and Smart Impact apps’ Function Details report, the App Area Details spreadsheet’s TEST column displays the number of optimal tests found for each object in the specified Test Repository.

  • The Cross System Impact Analysis, Smart Impact and Used Objects apps no longer reference the USR02 SAP table.

  • The Smart Impact app reports on known test gaps. These are most-at-risk objects that are not expected to have tests in the specified Pipeline’s Search Test Repositories. Known test gaps are specified in an External Data Source set the Pipeline’s Known Test Gaps field.

  • The Smart Impact app supports OData Services (IWSV).

  • The Smart Impact app’s Search Test Repository and Create Test Execution workflow has been split into two workflows named Integrate Test Repos and Filter Tests. This allows the app to continue running if the Filter Tests workflow generates an error.

  • The Test Audit app’s Test Execution Details spreadsheet reports the date and time when each test run was last started.

  • The Test Audit app has been modified to use the updated Search Test Execution action.

  • In the Test Quality Audit app’s results, the Test Coverage and Gaps bar chart lists the test coverage and gaps for each of the specified Most-at-risk Search Test Repositories. Coverage is the number of used executables that are covered by at least one test. Gaps is the number of used executables that are not covered by at least one test.

  • Notification emails sent to a user who runs an app have been updated to include the app’s result URL for apps that were successful, and the app’s error message for apps that failed. The app variant name is included in each case.

Projects

  • Projects have start and end dates, which are set by a LiveCompare administrator when each project is created.

  • Each LiveCompare project type includes additional documentation related to the associated SAP lifecycle event.

Templates

SQLite database encryption

  • The Update LiveCompare Service Configuration Wizard allows SQLite databases stored in the user data directory to be encrypted, re-encrypted or decrypted using a random seed value generated by LiveCompare, or your own seed value. Encrypted databases may not be examined or modified by SQLite analysis tools.

  • The Administration screen’s Database section displays the encryption status for LiveCompare’s SQLite databases.

  • If LiveCompare is configured to encrypt SQLite databases, the Administration screen allows the database key used for the encryption to be exported to an XML file.

Before changing LiveCompare’s database encryption status, either:

  • From Unencrypted to Encrypted, or

  • From Encrypted to Re-encrypted, or

  • From Encrypted to Unencrypted

you will need to back up the user data directory on your LiveCompare server.

Parallel impact analysis

Most-at-risk calculation

  • The Analyze Object Links action includes an Application Components property, which you should set to the Result dataset returned by the Get Application Components action. This data allows the Analyze Object Links action to return most-at-risk executables that are in the same application area as the changing object.

  • The Smart Impact app returns most-at-risk objects that are in the same application area as the impacting changing object. You will need to run new app-based variants of the Smart Impact app to view these results.

AI

  • LiveCompare’s use of AI is documented here.

Platform

  • Create Change Request URLs actions allow report URLs to be added to the Attachments section of a ChaRM change request.

  • Custom ALM Command actions allow custom commands to be run against an ALM Test Repository. Please do not use this action unless you are asked to by Tricentis Technical support.

  • Expand Table Keys actions expand a table key object into its key fields and values.

  • Get Application Components actions retrieve the application components for a set of objects from the specified RFC Destination.

  • The Analyze Object Links action has been updated to work with business-critical non-SAP object types in addition to the CLAS, PROG, TCOD and WAPA object types.

  • The Convert Data action’s PipelineToKnownTestGaps conversion type converts a Pipeline to its Known Test Gaps External Data Source.

  • The Convert Data action’s ‘PipelineToSearchTestRepos’ conversion type may be used to convert a Pipeline parameter or dataset to a Table dataset containing the Pipeline’s distinct Most-at-risk Search Test Repositories.

  • The Convert Data action’s PipelineToTestRepo conversion type has been renamed to PipelineToTestRepos and returns a distinct set of results.

  • The Convert Data action’s ‘Table_TestRepository’ conversion type may be used to convert the first row and column of a table to a Test Repository dataset.

  • The Create Object Links Cache action has been updated to include table /ICORP/YVPR001. This table contains a mapping between transactions and programs.

  • The Create Object Links Cache action has been updated to read the SAP tables required by the Get Application Components action.

  • The Create Object Links cache action has been updated to collect links for OData services from the /IWBEP/I_MGW_SRH SAP table on the analysis system.

  • The Create Object Links cache action has been updated to collect links for background job data.

  • The Create Requirements action for ALM Test Repositories has been updated to convert ‘$%@’ path separators in the Source parameter’s NAME column to ‘/’ in the Result dataset’s REQ_NAME column. The action therefore returns simpler requirement names.

  • The Create Test Execution action allows existing ALM execution lists to be reused.

  • The Search Test Execution action’s Source table schema has been updated to allow it to be set to the Result dataset returned by the Read Test Repository action.

  • The Search Test Execution action’s Result table schema has been updated.

  • The Search Test Execution action’s Result dataset includes a column named LAST_RUN_DATETIME, which stores the date and time when the execution item was last started.

  • The Search Test Repository action finds focused build tests when searching an SAP Solution Manager Test Repository’s Test Plans.

  • The Search Test Repository action has been updated to search both Tile Modules and Fiori Modules when performing a legacy search using a Tosca Test Repository.

  • The Uses What action in has been updated to include DYNX objects as PROGs in its TCOD PROG Pairs dataset when the Extractor Mode property is set to true.

  • The Uses What action has been updated to read table /ICORP/YVPR001 when its Extractor Mode property is set to true. This table contains a mapping between transactions and programs.

  • In the Configuration - General screen the FioriLaunchpadTransactionFieldNames field may be used to specify the possible column names in the /UI2/FLPCA export that contain transaction codes (for example, VA01).

  • The DisableTableContents setting has been moved from the Configuration - Impact analysis screen, and it is now available for individual pipelines. The setting is used by the following apps: Smart Impact, Test Audit, and the following Impact Analysis workflows: Released Request Impact Analysis, Smart Impact Analysis, SmartImpact_ChaRM.

  • LiveCompare’s internal table that maps transactions to programs has been updated to allow the screens associated with transaction FK93 to be retrieved and compared.

  • Apostrophes may not be used in RFC Destination, Test Repository and Pipeline names set in the Apps user interface, to match the naming restrictions used in the studio. Apostrophes used in Pipeline names prevent the Commit Configuration process from running to completion.

User Interface

  • The App Cockpit screen has been updated to use Data Grids for its My Variants and My Results tables.

  • In the App Cockpit screen, the order of the action buttons in the Variants table has been changed to Edit, Run, Share. This allows variants to be edited more easily.

  • The Contacts screen in the Apps user interface has been updated to use a Data Grid.

  • If the settings in the Guided Configuration screen’s email tab are incorrect, LiveCompare displays an error message that list the possible causes of the problem.

  • In the Edit Pipeline screen, the ‘Most-at-risk Hits Execution Test Repositories’ label text has been corrected.

  • In the Email Results screen, the ‘Send’ button is disabled if no users are entered in the ‘To’ field.

  • The Email Results screen allows email addresses set in the ‘To’ field to be deleted.

  • The license screens in the apps and studio user interface no longer display the LiveCompare product version.

  • LiveCompare’s Profile screen and About dialog include an internal build number for use by Tricentis only.

  • When an Administrator creates or edits a project in the Apps user interface, the details screen is displayed in line with any additional entries on the Projects screen.

  • In the Share App Results screen, the ‘Send’ button is disabled if no users are selected in the ‘Share with’ field.

  • The Test Connection screen for RFC Destinations in the apps and studio user interface no longer list the AUT (ABAP Unit Tests) component.

  • The Variant screen has been updated to use button and control styles that match the other apps user interface screens.

  • The Data Cleanser’s user interface has been updated to match other apps user interface screens.

  • For consistency, the background color of each of LiveCompare’s user interface screens has been changed to white.

  • The toolbar icons in the apps user interface screens have been updated.

  • In the Apps user interface, the Project icons for ‘Editors’, ‘Consumers’ and ‘Administrators’ have been updated.

  • Each chart in the LiveCompare Dashboard has a ‘Show as table’ button, which displays the chart’s data in a Data Grid.

  • LiveCompare displays a user-friendly error message when sending emails if an invalid SMTP server is specified. The message is: Error initializing email client: No such host is known, which replaces the more cryptic message: A non-recoverable error occurred during a database lookup.

  • The ‘Shutdown Server’ function which stops the Tricentis LiveCompare Application Server service has been renamed to ‘Stop Service’.

  • The Feedback link in the apps UI screens has been removed as the feature is no longer supported.

Accessibility

  • The color scheme of the consumer interface has been upgraded from Cornflower Blue to Royal Blue to improve the contrast ratios between UI components and their backgrounds.

  • The background color of the screens in the Apps user interface has been made lighter, increasing the contrast with the text.

  • In the apps user interface screens, the contrast ratio between user interface components and their backgrounds is at acceptable levels for accessibility.

  • The App Cockpit screen has been updated to include headings for each of its table columns.

  • The App Cockpit screen displays ‘Skip to Variants datagrid’ and ‘Skip to Results datagrid’ links during keyboard navigation.

  • If the tab key is used in the App Cockpit screen’s Create a Variant modal dialog, keyboard focus remains within the dialog.

  • In the Apps screen, text in the app tiles is shown correctly when the display is zoomed.

  • Tiles in the Apps screen may be navigated using the tab key.

  • In the apps user interface screens, pressing the tab key displays a ‘Skip to main content’ link. Selecting the link moves the keyboard focus to the first control in the main part of each screen, skipping the peripheral controls.

  • The Details links in the Service Status screen have been updated to state ‘Show the <error or warning> details for Pipeline <Pipeline name>’.

  • In the Variant screen, the Distribute Results To field may be read by a screen reader.

  • After running or aborting a variant in the Variant screen, keyboard focus remains on the Run or Abort variant button.

  • User interface elements in the Apps, LiveCompare Dashboard and Service Status screens are shown correctly if the browser display is zoomed to 200%.

  • Text and icons in the consumer interface are displayed using contrast ratios that are at acceptable levels for accessibility.

  • The icons in the Data Cleanser utility have been updated to improve their contrast ratios.

  • The icons in the Pre-install check program have been updated to provide an acceptable contrast ratio for accessibility.

  • LiveCompare’s setup and uninstall program logos have been updated to use a contrast ratio that is at an acceptable level for accessibility.

  • Checkboxes in the App Cockpit screen have tooltips.

  • Search icons in LiveCompare’s Data Grids have tooltips.

  • Icons in the apps user interface have a clearly visible outline when navigated to using the tab key.

  • The group headings in the Guided Configuration - Email screen may be read by a screen reader.

Security

  • The ‘Advanced’ button in the Edit External Data Source screen for Access, CSV and Excel External Data Sources has been removed. This prevents the connections string for these External Data Sources from being modified, which could allow access to files stored anywhere on the LiveCompare server.

  • API tokens generated for External Data Source REST APIs, workflow REST APIs, and Web Services are more secure in this release. They are 32-bytes (256 bits) long and generated using the Windows CryptoAPI that produces secure random data.

  • When an AAQ Select List is saved in the apps user interface its values are checked against an XML schema definition file for IMG Select Lists, and an error message is displayed if there are any schema differences. This protects against XML injection attacks for AAQ Select Lists.

  • When an IMG Select List is saved in the apps user interface its values are checked against an XML schema definition file for IMG Select Lists, and an error message is displayed if there are any schema differences. This protects against XML injection attacks for IMG Select Lists.

  • Users’ email addresses are encrypted in the \<user data dir>\private\Users.xml file on the LiveCompare server.

  • LiveCompare’s Workflow Gateway Interface (WGI) programs are protected against XML injection attacks.

  • In many places in the code, LiveCompare is protected against XML injection attacks.

Test Repositories

  • If the DontDeleteExportedTests setting is in the ALM section of the Configuration - Test Repository screen is set to X, temporary files created by the Search Test Repository action when using the default ALM search method will not be deleted. In earlier releases of LiveCompare, this setting was named ALMKeepExportedTempFiles.

  • To avoid timeout (499) errors when integrating LiveCompare with Tosca, Tosca Server’s Gateway Service must be updated as described in this knowledge base article.

  • If the Api Type SAP Module check box is selected for a Tosca Test Repository, the Search Test Repository action matches SEARCH_TERM values from its Source table against custom modules associated with Fiori apps to find the associated tests. The custom modules have an ApiType attribute that begins with ‘sap.’.

  • The ReusableTestStepBlocksDepth in the Configuration - Test Repository screen’s Tosca section allows you specify to depth to which a live Tosca Test Repository will be searched by the Search Test Repository action to find test cases that use Reusable Test Step Blocks.

Pipelines

  • Pipelines include a Known Test Gaps field which may be set to an External Data Source containing a set of objects that are not expected to have tests in the Pipeline’s Search Test Repositories.

Workspaces

  • The Workspaces screen uses a ‘data grid’ to list the workspaces registered on the LiveCompare server, or in the currently selected ‘resource group’.

ChaRM integration

  • LiveCompare’s ChaRM integration has been updated to include a configuration which allows multiple ChaRM actions to invoke the same workflow, and a ChaRM action to invoke multiple workflows.

  • The SmartImpact_CharM workflow has been updated to store its report URL in the Attachments section of the ChaRM document that triggered the impact analysis.

ServiceNow integration

Salesforce integration

  • Salesforce integration has been removed in this release.

Background jobs

OData services

Debug logging

  • The Logs screen in the LiveCompare studio displays log files using a Data Grid, which allows the entries to be sorted, filtered and grouped. The log file entries are displayed in descending date order so that the most recent log file is shown at the top of the grid. Individual log files may be downloaded and sent to Tricentis Technical support for analysis.

  • The AdditionalCrashDumpSearchPaths setting in the Configuration - General screen may be used to additional paths to search when locating crash dumps. All crash dump files found are presented in the user interface.

Service Status and Dashboard databases

Installation

  • LiveCompare has been updated to require SAP NetWeaver RFC SDK 7.5.0 Patch 13. See here for details.

  • The Pre-install Check program tests for disabled insecure versions of TLS (1.0 and 1.1) and enabled secure versions of TLS (1.2 and 1.3). The disabled test reports a warning if least one checked version is not disabled; the enabled test reports a warning if all the checked versions are disabled.

  • The Pre-install Check program has been updated to check for OLEDB SQL Driver version 19.

  • The Pre-install Check program no longer checks for the Microsoft Visual Studio 2013 x64 Runtime, as it no longer required by the SAP RFC SDK libraries used by LiveCompare.

  • The Configuration Wizard’s SAP RFC Library screen requires that the sapnwrfc.dll file is selected from the nwrfcsdk/lib directory in order to load the required SAP NetWeaver RFC SDK library files. This protects against errors that may result if SAP changes the names of any of the library files.

  • The Configuration Wizard has been updated to display a user-friendly error message if the specified LiveCompare service account is locked or disabled.

  • When an apps package is installed, LiveCompare backs up the <user data dir>\public\externaldatafiles directory and installs the package’s external data files to the <user data dir>\public\externaldatafiles directory, overwriting any existing files.

  • Files used by an app package’s External Data Sources are backed up during an upgrade. If you have modified any of an app’s packages external data files, these should be restored following an upgrade, as described here.

  • The default LiveCompare authorization object /ICORP/LC_CORE_AUTHS3 includes the following tables to support the retrieval of ODATA services and background jobs: TBTCP, /IWBEP/I_MGW_SRH, TBTCO.

Authorizations

  • The Test Connection results screen for RFC Destinations has been updated to include tables /SALM/TM_TD_STEP and BADI_SPOT in its Required Authorizations section. These were added to the S_TABU_NAM authorization object for the default LiveCompare role.

  • Table USR02 has been removed from the default LiveCompare authorization object /ICORP/LC_CORE_AUTHS3.

Fixes

  • A problem with the Code Watch app has been resolved where the app retrieved all available ChaRM requests if no ChaRM requests were provided.

  • A problem with the Smart Impact app has been resolved where the Check Prerequisites workflow passed although the Analysis System’s Object Links Cache database had a status of ‘Incomplete’.

  • A problem with the Test Audit app has been resolved where its Search Test Executions workflow did not find any test hits.

  • A problem with the Test Audit app has been resolved which caused a ‘No Changing Objects’ error if no most-at-risk objects were found.

  • A problem with the Test Quality Audit app has been resolved which caused a ‘LinkDb. Bad symbol’ error if no most-at-risk objects were found.

  • A problem with the Analyze Impact DIA workflow has been resolved which caused a ‘Missing or empty parameter: RfcDestination’ error.

  • A problem with the Monitor PHD Collection workflow has been resolved which caused an error in its Execute SQL if no performance history data had been collected for an analyzed RFC Destination.

  • A problem with the Remove Objects to Ignore workflow has been resolved which caused a Regular Expression error in the Filter by Patterns action.

  • A problem with the Analyze Object Links action has been resolved which caused an Unknown Termination error if the action was run without an RFC Destination.

  • A problem with the Compare Objects action has been resolved where the table data for views whose names started with PC could not be compared.

  • A problem with the Compare Objects action has been resolved which caused a ‘table has bogus data in its keys’ error.

  • A problem with the Compare Objects action has been resolved which caused an ‘OBJECTS_OBJREF_NOT_ASSIGNED_NO’ error when comparing smart forms.

  • A problem with the Create Hierarchy Report action has been resolved which caused an ‘unknown object type=ELEM_CHARATTRS’ error.

  • A problem with the Create Object Links Cache action has been resolved which caused a ‘no such column CDAT’ error in the SAP HANA Upgrade Analysis app.

  • A problem with the Create Test Execution action has been resolved which caused an ‘Object reference not set to an instance of an object’ error if its Source table contained a test ID that could not be found.

  • A problem with the Search Test Repository action for ALM Test Repositories has been resolved where the action crashed if it found an attachment that it could not open.

  • A problem with the Search Test Repository action for ALM Test Repositories has been resolved which caused a crash if the WgiLogFiles=X registry setting was not present.

  • A problem with the Search Test Repository action for Certify Test Repositories has been resolved where the action produced duplicate results.

  • A problem with the Search Test Repository action for SAP Solution Manager Test Repositories has been resolved where the action did not read all SALM table rows.

  • A problem with the Search Test Repository action for Tosca Test Repositories has been resolved where the TEST_PATH column in the action’s Result dataset was missing a leading /.

  • A problem with the Search Test Repository action for Tosca Test Repositories has been resolved where the Tosca hierarchy was not searched recursively to find items that used reusable test step blocks.

  • A problem with the Commit Configuration process has been resolved where RFC Destinations using a performance history data External Data Source were converted to RFC Destinations using the LiveCompare RFC collection method.

  • A problem with the Apps Monitor screen in the Apps user interface has been resolved where report links were not exported to Microsoft Excel.

  • A problem with the Email Results screen has been resolved where an email address was not accepted if it was entered again after clicking the browser’s Back and Forward buttons.

  • A problem with the Project screen in the Apps user interface has been resolved where the help for the ‘S/4 HANA Feature Pack’ panel was linked incorrectly.

  • A problem with the ExternalDataSource dialog has been resolved where an External Data Source folder disappeared when selected if another External Data Source had the same name.

  • A problem has been resolved where a copied workflow could not be registered as a REST API if the original workflow was also registered as a REST API. The REST API files were replaced in the REST API folder for the original workflow, rather than being recreated for the new workflow.

  • A problem with running workflows as REST APIs has been resolved where the status.lcrs endpoint was not available after a successful workflow run.

  • A problem has been resolved where API tokens were not reloaded when the Tricentis LiveCompare Application Server service was restarted.

  • A problem with the LiveCompare Essential and Professional licenses has been resolved where these licenses did not allow a user to run workflows.

  • A problem with the Process Runs screen has been resolved which caused an ‘Invalid input‘ error if the ‘Refresh Now‘ button was clicked before the screen had finished loading.

  • A problem with the Tosca Test Connection feature has been resolved where a ‘Suspicious pathname’ exception was raised, and written to the tccontst_<YYYYMMDD>_<HHMMSS>.txt log file. This occurred because the path to a temporary file included both forward and backward slashes. Paths are now normalized to protect against XML injection.

  • A problem has been resolved which caused the Tricentis LiveCompare Application Server service to crash if the SAP Data Mask External Data Source had an invalid schema.

  • A problem has been resolved which allowed an administrator to rename a workspace so that the name included apostrophes. This prevented resource groups from being created or edited. If you have any workspaces with apostrophes in their names, these workspaces will need to be renamed to allow resource groups to work correctly.

Deprecated features

  • Several workflow components are deprecated in this release and will not be available in future LiveCompare releases.

Documentation

  • LiveCompare’s online help is no longer installed with the software. Instead, help links in the user interface redirect to the LiveCompare help stored on the Tricentis documentation server. This brings LiveCompare in line with other Tricentis products.

  • The LiveCompare security help topic describes the security features available for the LiveCompare server.

  • The Secure your LiveCompare server help topic provides tips on how to make your LiveCompare server more secure.

  • The Smart impact analysis runtime performance help topic describes the factors that influence the time taken for an impact analysis to complete.

  • The Used, impacted and most-at-risk help topic describes used, impacted and most-at-risk objects as used in LiveCompare’s impact analysis reports.

  • The Guided Configuration - Pipelines help topic has been updated to warn against using the Commit Configuration feature if you have customized Create Object Links Cache or Create Test Repository Cache workflows.

  • The Install LiveCompare packages section of the LiveCompare installation and configuration Guide has been updated to state that the LiveCompareLearningApps.exe package requires that the LiveCompareApps.exe package is also installed.

  • The Dashboard report treemaps help topic has been corrected so that it no longer mentions the Smart Impact Analysis workflow.

  • The Send Email actions help topic has been corrected so it no longer states that the Zip property must be set to ‘true’ in order to allow attachments to be sent with the email.

  • A grammatical error has been corrected in the automated email that LiveCompare sends when users change their password.

  • LiveCompare no longer includes the Installation and Configuration Guide as a Word document. Instead, it is available here in the online help.

Miscellaneous

  • The following components have been updated to the versions in parentheses: boost (1.84.0), jQuery (3.7.1), sqlite (3.45.1).

How to use LiveCompare

Backward compatibility

Release notes