Release Notes 2023.2

Advanced Systems Concepts, Inc. is pleased to announce the release of ActiveBatch® version 2023.2.

 

Enhancements

 

Unlock a new era of security with ActiveBatch Release 2023.2!

 

We are excited to introduce a significant key improvement - enhanced data encryption. ActiveBatch’s legacy homegrown data encryption has been replaced with AES 256-bit encryption. Here are some of the benefits of upgrading to the latest ActiveBatch version:

 

Enhanced Data Security: Your data's protection is our top priority. We've upgraded our encryption to the gold standard - AES 256-bit encryption. Say goodbye to worries about data breaches and hello to peace of mind.

 

Seamless Compatibility: We're all about making your life easier. Easily import your data from older versions with complete compatibility. Plus, our upcoming Java-based Execution Agent ensures smooth support for non-Windows platforms without losing any functionality.

 

Prioritize Security, Upgrade Today: Security threats are evolving, and so are we. Upgrading to Release 2023.2 is not just an option; it's a necessity to safeguard your valuable data. Join countless organizations who've already made the smart move.

 

Empower Your Team: Give your administrators the power to manage encryption keys effortlessly. Less hassle, more control - it's a win-win for your IT team.

 

Stay Ahead of the Curve: In the ever-changing landscape of data security, staying ahead is crucial. Don't wait until it's too late. Be a pioneer in data protection.

 

Upgrade Today, Secure Tomorrow: Don't miss out on the chance to upgrade to the most secure and efficient version yet. Your data deserves the best, and so do you.

 

Make the upgrade to ActiveBatch 2023.2 your organization's top priority in today’s world of ever increasing security threats. Elevate your data security and peace of mind. Contact our Success Team to get started on your journey to a more secure future.

 

Review the General Information section to learn more about the upgrade process, and where to access upgrade resources.

 

Corrections

 

The following list of corrections have been applied to Version 2023.2. They are issues fixed after the release of V12 SP9.

 

Execution Agent\UNIX

  • Linux Agent crashes when aborting a job with a large name (40+chars). Ticket-46359.

 

Extensions\Job Steps\Licensed\Informatica

  • Informatica GetSessionLog Step is not writing to the log when the Write to Log property is set to true. Ticket 43060.

 

Job Scheduler

  • The Job Scheduler is aborting abnormally when copying/pasting a plan object. Ticket-43812.

  • The Job Scheduler service is frequently failing over to a secondary Scheduler. Ticket-52943.

 

Job Scheduler\Job Types\Script

  • When switching back and forth from one job type to another (for example, switching a script job to a jobs library job, then back to a script job again), the properties specific to the original job type (i.e. script contents) are not visible in the UI. Ticket-21756.

     

Job Scheduler\Web Services

  • After upgrading the Web Console or Self-Service Portal to V12 SP8 or V12 SP9, the Job Scheduler will abort abnormally (in certain scenarios) due to memory corruption. Tickets-55523, 51622, 49173.

 

Self-Service Portal

  • Sensitive data is being stored in an unsecure manner. Note! - The browser cache must be cleared in order to remove existing session data generated from previous versions. Ticket-61232.

 

Web\Web Console

  • The following security-related error occurs when attempting to create a script-type job using the Web Console UI: Access denied. For <JobName>: PermissionUse on //[0] has not been granted (c0250001). This error does not occur when using AbatConsole. Tickets-36889, 41440.

  • When saving a job in Web Console, if a Service Library Job Step is inside a loop step (e.g., for loop, for-each-regex, etc.), the object cannot be saved. It will fail with the following error: Object Reference not set to an instance of an object. Ticket-51771.

  • Sensitive data is being stored in an unsecure manner. Note! - The browser cache must be cleared in order to remove existing session data generated from previous versions. Ticket-61232.

 

Web\Web Console\Property Sheets

  • In Web Console, adding/editing/removing the 'associated time' property of Job or Plan schedule association fails with the following error: Uncaught TypeError: Cannot read properties of undefined (reading 'TimeSpecification'). As a result, the time is not set for the property. Ticket-52876.

 

Retired

 

The “Lieberman” Credential Type in the User Account object has been retired.

 

General Information

 

Please review the ActiveBatch Hardware/Software Compatibility knowledge article to make sure your database and operating systems are supported in V2023.2.

 

Next, the ActiveBatch V2023 Installation and Administrator’s Guide provides all the details required to upgrade to V2023.2. 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 to V2023.2, 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.

 

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.