Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Any changes made to your environment must be fully deployed via Setup before the upgrade and previously deployed versions will no longer be available after the upgrade.
  2. If your organization is staffed during maintenance, they will experience a short period of downtime (less than 10 minutes).
  3. Users will get a notification on their first login after the upgrade to accept and download the newest update. Please instruct your users to accept the application update.
  4. For more details about the steps, each customer can take after the release, see the Post Release Testing

Known Issue:

Configuration Save:

  • ECS uses a Change-Stage-Commit workflow to manage configuration changes to the system. ECS 5.4.0 introduced an unexpected change to this process. When the save button is clicked changes that should be staged for commitment are being applied immediately to the system. This change applies only to light deploys. Full deploys continue to follow the standard workflow.


This release contains the following feature and reporting enhancements, and bug fixes.

...