Rule Examples


Overview

Tasks

Included with

Tivoli Change Management administration

Overview

Rule examples

You can use rules to perform the following types of actions:
  • Update data fields
  • Add approval requirements
  • Notify personnel
  • Add tasks
  • Invoke commands at the operating system level

The following sections provide examples of each type of rule.


Tasks

Updating data fields examples

You can create a business rule which sets or updates the data in a field when the criteria for the rule is met.

Example 1

Action Set Field
Description Set the change status to "Verify" once all tasks are 100% complete
Category All
Time Dependency
Table IMPLEMENT SCHEDULE
Attribute Percent_Complete
Operator =
Value 100
Phrase IMPLEMENT_SCHEDULE:PERCENT_COMPLETE="100"
Field Status_ID
Value Verify
Note "Verify" must be set up as a status code.

Example 2

Action Set Field
Description Set the change risk to code to "High" if the estimated cost of the change exceeds 10000.
Category All
Time Dependency
Table CHANGE
Attribute Est_Cost
Operator >
Value 10000
Phrase
Field Risk_Code
Value
Note "High" must be set up as a risk code.

Example 3

Action Set Field
Description If the change involves a Windows installation, add a note to the special requirements field that the support team must be involved.
Category All
Time Dependency
Table CHANGE
Attribute Category
Operator =
Value Win_Ins
Phrase
Field Special_Requiremen
Value Support team must assist with change.
Note

Adding approval requirements examples

You can use a business rule to automatically add approvers to the approval list when the rule criteria is met.

Example 1

Action Add Approver
Description If the cost or estimated cost of the change exceeds 10000, the change must be approved by the CEO.
Category All
Time Dependency
Table CHANGE
Attribute Cost
Est_Cost
Operator >
Value 10000
Phrase CHANGE:EST_COST>"10000" OR CHANGE:COST>"10000"
Approval Name (Name of CEO)
Value
Note CEO name must exist in the PEOPLE table.

Example 2

Action Add Approver
Description If the affected assets includes the mainframe, the mainframe director must approve the change.
Category All
Time Dependency
Table INV_EFFECT
Attribute Inv_Description
Operator =
Value Mainframe
Phrase
Approval Name (Name of Mainframe Director)
Value
Note Name of Mainframe Director must exist in the PEOPLE table and the mainframe must be added as affected assets.

Notifying personnel example

You can create a business rule to notify a person when the rule criteria is met.
Action Notify
Description Notify the requester two days prior to the earliest date if the change has not been approved.
Category All
Time Dependency 2.0 days prior to the earliest date
Table CHANGE
Attribute Status_ID
Operator <>
Value Approved
Phrase
Notification Name (Name of person to notify)
Value
Note Name of person to notify must exist in the PEOPLE table and there must be status code for "Approved."
Adding tasks examples You can create a rule to add a task when the rule criteria is met.

Example 1

Action Add Task
Description If the change category is File Server, add a task called Backout Plan, which lasts one day and requires six hours of resources.
Category All
Time Dependency
Table CHANGE
Attribute Category
Operator =
Value File_Server
Phrase
Task Name Backout Plan
Duration 1
Labor Hours 6
Note

Example 2

Action Add Task
Description If the impact category is Personnel, you must set aside a four hour time slot for training.
Category All
Time Dependency
Table IMPACT_ITEM
Attribute Imp_Category
Operator =
Value Personnel
Phrase
Task Name Personnel Training
Duration 1
Labor Hours 4
Note There must exist an impact category called "Personnel."
Calling an operating system command examples You can create a business rule to call an operating system command, a batch file, or any other command that you can execute from the operating system prompt.

Example 1

Action Call
Description If the change category is New_Emp and the change status is "Completed," execute the employee audit program.
Category New_Emp
Time Dependency
Table CHANGE
Attribute Status_ID
Operator =
Value Completed
Phrase
Command empaudit
Note Empaudit must be a command set up on the Commands tab of the List Maintenance dialog box to execute the audit program.

Example 2

Action Call
Description If an employee leaves the company or is terminated, run a batch program to remove the security access of the employee.
Category Term_Emp
Time Dependency
Table CHANGE
Attribute Status
Operator =
Value Completed
Phrase
Command termemp
Note There must be a command called termemp set up on the Commands tab of the List Maintenance dialog box to execute the batch program.