Setting auditing preferences and version control monitoring

You can set auditing preferences to justify a change to an item in your environment and then monitor changes with version control from the Dynamic Workload Console

About this task

In the following scenario you can learn how to set auditing preferences in the context of an example.

Timothy works in the payroll department of a bank named GoodCredit, and he is an HCL Universal Orchestrator Administrator. A new policy requires employers to provide a ticket number and a justification each time someone edits an item in the HCL Universal Orchestrator environment, so that the audit department can control any change anytime. Tickets are managed by a ticketing server named OurTickets.

Timothy has to enable the request of a ticket number and a justification when users perform changes on items.

Procedure

The steps that Timothy completes to set auditing preferences on HCL Universal Orchestrator follow.
  1. Require a ticket number and a justification when a user changes an item.
    1. From the navigation toolbar, select Administration.
    2. Select Auditing preferences.
    3. In the Engine section, select the check-box that corresponds to the engine for which you need to enable this option.
    4. Select the Justification check-box that corresponds to the same engine and then select the Ticket required check-box on the same line.
  2. Specify the ticketing server and the syntax that the server supports.
    1. Select the Ticket required icon.
    2. In the URL field, type the web address of the ticketing server and the ticket syntax: https://ourtickets.mycompany.com/tickets/${ticketnumber}
    3. Click Ok and then Save.

    Each time an item is created or changed in the GoodCredit environment, a window opens and requests that the user specifies a justification and a ticket number.

Monitoring changes with version control

About this task

In the following scenario you can learn how to monitor changes in your environment with version control in the context of an example.

The audit department must track the changes that the payroll department employees made on a job stream named PAYDAY. The steps that the audit department must perform to check the previous versions of the job stream are as follows:

Procedure

  1. From the Design menu, click Workload Designer page.
  2. In the Explore area, select the PAYDAY job stream.
  3. On the toolbar, click Versions.

Results

The audit department can check who changed the PAYDAY job stream and all related information.