Defining Legacy policy processes

Review and define the policies for various lifecycle events in IBM® Rational® Asset Manager, including asset submission, approval, asset publish, asset retire, asset archive, and timer.

About this task

Note: This topic describes functions that are supported, but no longer recommended as of Rational Asset Manager, Version 7.2. If you used policy processes and review processes prior to V7.2, you can still access and manage them. However, you cannot create new review processes unless they are using Rational ClearQuest®. Instead, create custom lifecycles with the Rational Asset Manager web interface to manage the development of assets on your repository. For more information, see Asset lifecycle and development and Creating master lifecycles.
Note: All policies in a custom lifecycle take priority over legacy (prior to V7.2) policy processes. If the conditions for a policy in a custom lifecycle and a legacy policy process conflict, the legacy process will not run.

Policies are more efficient and consistent than standard review boards. Review boards represent a necessary level of governance over the assets in a repository. However, policies automate many of the tasks that a review board is responsible for, which can save time and effort. Automated policies can also quickly and accurately complete tasks that might be more error prone to a human review board. When using automated policies, an asset is validated against a set of requirements that you define and then, upon meeting policy requirements, is submitted to a review board. If an asset does not meet the minimum requirements defined by the policies, it will not be submitted to the review board.

Although you can create your own custom policies, for information on the policies that are included with Rational Asset Manager, see Policies for asset lifecycles.

Follow these steps to create reviews using the policy processes that are installed on your repository.

Procedure

  1. Log into Rational Asset Manager web client.
  2. Open the Administration page.
  3. Click the community name that you want to create the review process for.
  4. Click the Lifecycles tab, and click and expand Legacy Review Processes.
  5. In the Policy Processes section, click New Policy Process.
  6. Describe the new policy process:
    1. Type a name for the review process.
    2. Type a description for the review process. Descriptions can include spaces and special characters.
    3. Specify the events, or a specific frequency, to start the policy process.
      Note: You can specify more than one event but you can only specify one timer.
      • Asset Submission: Runs the policy when the asset is submitted to the repository. If an asset is submitted, the policy will run before the regular review process begins. If the asset does not comply with policy requirements, the asset will be returned to draft state and a report will be displayed on the success page with a link to the review page that displays the content of the report.
      • Asset Approval: Runs the policy when the asset is approved in the repository. If an asset is submitted into a review process and the asset is approved, the policy will run. If the asset does not comply with policy requirements, the asset will be returned to draft state and a report will be displayed on the Review page. When the asset is approved in the review process and complies with the policy requirements, the asset will be approved for use in the repository.
      • Asset Publish: Runs the policy when the asset is published to another repository. If the asset does not comply to the policy requirements, the asset will not be published and a report describing the policy failure will be displayed on the Review page.
      • Asset Retire: Runs the policy when the asset is retired. If the asset does not comply with policy requirements, the asset will not be retired and a report describing the policy failure will be displayed on the Review page.
      • Asset Archive: Runs the policy when the asset is archived. If the asset does not comply with policy requirements, the asset will not be archived and a report describing the policy failure will be displayed on the Review page.
      • Asset Delete: Runs the policy when the asset is deleted. If the asset does not comply with policy requirements, the asset will not be deleted and a report describing the policy failure will be displayed on the Review page.
      • Timer: Runs the policy on a specific timer. You can specify the frequency of the policy, for example, 2 years will run the policy every two years. If this policy fails, the asset returns to the editable draft state.
  7. Define the conditions for the policy process. After a user submits an asset, if the asset matches the specified asset types and categorizations, the policy will be run against the asset.
    • Select any number of asset types that you want this policy to correspond to and click Add.
    • For each asset type, select the categorization and click Add.
  8. Add the policies that you want to run during in this policy process.
    1. Click Add policy. You will see a list of the default policies and any custom policies that you have defined.
    2. Select the policy from the Policies list and click OK.
  9. Configure the policies. There are two types of configurations: standard and relationship. The requirements of the policy determine the configuration that you use. The default policies (except Relationship Constraints) have their own configuration options.
    1. Click Configure. If the Configure link is not available for a policy, then it cannot be configured.
    2. In the Configure a policy window, type or select values to configure the policy. When you use a standard configuration, the policy provides a label and description and expects the value to be a string. For example, if the property label is Minute module: even=2, then the policy value could be 5. When you use a relationship configuration, the policy provides a label and description and expects the value to be an array. For example, if the property labels are Relationships to include and Dependent Relationships, then the policy values will be aggregation and dependent.
      Selected dependant relationships.
    3. Click OK.
  10. Click OK to save the policy.

Feedback