Keeping track of changes to scheduling objects

How to keep track of changes in your environment

From the Dynamic Workload Console, HCL Workload Automation administrators, operators, and schedulers can review all changes to scheduling objects, both in the database and in the plan, discover which user performed a specific change, and the time and date when the change was performed.

Schedulers can review the history of all changes made on a specific object at any time and check previous versions of the object in scheduling language.

Historical information is available for each scheduling object in the Workload Designer in the Versions tab and in the results of the Monitor Workload query.

Auditing justification and reporting

Administrators can maintain an audit trail, consisting of detailed information about the user who performed the change, the time and date when the change was performed, the reason why the change was implemented, and the details of the change for every modified item.

Administrators can optionally enforce a policy by which each user making a change to an object must provide a justification for the change.

They can produce a report containing information on all changed objects or on a subset of such objects.

You can audit both information available in the plan and in the database. By default, auditing is enabled. To disable auditing, use the following global options:
Enables auditing of the information available in the database.
Enables auditing of the information available in the plan.
You can store auditing information in a file, in the HCL Workload Automation database, or in both. To define in which type of store to log the audit records, use the auditStore global option. For more information about global options, see Global options - detailed description.

To enforce a policy by which each user making a change to an object from the Dynamic Workload Console must provide a justification for the change, see Auditing justification and reporting.

To enforce the justification policy when making changes from the command-line programs see:


Application developers and schedulers can compare and restore previous versions of each changed object because HCL Workload Automation Workload Automation on Cloud maintains all previous versions for the whole set of objects.

Schedulers can also view the differences between versions using a comparison viewer, compare the differences, and rollback to a previous version.

Previous versions of changed objects are available in scheduling language.

Release management

Application developers and schedulers can promote the job workflow from development to test or production environments. An enhanced versioning capability keeps track of differences between different versions in the test and production environments to avoid conflicts.

They can also promote changes from production to pre-production or development environments to apply in the preproduction environments last-minute changes implemented into the active plan.

To move their workflows they can create and export a workload application template, a compressed file containing one or more job streams with all the related jobs and internal or external dependencies (such as files, resources, prompts). A workload application template is a self-contained workflow that you can import into a target environment.

Any mismatches in the versions of objects between development and production environments are seamlessly managed and resolved. For more information about creating and importing workload application templates, see Reusing a workload in another environment.