> ## Documentation Index
> Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Release notes and changelog

<Info>
  For information on upgrading from previous versions, see the
  [Atoti Sign-Off Migration Notes](./migrate-5.1).
</Info>

<Update label="5.1.0" description="2023-11-30">
  Download the distribution files
  [here](https://activeviam.jfrog.io/artifactory/activeviam-accelerators-artifacts/signoff/5.1.0/)

  You can download the following zipped distribution files:

  * UI source code.
  * UI build that does not require an installation and can be directly deployed.
  * Source files that can be used to build the module.
  * Maven repository required to build the project and run the tests.

  <Note>
    The Atoti Server 6.0.9 Maven repository files have been removed from this zip, so you’ll need to download them separately. Click [here](https://artifacts.activeviam.com/share/ActivePivot_stable/6.0.9/) to locate them.
  </Note>

  * Offline documentation that can be served by the module.

  ### Summary

  * **Re-applying adjustments**: When an application server fails and restarts, previous adjustments are automatically applied for tasks that are not yet approved. Refer to the [User Guide](../../../user-ref/process-tasks/adjustments/perform-adjustments-ui#span-idre-applyingspanre-applying-adjustments-on-failure) for more information.
  * **Java 17 upgrade**: Atoti Sign-Off is now compatible with, and *requires*, Java 17.
  * **Atoti Server upgrade**: Atoti Sign-Off has been upgraded to Atoti Server 6.0.9.
  * **Spring Security upgrade**: We have upgraded Spring Security to version 5.8.7 to resolve vulnerabilities and prepare for the upgrade to Spring Security 6.0 (via Spring Boot 3).
  * **Audit log**: Export details are now correctly included in the audit log.
  * **Support for multiple members in a given level of the Sign-Off scope**: When specifying the scope of the Sign-Off tasks, you can now select multiple members within a given level. Previously, only one member could be selected.
  * **Unique task definition names**: Task definitions must now be created with a unique name. Creating a task definition with a name that already exists in the database results in an error. Uniqueness is enforced at the point that a task definition is published. Existing task definitions are unaffected.

  ### Known issues

  None.

  ### Dependency versions

  <Warning>
    **Updated 2024-04-12**: This version of Atoti Sign-Off is not compatible with Atoti UI version 5.1.16 or higher.
  </Warning>

  | Component                                                                                                      | Version |
  | -------------------------------------------------------------------------------------------------------------- | ------- |
  | [Adjustments Services API](https://docs.activeviam.com/products/modules/adjustments-services/2.2/online-help/) | 2.2.0   |
  | [Atoti Server](https://docs.activeviam.com/products/atoti/server/6.0.9/)                                       | 6.0.9   |
  | [Atoti UI](https://docs.activeviam.com/products/atoti/ui/5.1/)                                                 | 5.1.x   |
  | Java                                                                                                           | JDK17   |
  | [Sign-Off API](https://docs.activeviam.com/products/modules/signoff-api/2.1/online-help/)                      | 2.1.0   |
  | [UI Components](https://docs.activeviam.com/products/tools/ui-components/5.0.28/online-help/)                  | 5.0.28  |

  ### Added

  | Issue Key                                                | Details                                                                                                                            |
  | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
  | [SO-448](https://activeviam.atlassian.net/browse/SO-448) | When an application server fails and restarts, previous adjustments are automatically applied for tasks that are not yet approved. |

  ### Changed

  | Issue Key                                                | Details                                                                            |
  | -------------------------------------------------------- | ---------------------------------------------------------------------------------- |
  | [SO-471](https://activeviam.atlassian.net/browse/SO-471) | You can now select multiple members in the given level in a sign-off task’s scope. |
  | [SO-474](https://activeviam.atlassian.net/browse/SO-474) | Reduced Sonar issues.                                                              |
  | [SO-477](https://activeviam.atlassian.net/browse/SO-477) | Upgraded to Atoti Server 6.0.9, including Spring Security 5.8.                     |
  | [SO-478](https://activeviam.atlassian.net/browse/SO-478) | Upgraded to Java 17.                                                               |
  | [SO-482](https://activeviam.atlassian.net/browse/SO-482) | Task definitions must now be created with a unique name.                           |

  ### Fixed

  | Issue Key                                                | Details                                                                                                                                                         |
  | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | [SO-426](https://activeviam.atlassian.net/browse/SO-426) | Fixed a bug where export details were not included in audit log.                                                                                                |
  | [SO-485](https://activeviam.atlassian.net/browse/SO-485) | RestTemplates are now configured to support standard cookie spec which stops the appearance of WARN log messages when requests are made to application servers. |
</Update>