Requests

Code Insight 6.14.2 SP1

When a project is set up in the system, the number of review levels and team members responsible for reviewing component requests are established by the project owner. The policy administrator is responsible for setting up automatic policies for component/license combinations, which automatically assign the new request a status of approved, rejected, or determines that the request requires manual review.

If a requester submits a new request for a component/license, and no policy is associated with that new request, a workflow is created based on the project attributes. The system automatically sends email notifications to the users responsible for reviewing the request.

Upon submission, the request is assigned to the first-level reviewer for action. If the request is approved, it is sent to the next person in the workflow responsible for reviewing it. Once all reviewers approve the request, it moves to history. If the component has conditions for use, once the request is approved by all reviewers, the request is automatically sent back to the requester for review and acknowledgment of the conditions for use. If a request is rejected, the workflow stops immediately, and the request is completed and moved to history. For each step in the workflow, the system sends email notifications to the appropriate requesters and reviewers notifying them of the action needed or action taken.

The possible request statuses are as follows:

•

Draft: This is a work-in-progress component request saved as a draft and not submitted for review.

•

Pending: This is a component request submitted for review, and a workflow is consequently created.

•

Approved: This status means that the component request is approved by all reviewers and all required conditions for use are reviewed and acknowledged by the requester.

•

Rejected: This means that at least one reviewer rejected the component request.

•

Code Insight provides the ability to customize the appearance of the Request Dashboard. For more information, see Customizing the Request Dashboard.