Release Notes 2023.3
Advanced Systems Concepts, Inc. is pleased to announce the release of ActiveBatch® version 2023.3.
This is a service pack upgrade. For instructions on how to apply the service pack, please refer to the ActiveBatch Installation and Administrator's Guide. See the Service Packs and Installation Maintenance Operations section.
Enhancements
Web\Self-Service Portal (SSP)
-
An enhancement was implemented where the SSP business user can now respond to an instance in a Waiting Constraint (User Input) state.
Web\Web Console
-
The Web Console Connection Manager has been enhanced as follows:
-
It now seamlessly integrates with modern browser auto-fill capabilities.
-
It will prompt a user for credentials if they attempt to connect prior to entering them.
-
-
A Web Console enhancement was implemented where after a browser refresh, the user does not need to re-enter user credentials if a session is already established and has not timed out.
Corrections
Extensions\Job Steps\ActiveBatch\ImportObject
-
The ActiveBatch > ImportObject Jobs Library Job Step lets you specify the import object path as a location that is not valid (the location should be the fullpath to an existing container - plan, folder, or root). Despite the invalid path, the job is marked a success when it runs.
Job Scheduler\Constraints
-
When a SQL Query active variable returns a negative number that is used in the Constraint Logic property for comparison purposes, the constraint resolves incorrectly as follows: The instance continues to wait on the constraint despite the logic evaluating to true, or the instance runs despite the logic evaluating to false. Ticket-83481.
Job Scheduler\Event Triggers\Web Service
-
When configuring a Web Service Event Trigger using RestUsernameSecure as the Endpoint Type, the call fails with “Object Reference null”, or with "the server encountered an error processing the request". Ticket-55157.
Utilities\Change Management
-
When using Change Management to synchronize objects, completion triggers are intermittently missing on the target Job Scheduler. Tickets-41131, 54700.
Web\Self-Service Portal (SSP)
-
In certain scenarios, refreshing the SSP application results in multiple message boxes popping up when only a single message should appear.
-
If the SSP browser is refreshed after a valid connection to the Job Scheduler has already been established, the user is presented with the login page instead of the main page.
-
When a valid connection to the Job Scheduler using SSP has been established, it is possible to connect to SSP in a second session using the same user account as the first session, but with a missing or invalid password. Ticket-60131.
Web\Web Console
-
In certain scenarios, responding to an instance in a Waiting Constraint (User Input) state does not result in expected behavior.
General Information if you are running a V12 or earlier version of ActiveBatch
Please review the ActiveBatch Hardware/Software Compatibility knowledge article to make sure your database and operating systems are supported in 2023.
Next, the ActiveBatch 2023 Installation and Administrator’s Guide provides all the details required to upgrade to 2023 if you are still running on version 12 (or earlier). Please see the section named “Upgrading from V12”.
Before you begin to consider the upgrade process, make sure your ActiveBatch environment is running on a version that has been thoroughly tested to support the upgrade procedure. See more details below.
To upgrade from a prior major release to 2023, your current Scheduler must be running V12 SP8 or V12 SP9. You cannot upgrade from V11 (you must upgrade to V12 first). Please see the links below to assist in the process of upgrading your environment if you are currently not running on a version that supports the upgrade path.
-
Strategies and Procedures for Upgrading to ActiveBatch V12 (from V11 or earlier).
-
The ActiveBatch V12 Installation and Administrator’s Guide provides details on upgrading from V11 to V12.
Product End-of-Maintenance and End-of-Life
End-of-Maintenance (EOM)
The EOM date is defined as the point at which the software will no longer receive updates or bug fixes, but support will still be available to you. EOM happens 12 months after the release date, and notifications will be sent to you before that date. Updates or patches for software applications that have reached their EOM date will no longer be provided.
End-of-Support (EOS) or End-of-Life (EOL)
The EOS date is defined as the point at which the software will no longer be supported, and no further updates or bug fixes will be provided. EOS happens 18 months after the EOM date, as described in the documentation at the time of the release.
- EOM for 2024.2 is May 29, 2025.
- EOL/EOS for 2024.2 is October 28, 2026.
- EOM for 2024.3 is August 29, 2025.
- EOL/EOS for 2024.3 is March 2, 2027.
- EOM for 2024.4 is Nov 20, 2025.
- EOL for 2024.4 is May 20, 2027.
- EOM for 2025.1 is February 21, 2026.
- EOL for 2025.1 is Sept 1, 2027.
End-of-Life (EOL) for other versions
- EOL for V11 was June 30, 2024
- EOL for V12 was Nov 30, 2024
Contact Information
If you encounter any problems with ActiveBatch and are under the Product Warranty or post-warranty maintenance service plan, contact Redwood at support@redwood.com or visit our website at http://www.redwood.com.