Siebel Field Service Guide > Quality Management > Process of Administering Siebel Quality >

Adding Release Product Builds


You control product version information for the organization by setting up release product builds. Because every Release Manager and Siebel Quality record must be associated with a specific release product build, you must set up product builds before users enter any records.

As a product progresses through the release cycle, increasingly advanced product prototypes apply. (In the case of software development, these prototypes are builds.) When each new prototype is available, enter it into Siebel Quality to allow users of Siebel Quality and Release Manager to record each record for the appropriate build.

Releases include the following types:

  • Future Releases. Although only 1 active release can be in progress, you must also set up records for future releases. Consequently, if a manager defers a feature or fix from the current release, then a user can target it to a specific future release.
  • Unspecified Releases. Sometimes you might not know the appropriate future release for a feature or fix. For this contingency, you must set up at least 1 artificial release named Unspecified Release or a similar term. Users can link orphan items to this release. When the appropriate future release is determined, users can then retarget an item to that release.

This task is a step in Process of Administering Siebel Quality.

To add a release product build

  1. Navigate to the Quality screen, then the Release Product Administration view.
  2. In the Release Product Administration list, create a new record for a build, and complete the fields as appropriate.

    Some fields are described in the following table.

    Field
    Comments

    Product

    Type the prototype product for the build.

    Version

    Type the version number of the product.

    Build

    Type the number or code that identifies the build.

    Language

    Type the 3-letter language code.

    Target Version

    Select this check box to make the build available as a value in the Target field of the Change Requests view.

    End Date

    Select the date after which the build disappears from the Build and Target fields of the Change Requests view.

    NOTE:  When you create a record in the Release Product Administration view, the information in the Build, Language, Product, and Version fields is available to users in the Build field in the QA Tests view of the Release screen and the Change Requests view of the Quality screen. If you select the Target Version check box, then this information also is available in the Target field in the Change Requests view of the Quality screen.

Siebel Field Service Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.