With cross launch functionality, when you click a ticket number hyperlink in a report in BMC Remedy Smart Reporting, the ticket opens in other BMC applications.

If you have installed BMC Remedy Smart Reporting in a cluster, you must perform the following configuration post-installation.

BMC Remedy Smart Reporting is integrated with Smart IT version 1.2 or later.

If your Smart IT session is active and you cross launch from BMC Remedy Smart Reporting to Smart IT, you need not provide Smart IT credentials. However, if your Smart IT session is inactive, you must provide credentials and the ticket opens after authentication.

Elevated user rights (such as Schema Owner or Database Owner) are required for the Appian Data source during the application server startup portion of the update process.

Note: The configuration for relational databases can change significantly between versions of JBoss.

Before updating, you must review the Appian Release Notes, Update Considerations, and System Requirements pages.

In this document, the following conventions are used to indicate the locations you have selected on your servers during installation: directory location, you may avoid having to change some of the file paths that Appian uses for referencing your data after copying the data files over to the new installation.

This step is not strictly required for the proper operation of the system, however the logs directory contains valuable information in the Support for custom Spring Security configurations has been deprecated since version 7.11 and you should convert your authentication configuration to one of the three out-of-the-box authentication mechanisms at the earliest opportunity.

If you have not yet converted to using the out-of-the-box authentication configurations and you maintain customized or overridden Spring Security xml files, you must merge them with the associated base files in the directory when updating to the latest version of Appian.

Follow the steps listed in the Appian Installation Guide specific to your environment and new version, keeping the following in mind: Starting in Appian 17.1, there are new required web server configurations that specify cache policies specific to certain paths.

These caching configurations not only provide users with better performance when accessing Appian from a web browser, they are necessary to avoid UI errors upon upgrade.

Note: Do not perform an update and add additional execution or analytics engines or additional gateways in the same step.