Free cookie consent management tool by TermsFeed Appian Hotfixes [Hotfixes]
Appian Hotfixes

This page lists all the recent hotfixes for Appian 24.3.

Note:  Appian Cloud customers can refer to MyAppian to see your latest hotfix version.

For self-managed customers, all hotfixes are released as a downloadable package at the end of each week.

Hotfix package (13 Sep 2024)

Self-managed customers can use the following links to download and install the hotfixes package. If you are managing Appian on Kubernetes, instead of using the links below, you'll need to upgrade to the latest Appian on Kubernetes images to apply the hotfixes.

This cumulative hotfix package includes all resolved issues listed below in a single download. This hotfix is required for any Appian 24.3 installations not currently up to date with the latest hotfixes. After installing, you will be running on Appian 24.3.280.0.

You can view your current self-managed Appian version by logging into your Appian environment as a designer or system administrator and clicking the navigation menu > About Appian.

The package resolves the following issues.

24.3.280.0 (13 Sep 2024)

  • Security Updates - High

  • AN-291904 - Low
    Fixes error message associated with validations on the activity attribute type.

24.3.250.0 (06 Sep 2024)

  • Security Updates - High

  • AN-280586 - Medium
    Fixed an error with they apply() function.

  • AN-290307 - Medium
    Resolved an error with k transactions due to a negative time.

  • AN-290852 - Medium
    Fix an app import issue where a version mismatch occurred in the publish-portals-lock document after the Search Server upgrade.

  • AN-291067 - Medium
    Fixed an issue that prevented basic users from accessing record links on environments with legacy Portals.

  • AN-291324 - Low
    Fixed an issue where the search server failed to create a user due to a previous password configuration being left as a comment in the custom.properties file.

24.3.230.0 (29 Aug 2024)

  • Security Updates - High

  • AN-271602 - High
    Updated the bcprov library

  • AN-288191 - High
    Fixed an issue that prevented adding and editing rows in Record Type Designer when the record had a relationship to an empty record.

  • AN-289038 - High
    Fixed an issue that prevented adding and editing rows in Record Type Designer when the record had a relationship to an empty record.

  • AN-279631 - Medium
    Not Applicable

  • AN-288351 - Medium
    Fixed an issue that prevented Write Studio Records from showing an error message when the user didn't have access to a related record.

  • AN-288680 - Medium
    Add retry logic to Document Extraction Reconciliation result retrieval.

  • AN-288953 - Medium
    Fixed an issue with drag-and-drop on Studio display builder.

  • AN-289833 - Low
    Solved a bug in the operations console

24.3.205.0 (22 Aug 2024)

  • Security Updates - Critical

  • AN-289038 - High
    Fixed an issue that prevented adding and editing rows in Record Type Designer when the record had a relationship to an empty record.

24.3.200.0 (16 Aug 2024)

  • Security Updates - High

  • AN-277986 - High
    Updated the Okio JVM library

  • AN-288129 - High
    Removed an error message that was appearing intermittently in reconciliation tasks and interrupting the usual execution flow. Users will no longer have to dismiss this error and re-open the reconciliation task.

  • AN-288482 - Low
    a!callLanguageModel is no longer autosuggested in expression editors.

24.3.100.0 (18 Jul 2024)

  • Security Updates - Critical

  • AN-281250 - Critical
    Fixed Sharepoint and Dynamics integrations throwing an SLF4J error in some circumstances

  • AN-277201 - High
    Fixed an issue where Extract from Document Smart Service and Classify Emails Smart Service would fail due to an error generating unique job keys.

  • AN-278708 - High
    Fixed an issue that caused AI Skill smart services to hang indefinitely, exhausting the thread pool and causing failures in smart service executions.

  • AN-281972 - High
    Changed library dependencies to fix Legacy Web Services (SOAP)

  • AN-282074 - High
    Fixed an issue with custom attribute record field pickers in Process Insights

  • AN-282192 - High
    Fixed an issue that caused Appian instances to fail to start when the HTTP Proxy credentials can not be decrypted.

  • AN-282435 - High
    Fixed an issue where naming a custom attribute with "@" results in null attribute values

  • AN-283825 - High
    Process parameters with no values provided are now properly set to null, and null or empty process parameters now properly override default values. This fix restores behavior to be consistent with Appian 24.1.

  • AN-277303 - Medium
    Fixes an issue where Zookeeper configurations are missing for self-managed customers.

  • AN-279866 - Medium
    Fixed an issue where in rare circumstances Export to Excel of a Process Report was not exporting all columns.

  • AN-283427 - Medium
    Increased timeout for smart service syncs to prevent record type invalidation when full syncs occur at the same time.

  • AN-284801 - Medium
    Resolved an issue where component plugin interactions did not properly extend the session

  • AN-280147 - Low
    Fixed an issue that generated a high volume of error log entries in the application server log for some long-lived environments.

  • AN-286448 - Low
    Updated en_GB translations for "AI Test Case" labels

Installation

Perform the following steps to apply the hotfix:

  1. Stop Appian. See Starting and Stopping Appian for detailed instructions:
    1. Shut down the application server.
    2. Shut down the search server.
    3. Shut down the data server.
    4. Shutdown all Appian Engines, ensuring that the engines are checkpointed upon shutdown.
  2. Back up your existing Appian instance. See Backing Up Your Existing Appian Instance.
  3. Unzip the contents of the Hotfix package 24.3.280.0 into your <APPIAN_HOME> directory.
  4. Run the deleteFiles script (deleteFiles.bat on Windows, deleteFiles.sh on Linux) that is now located in your <APPIAN_HOME> directory.
    • If the script reports that some files were not deleted, address the reason for the failure (common causes listed below), and run it again until it no longer reports failed deletions.
    • Common causes of failed file deletion include:
    • The file is open in another window or process
    • The file is locked
    • You do not have permission to delete the file
  5. Unzip the contents of the updates.zip archive that is now located your <APPIAN_HOME> directory.
  6. Run the installJdk script (installJdk.bat on Windows, installJdk.sh on Linux).
  7. If you maintain customized or overridden Spring Security .xml files, merge them with the associated base files in the /deployment/web.war/WEB-INF/conf/security/ directory.
  8. Delete the following files:
    Linux
    • deleteFiles.sh
    • installjdk script.sh
    • OpenJDK8U-jdk_x64linux_hotspot.tar.gz
    • updates.zip

    Windows

    • deleteFiles.bat
    • installjdk script.bat
    • OpenJDK8U-jdk_x64windows_hotspot.zip
    • updates.zip
  9. If you are using a Web server, copy the content of <APPIAN_HOME>/deployment/web.war to the folder where the Web server is getting the static resources. See Copy Static Resources to the Web Server for more information.
  10. Run the configure script to deploy your environment's configuration and re-configure any node names previously set by the configure script tools.
  11. Start Appian:
    1. Start the Appian Engines.
    2. Start the data server.
    3. Start the search server.
    4. Start the application server.

To determine if the Appian 24.3 Hotfix is deployed, open the build.info file located in <APPIAN_HOME>/conf/. The contents of this file should match the following code sample:

build.revision=674ce437dc146122f73efcb7eec016d9c40ead41
build.version=24.3.280.0

Appian Hotfixes

FEEDBACK