Govern Scheduler Console (SC) – What’s New
Version 6.0 | 6.1
Overview
The following is a non-exhaustive compilation that lists recently updated topics related to the Govern for OpenFormsTM Scheduler application.
What’s New!
Govern Ribbon Search
Standard Feature – Ribbon Search Release 6.0.1903.0374 (Govern only) | 6.0.1904.0515 (Govern only) Release 6.1.1911.0497 (All applications) | 6.1.1912.0513 (All
Standard Feature – Sequential Batch Process
Standard Feature – Sequential Batch Process Version 6.0 and Version 6.1 Overview Available in Release 6.0 and 6.1 A standard
Batch Scheduler Service Installation
Batch Scheduler Service Installation Version 6.0 and 6.1 Overview Step by step Govern Batch Scheduler Service installation procedure. Before Getting
Old News
Read More... 106-all-SC-wnew Release 6.0
[6.0.1603] Batch Process Definition will be maintained in the OpenForms Reference database and distributed
[6.0.1603] Archive Path was added to keep a copy of the source documents after having been processed
[6.0.1603] When a batch process is executed, the Current System Date and the Tool Box are disabled so that you cannot change the dates and year used by the batch process.
[6.0] Batch Processes are linked to Profiles. Users access the Govern Batch Processes in the same way that they access the user forms.
[6.0] Batch Processes Categories (nodes) are deprecated.
[6.0] Automatic Update when a new version is installed
[6.0] Minutes to Update (new SY Registry Parameter)
[6.0] Single Deployment/ Connection Key per Windows Service – Appender Services to add connection keys is deprecated
[6.0] Uninstalling Batch Scheduler Service is now done in an Administrator Command Prompt, using the SC DELETE command. See Batch Scheduler Installation for more information
[6.0] System Registry Default Log file path for reports and logs is deprecated – Paths are defined in the Batch and Report Definitions
[6.0] New system generated trailer connection key (copy of original with NO CONNECTION TIME OUT LIMIT) is used in batch processing to prevent time out errors. Depending on the type and mode of execution (i.e roll back), SQL transactions may be committed to the database in a large group where the processing time may exceed the normal time out parameter.
See Also