What's new in this version


New developments in this version are divided into the following categories:

New features

The following new features were introduced in this version:

Feature

Link to further information

Page

Section

A new type of If action, Action:CaptureOutput, now enables you to search job output and capture text from the job output into a variable.

When specifying a Site Standard to enforce on a folder or simple folder, you can now specify values for its Business Fields through the JSON code.

The Rerun property now supports cyclic folders, in addition to cyclic jobs. The RerunLimit property now also supports folders, in addition to jobs.

The Confirm property now supports folders, in addition to jobs and subfolders.

When specifying a time period under the When property, you can now use the ActivePeriod parameter to choose between specifying a period of activity (when the job can run) or specifying a period of inactivity (when the job cannot run).

When specifying a time period under the When property, you can now specify a predefined Confirmation calendar to use for validation of scheduling dates and you can indicate how to handle jobs that are scheduled for a non-working day in this calendar.

SAP BW job for running and monitoring a Process Chain in SAP Business Warehouse (SAP BW).

Informatica job for automation of Informatica workflows and an Informatica connection profile.

File Transfer connection profiles were enhanced with several new optional parameters:

  • WorkloadAutomationGroups — enables you to specify roles (groups of users) that are allowed to access the connection profile.
  • VerifyDestination — Verifies the size of the file at the destination after a successful binary-mode transfer.
  • VerifyBytes — Verifies that the number of bytes sent to the destination during a successful binary-mode transfer is the same as the source file.

The new run job::waitingInfo command enables you to display the reasons why a waiting job has not yet been executed (for example: missing conditions, resources, hosts, users, or workloads).

The run order command now supports ordering of z/OS type jobs.

The new deploy ai:jobtype and deploy ai:jobtypes::get commands enable you to deploy Application Integrator job types to the Control-M/Agent and to get details of such job types.

The deploy service, which enables you to transfer job and configuration definitions to Control-M, now supports the use of a job definitions XML file. This is in addition to the folder definitions XML file, which was already supported.

For the retrieval of existing definitions, the deploy jobs::get command now enables you to choose the job definitions XML format for the output, in addition to the folder definitions XML format and the JSON format (the default).


Changes

The following changes were made in existing features in this version:

Feature

Link to further information

Page

Section

Responses to API commands of the run service no longer display session tokens in URLs.

To display session tokens in URLs in responses to API commands (as in previous versions of the product), you can use a new setting in the automation_api_config file, as described in the Control-M Administrator Guide.


Values of useextended, a Boolean parameter of the ConnectionProfile:SAP element, were changed from yes/no to true/false.

Corrected problems

The following table lists issues that have been corrected in the current release:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*