|
Siebel Field Service Guide > Release Management > Process of Administering Release Manager >
Setting Up Lists of Values
The administrator typically sets up Lists of Values (LOVs) for use in Siebel Business Applications. Although all types of release items share the Status field, the LOVs for the Status field are likely specific to each release item. For example, while the Status values for an engineering task typically relate to the development phase of the task (Unit Test, Final, and so on), the Status values for a technical publications document typically relate to the production phase of the document (Draft, Final Edit, and so on). So that users do not have to review long LOVs for phases that are related to their work, you might have to restrict the views where specific LOVs appear. For more information about setting up LOVs and restricting the views associated with specific LOVs, see Siebel Applications Administration Guide. Table 41 describes the LOVs to set up before using Release Manager. In this table, the Type column denotes the drop-down list record in the List of Values view.
Table 41. Release Manager LOVs
|
|
|
|
|
Client OS |
QA Tests |
PSTASK_CLIENT_OS |
The type of operating system running on the client. |
Windows 2000, Mac OS |
Client Type |
QA Tests |
PSTASK_CLIENT_TYPE |
The type of test computer used by the tester. |
HTML |
Database |
QA Tests |
PSTASK_CLIENT_DB |
The type of database running in the test environment. |
IBM DB2, Microsoft SQL Server 7.0 |
Effort |
Engineering Tasks |
PSTASK_ENGINEER_EFFORT |
The amount of effort required of the engineer to complete the task. |
High, Low, 1 Man Month |
Priority |
Features |
PSTASK_PRIORITY |
The relative importance of the feature. |
High, Medium, P1. Critical |
Revenue |
Features |
PSTASK_REVENUE |
The amount of expected revenue if the feature is implemented. |
High, Low, >5M, <1M |
Risk |
Engineering Tasks |
PSTASK_ENGINEER_RISK |
The amount of risk to destabilizing the product by undertaking the engineering task. |
High, Low |
Server OS |
QA Tests |
PSTASK_SERVER_OS |
The type of operating system running on the server. |
Windows NT |
Source |
Features |
PSTASK_SOURCE |
The source of the feature. |
Customer Input, Market Survey |
Status |
All |
PSTASK_STATUS |
The current implementation or development phase of the release item. |
Draft, Unit Test, Final |
Test Class |
QA Tests |
PS_QA_TEST_STRATEGY_
TEST_CLASS |
The sequence category of the test. |
Certification Pass, Full Pass, Final Pass, Acceptance Pass, Browser Certification |
Test Set |
QA Tests |
PS_QA_TEST_PLAN_TEST_
SET |
The product area applicable to the test. |
Install, Upgrade, Report, Charts, General |
Type |
QA Tests |
PSTASK_ALT_TYPE |
The type of test that is conducted. |
Blitz, Ad Hoc, Detailed, White Glove |
This task is a step in Process of Administering Release Manager. Lists of Values for Special Tag Fields
You must also add a List of Values (LOV) for the Special Tag field in the QA Test Plans view. Table 42 shows an example of how you might set the fields of several new LOV records to populate the Special Tag field with values.
Table 42. Special Tag LOV Examples
|
|
|
|
|
Type |
LOV_TYPE |
PS_TEST_PLAN_SPEC_TAG |
PS_TEST_PLAN_SPEC_TAG |
PS_TEST_PLAN_SPEC_TAG |
Display Value |
PS_TEST_PLAN_SPEC_TAG |
Browser Specific |
EBIZ Specific |
Config. Specific |
Language-Independent Code |
PS_TEST_PLAN_SPEC_TAG |
Browser Specific |
EBIZ Specific |
Config. Specific |
Language Name |
English-American |
English-American |
English-American |
English-American |
Active |
True |
True |
True |
True |
Replication Level |
All |
All |
All |
All |
|
