Siebel Field Service Guide > Release Manager > Administrator Setup Procedures for Release Manager >
Setting Up Lists of Values
The Siebel administrator is typically responsible for setting up lists of values (LOVs) for use in Siebel Business Applications. Although the Status field is shared by all types of release items, the LOVs for the Status field are likely to be 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). To prevent end users from having to sift through long lists of values for phases that are related to their work, you may need to restrict the views in which specific lists of values appear. For information on setting up LOVs and restricting the views associated with specific LOVs, see Siebel Applications Administration Guide. Table 123 displays information about the LOVs to be set up before using Release Manager.
Table 123. Release Manager LOVs
|
|
|
|
|
Client OS |
QA Tests |
PSTASK_CLIENT_OS |
Type of operating system running on the client test machine. |
Windows 2000, Mac OS |
Client Type |
QA Tests |
PSTASK_CLIENT_TYPE |
Type of test machine used by the tester. |
Dedicated, HTML |
Database |
QA Tests |
PSTASK_CLIENT_DB |
Type of database running in the test environment. |
IBM DB2, Microsoft SQL Server 7.0 |
Effort |
Engineering Tasks |
PSTASK_ENGINEER_EFFORT |
Level of effort required of the engineer to complete the task. |
High, Low, 1 Man Month |
Priority |
Features |
PSTASK_PRIORITY |
Relative importance of the feature. |
High, Medium, P1-Critical |
Revenue |
Features |
PSTASK_REVENUE |
Amount of revenue that can be expected if the feature is implemented. |
High, Low, >5M, <1M |
Risk |
Engineering Tasks |
PSTASK_ENGINEER_RISK |
Level of risk to destabilizing the product by undertaking this engineering task. |
High, Low |
Server OS |
QA Tests |
PSTASK_SERVER_OS |
Type of operating system running on the server. |
Windows NT |
Source |
Features |
PSTASK_SOURCE |
Source of the feature. |
Customer Input, Market Survey |
Status |
All |
PSTASK_STATUS |
Current implementation or development phase of the release item. |
Draft, Unit Test, Final |
Test Class |
QA Tests |
PS_QA_TEST_STRATEGY_ TEST_CLASS |
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 |
Product area to which the test was applied. |
Install, Upgrade, Report, Charts, General |
Type |
QA Tests |
PSTASK_ALT_TYPE |
Type of test that was conducted. |
Blitz, Ad Hoc, Detailed, White Glove |
NOTE: In the preceding table, the Type value is the value of the picklist record in the Applications Administration List of Values view.
Special Tag LOVs
You must also add a list of values for the Special Tag field in the QA Test Plans view. Table 124 shows an example of how you might set the fields of several new LOV records to populate the Special Tag field with values.
Table 124. 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 |
|