Contract workflow is the end-to-end process, beginning with submitting a request for approval for a desired contract change, to actually committing the changes to the system. The Contract Author, the person creating or modifying the contract, must receive the relevant approvals before committing the contract.
Using the contract workflow feature, a contract must be approved by the defined authorized party in order for it to be committed. The steps of the contract workflow include:
Step 1: Creating or modifying a contract version (Author)
The contract author prepares a new contract version or modifies an existing one.
The contract workflow status is Draft.
For more information, see Contract Workflow and Modifying a Contract.
Step 2: Requesting contract approval (Author)
An email request is sent to the Approver. The Contract Workflow status is Pending Approval.
For more information, see Requesting Approval for a Contract.
Step 3: Approving or rejecting changes to contract (Approver)
Clicking the relevant link in the email navigates to the login. Enter your user name and password and you are directed to the CA Business Service Insight Contract Objectives page. Use the Contract Audit Trail tab to view changes in the contract. The contract approver approves or rejects the contract. The contract workflow status is Commit Ready if approved. If rejected, the workflow status is Draft.
Note: A user with approval privileges can approve the contract directly in the Contract Objectives page (without e-mail notification). In this page, the approver has the option to review the changes (via contract Audit Trail), and then approve or reject the changes.
For more information, see Approving or Rejecting a Contract.
Step 4: Authorizing the request (approved/rejected) (Approver)
An email message is to be sent to the Author stating that the changes were approved or rejected, and that he can commit the version (if they were approved). If approved, the contract workflow status is Commit Ready. If rejected, the contract workflow status is Draft.
For more information, see Committing a Contract.
Step 5: Contract ready for commit/edit (Author)
Once the contract is approved, the commit button on the Contract Objectives page is enabled, and a Revise button is visible. The author can either commit the version, or revise the version. If the author commits the contract, the contract workflow status is Commit. If the author revises the contract, the contract status is Draft.
Note: Choosing to revise a Commit Ready version of the contract, requires the Author to begin a new round of the contract workflow, meaning that approval is required for any additional changes made.
|
Copyright © 2012 CA.
All rights reserved.
|
|