1. Field Service Guide
  2. Process Flow for Logging Change Requests

Process Flow for Logging Change Requests

After you set up Siebel Quality, quality assurance testers and others can log change requests (CRs). The following figure shows the process flow for the tasks in logging.

Process Flow for Logging. This image is described in surrounding text.

More information about the tasks in this process follows:

  1. Query for Existing Change Requests. After identifying a product issue, but before logging a new CR, the CR creator queries to see whether a duplicate issue already exists. For more information, see Querying for Existing Change Requests.

    • Update Existing Change Request Comments. If the search reveals an existing CR for the issue, then the CR creator enters a comment with missing relevant information.

    • Log New Change Request. If the CR creator cannot find an existing issue, then the creator generates a new CR. For more information, see Logging Change Requests and Generating Change Requests from Service Requests.

  2. Add Attachment. Optionally, the CR creator can add attachments, such as screen captures and configuration files, to clarify the issue.