Release 2.0 comes as a separate product with the brand JS7 JobScheduler. It will be available in parallel to JobScheduler 1.x for around two years.
We strive for continuity in our release planning, see How long will you support the different versions of JobScheduler and YADE?
With the first release of JS7 JobScheduler 2.0 a limited set of features will be available that is intended for new users of the product who aim at high performance in larger scheduling environments. Users of JobScheduler 1.x are recommended to stick to ongoing releases of this branch until full feature compatibility of branch 2.0 and respective migration utilities become available.
Release 2.0.0
- Preview Release: May 2021
- Release Candidate: 2021-08-19
- General Availability: 2021-09-22
Release 2.0.1
- General Availability: 2021-10-08
- Features
- GUI Performance Improvements
- Improved bulk operations for larger numbers of orders
- For details see Release 2.0.1
Release 2.1.0
- General Availability: 2021-10-28
- Features
- Improvements to workflow patterns
- JS7 - Cycle Instruction for workflows in addition to cyclic orders from schedules
- Performance Improvements
- Improvements to workflow patterns
- For details see Release 2.1.0
Release 2.2.0
- General Availability: approx. 2021-11-15
- Features
- Active Clustering for Agents
- Support for JS7 - JITL SAP Jobs
- Git Repository Integration
- Improvements to monitoring and alerting
- Improvements to the Monitor View to select and display workflow related events and system events with JOC Cockpit
- Full migration support for JobScheduler 1.x releases by conversion utilities
- For details see Release 2.2.0 (in progress)
Release 2.3.0
- General Availability: approx. 2022-01-20
- Features
- Restart capability for Agent Clusters
- YADE 2.0 File Transfer
- Migration of Job Streams
- Restart Service
- Rerun persisted web service operations after restart of JOC Cockpit
- Synchronize inventory between Controller and JOC Cockpit
- Full feature compatibility compared to JobScheduler 1.x releases
- For details see Release 2.3.0 (planned)