To offer more flexibility in creating workflows that meet your organization's needs, some restrictive validation checks have been removed from the workflow builder. With these changes:
- After adding a starting element (image, drive, hardware imager, or watch folder) in a workflow, the following application element no longer requires the ${DRIVE} or ${IMAGE_PATH} variables. Previously, you couldn't save your workflow unless you used the ${DRIVE} or ${IMAGE_PATH} variables in the application element that followed the starting element.
- A Stop for merge element can now follow any application element, such as a PowerShell script or workflow plugin, and does not require an AXIOM Process element anywhere in the workflow. Previously, a Stop for merge element was required to follow an AXIOM Process element.
- You can now specify an existing AXIOM case as an "image" element in a workflow, removing the requirement for an AXIOM Process element. Previously, an AXIOM Process element was required in a workflow to create an AXIOM case.
To improve the responsiveness of the dashboard, various JavaScript libraries have been updated to support React 18.0, Node.js 18.15.0, and Bootstrap 5.0. Previously, React 16.14, Node.js 14.0, and Bootstrap 4.0 were supported.

When configuring a remote acquire agent in Magnet AUTOMATE Enterprise, the default value for the Disconnected keep alive option was 10000 seconds. For consistency with Magnet AXIOM Cyber, the default value is now 1 day. (AU-173)
After creating a case with a hardware imager workflow, clicking the Show details button from the Existing cases table displayed a blank screen with a console error message. This issue occurred only in a Firefox browser. (AU-646)
Workflow runs without a build number did not display run logs in the dashboard. (AU-574)
Workflow runs created with the API did not sanitize the output paths, resulting in incorrect slashes or trailing spaces in some output paths. (AU-599)

Long lines in log files may fail to wrap correctly, causing them to overlap with other lines. To resolve the issue, refresh the log you are viewing. -AU-699
In an image processing workflow, AXIOM Process cannot read an iOS image with a keychain encrypted by BitLocker. To successfully read and process this type of image, copy the keychain to an external drive not encrypted with BitLocker. Additionally, if the AUTOMATE agent node's workspace is encrypted with BitLocker, workflows that have been configured to "turn on local image mode" will not be able to read these images. -AXP-10310
During data validation, if the source destination contains an image with copies of the same image in subfolders, the data validation fails. In this scenario, the expected behavior is that Magnet AUTOMATE doesn't recursively catalog identical files. -AUTO-3407
When copying files during data validation, the associated node is in use; however, the Nodes column for cases in progress appears empty. The expected behavior is that the Nodes column should display the active node. -AUTO-3406
When data validation begins, the workflow run log records a "Creating hash catalog" status. If files fail to copy after creating file hashes, there is no status in the workflow run log to indicate when copying started. The expected behavior is that there should be a "Copying" status after "Creating hash catalog" to indicate the sequence of events and when they occurred. -AUTO-3408

Updated agent installers to include the latest version of workflow applications: AXIOM Process, AXIOM Exporter, AXIOM Post-Processing, and Magnet ACQUIRE.
If Hash Sets Manager couldn't establish a connection before starting a scan with the AXIOM Process CLI, the scan wouldn't complete successfully. (DEA-2942)
For more information about Magnet AXIOM 7.1 updates, see the Magnet AXIOM 7.1 Release Notes.
For more information about Magnet AXIOM Cyber 7.1 updates, see the Magnet AXIOM Cyber 7.1 Release Notes.