What’s new in this release?

LiveCompare 2025.1 patch 4

LiveCompare 2025.1 patch 4 includes the following new features:

Reports

User interface

File uploads

Fixes

  • We fixed a problem with the Code Watch app where its Get Changing Objects by ChaRM workflow included one of our own RFC Destination names.

  • 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 BW Impact Analysis workflow which caused a ‘Param does not implement fn’ error.

  • We fixed a problem with the Cache IDoc Impact Data workflow where its Create Object Links Cache action deleted the Object Links Cache database’s Symbol.db file. The workflow now uses the Has Valid Object Link Cache Diagnostic action.

  • We fixed a problem where the LiveCompare Dashboard scheduled task crashed if you had not installed the LiveCompareApps.exe package, due to the missing Smart Insights External Data Source.

LiveCompare 2025.1 patch 3

LiveCompare 2025.1 patch 3 includes the following new features:

Templates

  • The Collect SCMON Data workflow in the Tools Templates folder retrieves SCMON data into the specified RFC Destination’s SC_MON tab.

  • The Copy SCMON Data Between RFC Destinations workflow in the Tools templates folder copies SCMON data from a source RFC Destination to a target RFC Destination, overwriting any existing SCMON data in the target RFC Destination’s SC_MON tab. You can use the workflow to copy SCMON data from a QA system’s RFC Destination to an Analysis system’s RFC Destination if the Analysis system isn’t configured to collect SCMON data.

Platform

  • Collect SCMON Data actions retrieve SCMON data into the specified RFC Destination’s SC_MON tab cache. The action retrieves the most recent N months of SCMON data. N is the value set in the action’s Months property.

  • 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.

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

  • The Search Test Repository action for Xray Test Repositories reports a ‘Duplicate test case id’ error if the Test Repository’s External Data Source has duplicate entries in its Test Case Id column.

Fixes

  • 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 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 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 which caused an ‘IRecSet already set’ error in where the action’s Pipeline included more than one Most-at-risk Search Test Repositories.

  • We fixed a problem where LiveCompare took a long time to retrieve performance history data for an RFC Destination. This was caused by LiveCompare reading an SAP table more that once in some situations when determining the type of an object.

  • We fixed a problem where the collection of DUA and SCMON data used a function that wasn’t available on Windows 2019 Server.

LiveCompare 2025.1 patch 2

LiveCompare 2025.1 patch 2 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.

Impact Analysis

Fixes

  • 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 Compare Objects action and Quick Compare Wizard where they couldn’t compare Class (CLAS) objects without descriptions.

  • We fixed a problem with the Compare Objects action and Quick Compare Wizard where they couldn’t compare Class Interface (INTF) objects without descriptions.

  • We fixed a problem with the Convert SAP Objects Test Search action where it didn’t expand BSP Application (WAPA) objects to include text tile search terms.

  • We fixed a problem with the Execute SQL action where the SET RESULT TABLE KEYS command did not replace a Table dataset’s existing keys with the keys you specified.

  • We fixed a problem with the Read SAP Table action when it used the default MultipleQueries Filter Mode. The action only matched the first row in the Filter table with rows from the source table. If the Filter table contained three or more records, the action skipped every other record.

  • We fixed a problem with the Search Test Repository action which caused a ‘Missing ‘SkipCollect’ param’ error for Tosca Test Repositories.

  • We fixed a problem with the Search Test Repository action for Tosca Cloud Test Repositories where references to reusable test step blocks that did not exist caused the action to crash. The action now writes the IDs of the missing reusable test step blocks to the workflow’s log file.

  • We fixed a problem with the Search Test Repository action for Tosca Cloud Test Repositories where the action failed to parse line breaks in test step descriptions.

  • 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 Uses What action where it didn’t process the Patterns table correctly if you set its Expand While Custom property to true.

  • 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 an SQL syntax error in the Get Recently Changed Executables Systems workflow.

  • 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 purge log files feature where it did not automatically purge out-of-date log files in subfolders of the <LiveCompare user data dir>\public\Logs folder.

  • 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.

LiveCompare 2025.1 patch 1

LiveCompare 2025.1 patch 1 includes the following new features:

Operating model

  • The LiveCompare operating model is a high-level description of how to get the most value from LiveCompare as quickly as possible. It covers capabilities, people and process in the context of SAP lifecycle events captured in your SAP roadmap.

Apps

  • You can configure the Smart Impact app to generate a Cross Reference spreadsheet in its Function Details and Testing Details reports. The Cross Reference spreadsheet lists all the impacted or most-at-risk executables for each impactful changing object.

  • In addition to the most-at-risk objects, the Test Audit app identifies all objects impacted by a change, and reports on their test execution status in the specified Most-at-risk Hits Execution Test Repositories.

Platform

  • Find Objects in SC_MON actions match impactful objects against raw SC_MON data that the Read SC_MON Data action has retrieved for an RFC Destination.

  • The Analyze Object Links action’s Write Cross Reference parameter determines whether the action will write impacted executables to the Result Cross Reference dataset. If you set this parameter to true, generating the Result Cross Reference dataset will take a long time if the Source, Tree and Usage Counts datasets contain many records.

  • The Read Performance History Data action’s Include Background Jobs parameter determines whether the action will retrieve background jobs (BKGJ) into the Application Archive and Application Statistics datasets. The default value is false.

  • The Read Test Repository Cache action includes a Search Terms output dataset which includes the search terms written to the Test Repository cache by the Write Test Repository Cache action.

  • The Write Test Repository Cache action’s Search Terms parameter allows you to write a set of search terms to the specified Test Repository cache.

Impact analysis

User Interface

  • We updated LiveCompare’s user interface to use our corporate logos.

  • We reformatted the Add Pipeline screen in the and added bold headings for each section.

  • In the Add Pipeline screen we renamed the Add Pipeline button as Save and added a Cancel button.

  • We simplified the graphic on the My Profile screen.

Accessibility

  • Slider controls in the Variant screen are visible if you use a high contrast theme.

  • Calendar controls in the Variant screen display a pointer icon when you mouse over them.

Security

  • We protected the report viewer URLs against path traversal attacks.

Performance

  • We improved the performance of the Search Test Repository action when it searches for Tosca UI5 test cases, using a Tosca REST Test Repository.

Test Repositories

Fixes

Documentation

Miscellaneous

  • We updated the following components to the versions in parentheses: curl (8.11.1).

LiveCompare 2025.1

LiveCompare 2025.1 includes the following new features:

Apps

  • We updated the SAP HANA Upgrade Analysis app’s SAP HANA Fiori Apps External Data Source for S/4HANA 2023.

  • The Smart Impact app’s Dashboard report includes the Top 5 Application Areas bar chart and the All, Covering and Optimal Tests column chart, taken from the app’s Function Details and Testing Details Excel reports.

  • In the Smart Impact and Smart Impact Learning app’s Function Details report, we renamed the Changed Objects tile to Transport Objects to avoid confusion with the Changed Objects Summary chart.

Projects

  • The Enhancement Pack Upgrade project type assists in performing an SAP upgrade using enhancement packs.

  • When you create a new project, LiveCompare sets its start date to today’s date and calculates its end date based on the project’s type.

Templates

Reports

  • LiveCompare requires a user’s email address to display or download a report accessed from a shared URL. The report generated by the LiveCompare Usage Report workflow displays details for users who access reports from LiveCompare, and details for users who don’t have a LiveCompare account, but who access reports from a shared URL.

  • If you have turned off the Do Not Send Anonymous Usage Data to Tricentis switch in the Configuration – Email screen, LiveCompare sends an anonymized version of the LiveCompare Usage Report to the Tricentis LiveCompare team during the Commit Configuration process.

  • LiveCompare uses a browser-based viewer to display Excel reports generated by the Create Excel Report action, and CSV reports generated by the Create CSV Report action. You don’t need to have Excel installed on your client machine.

  • The Get Administration Objects action’s ReportView object type retrieves details for users who have viewed or downloaded reports.

  • The Send Email action includes links to attachments in the email’s Attachments section. These are normally URLs for generated reports.

  • The Usage Dashboard provides a graphical summary of the number of times users have displayed or downloaded LiveCompare reports. LiveCompare users can access reports using links in the LiveCompare user interface; users who do not have LiveCompare accounts may access reports via URLs that LiveCompare users have shared with them.

Platform

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

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

  • The Custom ALM Command action includes a dump_subject_tree command.

  • The Custom ALM Command action supports search paths and include paths.

  • The Diagnostic action includes an option to report on the age of an RFC Destination’s object links cache database.

  • The Execute Test Cases action returns details for non-automated Tosca execution lists. Tosca doesn’t allow you to add non-automated execution lists to an execution event.

  • The Get Application Components action supports Function Groups (FUGR) stored as Programs (PROG). In this case, the action returns the PS_POSID value associated with the Function Group.

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

  • You may configure the Search Test Repository action to find matching SAP Engine modules in transactions based on the value of each transaction’s NodePath attribute. This requires that the FindSAPModules and FindSAPModulesByNodePath fields are set to Y in the Configuration - Test Repository screen’s Tosca section.

  • The Search Test Repository action’s Exclude Test Ids parameter allows the action to exclude one or more Test IDs from its search results. The action only uses this property when searching an ALM Test Repository.

  • The Uses What and Uses What (Read Only) actions use Gateway Service (IWSV) objects as legal parent types when they perform SC_MON processing.

  • We resolved a problem with LiveCompare’s impact analysis actions which caused a ‘Timeout waiting for write lock’ error in some cases.

  • LiveCompare presents UTCLONG values retrieved from SAP as human-readable date time values. For example, the TIMESTAMP field in SAP table ABDOC_FILES has the type UTCLONG.

User interface

  • The apps user interface’s Getting things ready screen uses an animated display.

  • The apps user interface’s Apps Monitor screen no longer displays the Actions column in the wrong position.

  • LiveCompare installations that use a new user data directory no longer include the LiveCompare Product Support contact on the Administration screen, because the contact’s email address is no longer in use.

Accessibility

  • A screen reader can read error messages displayed in the Variant screen for example, Not a valid e-mail address.

  • Slider controls are visible against the Variant screen’s background if you use a high contrast Windows theme.

  • A screen reader can read the Server Settings and Recipients headings in the Guided Configuration screen’s Email tab.

  • In the Data Cleanser screen, you can access, the Add Files button using the keyboard.

  • You can access the toolbar icons in the studio interface using the keyboard.

  • In the Test Repository integrations topic, we improved the coloring in the Hits and Gaps chart.

Performance

  • The Smart Impact app’s Find Most-at-Risk Objects workflow passes a distinct list of changed objects to the Find Object Links (Read Only) action. This improves the app’s performance.

  • The Convert SAP Objects Test Search action uses cached BSP Application (WAPA) objects stored in its RFC Destination’s object links cache database if available. This improves the action’s performance.

  • The Create Object Links Cache action no longer stores SAP tables D010INC and D010TAB in its object links cache database, because LiveCompare’s impact analysis actions don’t use these tables. This improves the Create Object Links Cache action’s performance.

  • The Create Object Links Cache action uses the CHANGEDON date for BSP Application (WAPA) objects when updating an existing object links cache database. This improves the action’s performance.

  • The Create Object Links Cache action scans only *.js* files in ODATA services to find changed BSP Application (WAPA) objects. This improves the action’s performance.

  • The Symbol.db database file is part of an RFC Destination’s object links cache. LiveCompare reads symbols in this file from an in-memory cache when running impact analysis actions. As LiveCompare accesses the symbols many times, this improves the performance of the Smart Impact app and other apps and workflows that perform impact analysis.

  • The SymbolDbCacheCapacity setting on the Configuration - Impact Analysis screen determines the number of symbols from the Symbol.db database file that LiveCompare will store in the in-memory cache. This is a least recently used cache, where LiveCompare will remove symbols that it has not used recently and replace them with more recently used symbols. The default value is 10,000, but you may adjust this if you find that using a higher value provides a greater performance improvement.

  • The Update Cache button in an RFC Destination’s PHD, UPL, SDD, DUA and SC_MON tabs is enabled when a schedule is set in the respective tab. It runs the schedule immediately to retrieve the specified number of months of usage data into the tab. LiveCompare retrieves usage data using a schedule in each case; this does not affect the responsiveness of the RFC Destination’s tabs.

  • We changed the default value for the SapTableReaderMaxMemory setting in the Configuration - Table Contents screen from 10,000 to 80,000. This improves the performance of the Create Object Links Cache action when generating a full object links cache database.

  • The Pre-install Check utility checks for the IIS-ApplicationInit feature in IIS. This provides a performance improvement when you start the apps user interface for first time.

Test Repositories

Usage data

  • DUA, PHD, SC_MON, SDD and UPL data retrieved for an RFC Destination are each stored in separate SQLite databases in the <user data dir>\private\PerfHist directory on the LiveCompare server. If you update the cache for one type of data, this doesn’t affect the other databases.

  • The DUA, PHD, SC_MON, SDD and UPL tabs for RFC Destinations includes a Save button to allow you to save the retrieval and schedule details.

  • The Update Cache buttons in an RFC Destination’s DUA, PHD, SC_MON, SDD and UPL tabs for run the tab’s schedule to retrieve usage data immediately. The Update Cache button is only available if you have set a schedule in the appropriate tab.

  • An RFC Destination’s PHD tab allows you to schedule the retrieval of performance history data for the first day of each month.

  • The Collect Performance History Data and Get Performance History Data actions filter performance history to remove objects that match the Regular Expression patterns stored in the ObjectTypeNamePatternsToIgnore External Data Source.

  • If you retrieve performance history data using a LiveCompare Remote Function Call, an RFC Destination’s PHD tab filters the data to remove objects that match the Regular Expression patterns stored in the ObjectTypeNamePatternsToIgnore External Data Source.

  • The Create Test Repository Cache workflow in the Prerequisites folder uses the ObjectTypeNamePatternsToIgnore External Data Source to reduce the amount of usage data passed to the Search Test Repository action.

  • The Configuration Wizard updates existing usage databases during an upgrade from an earlier LiveCompare release.

ChaRM document states - Technical preview

  • The Get Change ID GUID workflow in the Tools templates folder accesses the specified ChaRM system and retrieves the GUIDs for the specified ChaRM document IDs.

  • The Get Change Request Type Statuses workflow in the Tools templates folder returns ChaRM document state identifiers for either Normal Changes or Request for Changes on the specified ChaRM system.

  • The Set Change Request State workflow in the Tools templates folder sets the state of a ChaRM change request document. Your ChaRM configuration determines the allowed states that a change request document may be set to; you can’t use the workflow to set a change request document states that your ChaRM configuration would not allow.

Debug logging

  • LiveCompare stores log files generated for a workspace in the <user data dir>\public\logs\<workspace name> folder on the LiveCompare server.

  • The Update Cache function for an RFC Destination’s PHD tab no longer creates a log entry for each row in the web statistics table returned from SAP. Instead, it logs only the first 10 rows in the Debug_ServerMain_<YYYYMMDD>.txt log file. This makes the log file shorter and more readable.

  • The Tier2BasicDebugLogAttrTab and Tier2BasicDebugLogGetValue registry settings allow for detailed logging of SAP hexadecimal values returned to LiveCompare. LiveCompare switches these options off by default. You should not normally switch them on unless Tricentis support asks you to.

  • We renamed the ServerDebugOn setting in the Configuration - Logging screen to ServerDebugLogLevel. LiveCompare replaces the ServerDebugOn=X setting with ServerDebugLogLevel=debug following an upgrade to this release of LiveCompare.

Installation

  • The Pre-install Check program checks for the Windows Authentication IIS feature on the LiveCompare server. LiveCompare requires this feature to support single sign on. If required, click Fix in the Pre-install Check screen to install the missing IIS feature.

  • You can’t run more than one copy of the Install Software program at the same time.

  • You can’t run more than one copy of the Configuration Wizard at the same time.

  • You can’t run more than one copy of the LiveCompareApps setup program at the same time.

  • The Deconfiguration Wizard stops any running Tosca Workflow Gateway Interface (WGI) programs during the deconfiguration process.

  • We have merged the LiveCompare Learning apps into the LiveCompareApps package. The LiveCompareLearningApps package is no longer available as a separate package.

  • We have removed the unused function /ICORP/RFC_GET_CHANGE_LOGS2 from both the LiveCompare ABAP Add-on and the core transport.

Fixes

  • We fixed a problem with the Code Guard app which caused a ‘no such table’ error in the Get TCOD to PROG Map workflow’s Find PROGs at 2nd Level action.

  • The Hierarchy report produced by the Compare IMG app no longer includes any IMGDUMMY links to tables that do not exist.

  • The Compare Objects app no longer reports a status of Can’t Compare for some Composite Provider (HCPR) objects.

  • We fixed a problem with the Compare Objects app where Transport Table key (TPRD) specifications in the Selects parameter caused an IMG hierarchy error if you hadn’t downloaded the IMG for the System1 RFC Destination.

  • We fixed a problem with the Compare Objects app where it compared objects that didn’t exist in the input transports.

  • We fixed a problem with the Retrofit Transports Analysis app which caused an ‘Invalid connection handle’ error in the Compare Changing Objects workflow’s Compare Objects action. The cause of the problem was that LiveCompare’s /ICORP/RFC_GET_TRCS_ATTRIBUTES function was not remotely-callable.

  • The SAP HANA Migration Assessment app no longer generates an error if it finds no customer IDOC extensions in SAP table EDCIM.

  • We fixed a problem with the SAP HANA Migration Assessment app which caused a ‘Cannot find table EDCIM in LUX’ error.

  • We fixed a problem with the SAP HANA Upgrade Analysis app where the Calculate Risk Diagnostic action caused a crash if its Source1 table contained only one record.

  • We fixed a problem with the Smart Impact app which caused a ‘Bad symbol’ error in the Find Object Links (Read Only) action.

  • We fixed an SQL error in the Test Audit app’s Search Pipeline Test Repositories workflow.

  • We fixed a problem with the Test Quality Audit app which caused an error in the Find Most-at-Risk by Month workflow’s third Execute SQL action.

  • The Get Recently Changed Executables workflow called by the Create Test Repository Cache workflow now returns a TYPE column in its Recently Changed Executables dataset. This allows the Create Test Repository Cache workflow to run to completion.

  • We fixed a problem with the SmartImpact_ChaRM workflow which caused an ‘Empty Pipeline’ error in the workflow’s second Convert Data action.

  • We fixed a problem with the Compare Objects action which caused an ‘no conversion found’ error when comparing CDS View (DDLS) objects.

  • We fixed a problem with the Compare Objects action which caused an ‘Access violation - no RTTI data!’ error.

  • We fixed a problem with the Compare SAP Tables action which caused an RFC Connection error when comparing view V_001P_C.

  • The Convert SAP Objects Test Search action no longer generates an exception if its analysis system’s Fiori Launchpad External Data Source is missing. Instead, it displays the error: FLPCA external data source not found for RFC Destination: <name of RFC Destination>.

  • We fixed a problem with the Create Hierarchy Report action which caused a ‘Cannot write2 file’ error in the SAP HANA Upgrade Analysis app.

  • We fixed a problem with the Filter by Patterns action where in some cases it caused a crash in the WIPSRV.EXE program.

  • We updated the Get SAP Objects action so that it returns only the components of a Function Group (for example, Programs and Includes), and not the Function Group’s associated data dictionary objects.

  • We fixed a problem with the Read SAP Table action which caused an ‘unimpl type ->p<- for conversion from R/3 to SQL type in field TIMESTAMP’ error when reading table ABDOC_FILES.

  • We fixed a problem with the Uses What (Read Only) action where the action did not process BSP Application (WAPA) objects.

  • We fixed a problem with the Where Used (Read Only) action which caused a ‘OUT OF MEMORY (bad_alloc)’ exception for objects that did not exist in the specified system.

  • We fixed a problem with the Where Used (Read Only) action, which produced a crash dump when run for a particular function.

  • The LDAP Account Password field on the Create Import Specification and Edit Import Specification screens no longer limits entry to 40 characters.

  • We fixed a problem with the Logs screen where the tail view did not work for log files stored in subfolders of the <user data dir>\public\logs folder on the LiveCompare server.

  • The Project screen for Administrators in the apps user interface now saves a project’s start date and end date correctly.

  • The ServiceNow screen no longer reports ‘jQuery is not defined’ errors in the console.

  • We fixed a problem with the Test Connection screen for Tosca Test Repositories where the count of unsynchronized modules did not include any excluded modules shown in Tosca Commander.

  • We fixed a problem with the Process Runs screen where downloading the contents to Excel resulted in a corrupt file.

  • The User dialog in the apps user interface no longer displays a console error when the StrongPasswords field is set to X in the Configuration - Security screen.

  • We fixed a problem where users could not log in to LiveCompare if any email addresses stored in the <user data dir>\private\Users.xml file on the LiveCompare server were unencrypted. If LiveCompare finds an unencrypted email address, it allows users to log in and logs an exception in the ServerMain_<YYYY_MM_DD>.log log file.

Documentation

  • The LiveCompare architecture topic includes architecture diagrams for LiveCompare.

  • The Move the user data directory to a new drive on the LiveCompare server topic describes how to move the LiveCompare user data directory to a new drive on the LiveCompare server. You may need to move the user data directory if the original drive you chose for it runs out of disk space.

  • The Obsolete workflow components topic lists workflow components that are no longer available in this release.

  • The Pre-install Check help for the Internet Information Server URL Rewrite Extension includes the requirement to fix all Internet Information Server issues before installation.

Deprecated functionality

Miscellaneous

  • We updated the following components to the versions in parentheses: Bootstrap (5.3.3), Dev Express (24.1.3), EntityFramework (6.5.1), jQuery (3.7.1), log4net (3.0.2), Plupload (2.3.8). System.Text.Json (8.0.5).

  • The text for error 9901 describes what to do if you receive a Bad workflow hierarchy error.

Related topics

How to use LiveCompare

Backward compatibility

Release notes