Professional Documents
Culture Documents
Reports Guide
Serena Proprietary and Confidential Information
Copyright 19882007 Serena Software, Inc. All rights reserved. This document, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by such license, no part of this publication may be reproduced, photocopied, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Serena. Any reproduction of such software product user documentation, regardless of whether the documentation is reproduced in whole or in part, must be accompanied by this copyright statement in its entirety, without modification. The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Serena. Serena assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
Trademarks
Serena, TeamTrack, StarTool, PVCS, Collage, Comparex, and ChangeMan are registered trademarks of Serena Software, Inc. The Serena logo, Dimensions, Professional, Version Manager, Builder, Meritage, RTM, Change Governance, Profit From Change, Command Center, Composer, Reviewer, and Mover are trademarks of Serena Software, Inc. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Table of Contents
Welcome to Dimensions . . . . . . . . . . . . . . . . . . . . . . .
Product Name Changes and New Terminology . Typographical Conventions . . . . . . . . . . . . . . Printing Manuals . . . . . . . . . . . . . . . . . . . . . Contacting Technical Support . . . . . . . . . . . . Chapter 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9 11 11 11
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Dimensions CM Reports . . . . . . . . . . . . . . . . . . . . . . . . Users of Dimensions Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
14 14
Chapter 2
15
16 16 17 20 22 22 22 24 25 26
Chapter 3
29
30 30 30 31 31 31 32 32 33 34 34 34 35 36 36 36 37 38 38 3
Reports Guide
41
42 42 43 44 44 45 46 47 48 49 50 51 52 53 54 55 56 57 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81
Table of Contents pcms_chdoc_action_desc - request action description . . . . . . . . . . . pcms_chdoc_attr_history - historic request attribute information . . . pcms_chdoc_attachments - request attachments, primary catalog . . pcms_chdoc_data - current request information . . . . . . . . . . . . . . . pcms_chdoc_delegation - request delegations . . . . . . . . . . . . . . . . pcms_chdoc_detail_desc - request detailed description . . . . . . . . . . pcms_chdoc_history - request history . . . . . . . . . . . . . . . . . . . . . . pcms_chdoc_history_with_attr - request history with attributes . . . . pcms_chdoc_norm_lc - normal lifecycle for requests . . . . . . . . . . . . pcms_chdoc_related_baselines - request and related baselines . . . . pcms_chdoc_related_chdoc - related request information . . . . . . . . pcms_chdoc_related_items - requests and related items . . . . . . . . . pcms_chdoc_related_parts - requests and related design parts . . . . pcms_chdoc_related_worksets - request project relationships . . . . . pcms_chdoc_this_action_desc - request current action description . . pcms_chdoc_types - request type information . . . . . . . . . . . . . . . . pcms_chdoc_user_lists - request user lists . . . . . . . . . . . . . . . . . . . pcms_cm_catalogue - basic request information . . . . . . . . . . . . . . . pcms_command_statistics - command statistics . . . . . . . . . . . . . . . pcms_customer_details - customer information . . . . . . . . . . . . . . . pcms_customer_releases - releases forwarded to customers . . . . . . pcms_deployment_history - deployment history . . . . . . . . . . . . . . . pcms_derived_formats - one-to-one derived build relationship . . . . . pcms_environment_items - environment item definitions. . . . . . . . . pcms_groups - groups definitions . . . . . . . . . . . . . . . . . . . . . . . . . pcms_group_members - group members . . . . . . . . . . . . . . . . . . . . pcms_ipds - Item Process Definitions registered against a product . . pcms_item_attributes - product item attribute information. . . . . . . . pcms_item_attr_history - historic product item attribute information. pcms_item_data - current item information . . . . . . . . . . . . . . . . . . pcms_item_delegation - item delegations . . . . . . . . . . . . . . . . . . . pcms_item_exports - items checked out by users . . . . . . . . . . . . . . pcms_item_history - history of items. . . . . . . . . . . . . . . . . . . . . . . pcms_item_history_with_attr - item update history including attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_item_norm_lc - normal lifecycle for product items . . . . . . . . . pcms_item_pending_actions - users and their items to be actioned. . pcms_item_related_items - user-defined relations between items. . . pcms_item_related_parts - items and their related design parts . . . . pcms_item_revision_history history of item revisions . . . . . . . . . . pcms_item_types - product item type information. . . . . . . . . . . . . . pcms_life_cycles - lifecycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_mail_notif - e-mail notifications . . . . . . . . . . . . . . . . . . . . . . pcms_mail_subscribers - e-mail notification subscribers . . . . . . . . . pcms_make_instance_catalogue - network nodes used in the Dimensions Make process . . . . . . . . . . . . . . . . . . . . . . pcms_make_mo_list - made-of list for items resulting from Dimensions Make. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 83 84 85 87 88 89 90 91 92 93 94 95 96 97 98 99 100 102 103 104 105 106 107 108 109 110 111 112 113 115 116 117 118 119 120 121 122 123 124 126 127 128 129 130
Reports Guide
Table of Contents pcms_mo_list - made-of list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_part_attributes - design part attribute information . . . . . . . . . pcms_part_attr_history - historic design part attribute information . . pcms_part_data - design part information . . . . . . . . . . . . . . . . . . . pcms_part_history - design part update history . . . . . . . . . . . . . . . pcms_part_history_with_attr - design part update history including attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_part_types - design part type information . . . . . . . . . . . . . . . pcms_parts_structure - structural relationships between design parts pcms_privileges - privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_privilege_rules_enabled - privilege rules enabled . . . . . . . . . . pcms_product_attributes - product attribute information . . . . . . . . . pcms_product_attr_upd_history - product attribute update history . . pcms_product_catalogue - product catalog. . . . . . . . . . . . . . . . . . . pcms_release_data - release information . . . . . . . . . . . . . . . . . . . . pcms_release_items - items in releases . . . . . . . . . . . . . . . . . . . . . pcms_release_template - release templates . . . . . . . . . . . . . . . . . . pcms_replicator_branches - branches replicated . . . . . . . . . . . . . . . pcms_replicator_chdoc_types - replicator request types . . . . . . . . . pcms_replicator_configs - registered replication configurations . . . . . pcms_replicator_configs_rels - subordinate definitions in a master definition . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_replicator_receive - inward transfers received . . . . . . . . . . . . pcms_replicator_receive_cdocs -requests received . . . . . . . . . . . . . pcms_replicator_receive_items - item revisions received . . . . . . . . . pcms_replicator_receive_logs - text logs received . . . . . . . . . . . . . . pcms_replicator_transfer - outward transfers . . . . . . . . . . . . . . . . . pcms_replicator_transfer_cdocs - requests for transfer . . . . . . . . . . pcms_replicator_transfer_items - items for transfer . . . . . . . . . . . . pcms_replicator_transfer_logs - text logs associated with outward transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_report_chdoc_data - current request information used for reporting purposes. . . . . . . . . . . . . . . . . . . . . pcms_role_sections - role sections . . . . . . . . . . . . . . . . . . . . . . . . pcms_rtm_dm_project_col_xref - RM collections associations. . . . . . pcms_rtm_object - requirements associations . . . . . . . . . . . . . . . . pcms_rtm_project_product_xref - Dimensions RM project association pcms_rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_rule_privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_sec_chdoc_action_desc - secondary request action description pcms_sec_chdoc_attachments - request attachments, secondary catalog . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_sec_chdoc_attr_history - historic secondary request attribute information . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_sec_chdoc_data - secondary request information . . . . . . . . . . pcms_sec_chdoc_detail_desc - secondary request detailed description pcms_sec_chdoc_history - secondary request history . . . . . . . . . . . pcms_sec_history_with_attr - secondary request history with attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 151 152 153 154 155 156 157 158 159 160 162 163 164 165 166 167 168 169 170 171 172 173 174
Table of Contents pcms_sec_status_rpt1 - secondary requests on normal lifecycle . . . . pcms_sec_this_action_desc - secondary request current action description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . pcms_sites - registered base database sites . . . . . . . . . . . . . . . . . . pcms_status_rpt1 - requests on normal lifecycle. . . . . . . . . . . . . . . pcms_strings_db - Dimensions Make commands used to make an item pcms_user_attributes - user attribute information. . . . . . . . . . . . . . pcms_user_attributes_def - user defined attributes . . . . . . . . . . . . . pcms_user_attr_update_history - user attribute update history . . . . pcms_user_audit_trail - user audit trail . . . . . . . . . . . . . . . . . . . . . pcms_user_pending_chdoc - user and pending request information . pcms_user_roles - roles allocated to users . . . . . . . . . . . . . . . . . . . pcms_users_profile - registered users . . . . . . . . . . . . . . . . . . . . . . pcms_valid_set_view - valid sets . . . . . . . . . . . . . . . . . . . . . . . . . pcms_workset_attributes - project attributes . . . . . . . . . . . . . . . . . pcms_workset_components - project components. . . . . . . . . . . . . . pcms_workset_history - project history . . . . . . . . . . . . . . . . . . . . . pcms_workset_info - project information . . . . . . . . . . . . . . . . . . . . pcms_workset_items - Items in projects . . . . . . . . . . . . . . . . . . . . pcms_workset_norm_lc - normal lifecycle for projects . . . . . . . . . . . pcms_workset_related_chdocs - project request relationships . . . . . Use of the Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . List of Open Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Request Selected on Multi-Valued Attributes. . . . . . . . . . . . . . . . . . Requests Pending for a User and Related Parts . . . . . . . . . . . . . . . . Nested Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hierarchical Queries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 176 177 178 179 180 181 183 184 185 186 187 188 189 190 191 192 193 194 195 196 196 196 197 197 198
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
Reports Guide
Table of Contents
Welcome to Dimensions
Thank you for choosing Serena Dimensions CM, a powerful process management and change control system that will revolutionize the way you develop software. Dimensions helps you organize, manage, and protect your software development projects on every levelfrom storing and tracking changes to individual files, to managing and monitoring an entire development cycle. Purpose of this manual This manual: Describes the setting up and running of the Dimensions command-line reports. Describes how to set up Dimensions User Reports from the Administration Console for subsequent running with the Run User Reports (RUR) command. (The RUR command is described in the Command-Line Reference Guide.) Gives details on Dimensions views available to users for writing SQL-based reports. It provides field descriptions, descriptions of each view, and operating and installation instructions. This manual is intended for users of Dimensions from various platforms who have roles affecting the objects for which reports are to be generated. For more information Refer to the Introduction to Serena Dimensions CM for a description of the Dimensions documentation set, a summary of the ways to work with Dimensions, and instructions for accessing the Online Help. Refer to the Serena Dimensions CM Command-Line Reference for details of how to run command-line reports.
Reports Guide
Welcome to Dimensions The above product name changes have also led to changes in the Dimensions documentation set. Refer to the Introduction to Dimensions CM manual for a comprehensive list of the Dimensions documentation set. The following table details the terminology changes: Current terminology custom list/request list custom list/request list deployment area deployment stage inbox library cache privilegec project project working location request user interface profilec work areac areac Legacy terminology user lista custom listb build area build stage pending list n/a n/a workset workset root directory change document n/a n/a
a.Desktop client. b.Web client and Visual Studio integration. c.New term. See the User's Guide and Process Modeling Guide for details of these new terms. The latest Dimensions 10.1 documentation reflects the new terms, so if you are using a new Dimensions 10.1 component with a component from an earlier release of Dimensions (for example, the Migration Console in conjunction with Dimensions 9.1), you must bear in mind the terminology changes when working with the older components.
NOTE To ensure backward compatibility with existing customer applications, certain specialized features will continue to use legacy terminology, but the new terminology will be used when describing these features in the documentation. These features comprise: The Dimensions Command-Line Interface (dmcli). The public Dimensions C /C++ Developer's Toolkit and Java API (dmpmcli). This includes both the application interfaces and the manifest constants that come as part of this API. The Dimensions Data Interchange File Format (PDIFF).
10
Typographical Conventions
Typographical Conventions
The following typographical conventions are used in the online manuals and online help. These typographical conventions are used to assist you when using the documentation; they are not meant to contradict or change any standard use of typographical conventions in the various product components or the host operating system. italics bold UPPERCASE monospace Introduces new terms that you may not be familiar with and occasionally indicates emphasis. Emphasizes important information and field names. Indicates keys or key combinations that you can use. For example, press the Enter key. Indicates syntax examples, values that you specify, or results that you receive. Indicates names that are placeholders for values you specify; for example, filename. Indicates the results of an executed command. Separates menus and their associated commands. For example, select File | Copy means to select Copy from the File menu. Also, indicates mutually exclusive choices in a command syntax line. Indicates optional items. For example, in the following statement: SELECT [DISTINCT], DISTINCT is an optional keyword. Indicates command arguments that can have more than one value.
monospace italics
monospace bold vertical rule |
brackets []
Printing Manuals
As part of your Dimensions license agreement, you may print and distribute as many copies of the Dimensions manuals as needed for your internal use, so long as you maintain all copies in strict confidence and take all reasonable steps necessary to ensure that the manuals are not made available or disclosed to anyone who is not authorized to access Dimensions under your Dimensions license agreement.
Reports Guide
11
Welcome to Dimensions Language-specific technical support is available during local business hours. For all other hours, technical support is provided in English. The Serena Support Web page can also be used to: Report problems and ask questions. Obtain up-to-date technical support information, including that shared by our customers via the Web, automatic E-mail notification, newsgroups, and regional user groups. Access a knowledge base, which contains how-to information and allows you to search on keywords for technical bulletins. Download fix releases for your Serena products.
12
Chapter 1 Introduction
Introduction to Dimensions CM Reports 14
Reports Guide
13
Chapter 1 Introduction
14
Reports Guide
15
Introduction
This chapter lists and describes the functions and types of reports that can be undertaken when generating command-line ASCII format reports. For full details of the Dimensions command-line reports and options, see the Command-Line Reference.
OR
Database
Pre-Processor
Export File
Report Program
The pre-processor extracts complete structure details on the required product (or specified part of it) from the database and stores them in an export-file within the user-area. Please note that, despite the name used for it, this is not the same thing at all as an "export of the database". These 'export-files' are not suitable as backups of database contents, as they can be used only for producing reports of this snapshot of the database, and/or for comparing two snapshots from the same or different databases. The pre-processor phase can be bypassed where an existing file already holds the required product-structure details. This provision can save a considerable amount of time where a number of different reports of the same product-structure are required. An export file can also be retained for future use, e.g. to print a report of differences between it and the product-structure as developed subsequently. In joint-development environments, an export-file can be used in conjunction with the transfer of a product release to another database or installation. In this case, the file can be compared with the recipient's existing database to highlight any differences in the new release. The report-option programs provide a number of variations in product-structure reporting. A report may be based on:
16
Product Structure Reports the current product-structure the product-structure secured by a baseline the previously saved export-files, based on either a baseline or the then-current product-structure. In addition the differences between any two of the above structure sources can also be reported. Product-structure reports are provided as follows. Report Report Current Items Report Current Parts Report Design Structure Compare Structures or Baselines Command RCI RCP RDS CMP
Limitations Users initiating the following reports must have a valid role for the top design part being reported. In a structure-report whose structure is to include items, when an item has two or more revisions currently at the same lifecycle state, only the latest (most recently created/updated) of these is shown.
Report on Parts
Reports on Parts are implemented via RCI, RCP and RDS from the command line. These provide the following reporting functions. Report on Items The RCI command: This produces a report for all items found in the product-structure. If no export file is specified, the file name defaults to item_list.out. You may order by item identifier only. Report on Parts The RCP command: This produces a report for all design parts found in the product structure. You may choose to sort by part identifier or part number. Report on Product Structure The RDS command: This produces a structure-level report for a product-structure down to a certain number of levels (or to all levels), optionally including items, requests, user roles and usage relationships. The reports generated by choosing the part FS:CABIN.A;1, with all report options being at their default values, are shown on the following pages:
Reports Guide
17
REPORT CURRENT ITEMS Parameters : RCI tmp_file_xrep_1b73.tmp /NEW /SORT=IID /PART="FS:CABIN.A;1 User Date : USER1 : 17/Mar/99 17:20
17/Mar/99 17:20 Item id CABIN CABIN CABIN AIR CABIN AIR CABIN DOOR CABIN DOOR CABIN LIGHTS CABIN LIGHTS
CURRENT ITEMS REPORT Item Type OBJ SRC OBJ SRC OBJ SRC OBJ SRC Revision 1 2 1 2 1 2 1 2
TOP PART: CABIN Status COMPILED APPROVED COMPILED APPROVED COMPILED APPROVED COMPILED APPROVED Filename cabin.o cabin.c cab_air.o cab_air.c cab_door.o cab_door.c cablight.o cablight.c
Page 1 Ver 1 2 1 2 1 2 1 2
18
REPORT CURRENT PARTS Parameters : RCP tmp_file_xrep_1b73.tmp /OLD /SORT=PID /PART="FS:CABIN.A;1 User Date : USER1 : 17/Mar/99 17:21
17/Mar/99 17:21 Part id CABIN CABIN AIR CABIN DOOR CABIN AIR
Page 1
Cabin Envrnmnt Sub-system Cabin air conditioning systems Cabin door Cabin lighting systems
REPORT DESIGN STRUCTURE Parameters : User Date RDS */STRUCTURE=ALL /PART="FS:CABIN.A;1 : USER1 : 17/Mar/99 17:21
Reports Guide
19
CABIN.A;1 (SUB-SYSTEM) Roles USER1 USER1 USER1 ROBER T USER1 USER1 USER1 USER1 Items CABIN CABIN 1 Items CABIN AIR CABIN AIR 1 CABIN DOOR.A;1 (MODULE) Items CABIN DOOR CABIN DOOR 1 CABIN LIGHTS.A;1 (MODULE) Items CABIN LIGHTS CABIN LIGHTS A A -OBJ -SRC ;1 ;2 COMPILED APPROVED OWNER OWNER A A -OBJ -SRC ;1 ;2 COMPILED APPROVED OWNER OWNER A A -OBJ -SRC ;1 ;2 COMPILED APPROVED OWNER OWNER .A .A CABIN AIR.A;1 (MODULE) -OBJ -SRC ;1 ;2 COMPILED APPROVED OWNER OWNER (ANALYST) (AUTHOR) (CHANGE REVIEWER) (ENGINEER) (ENGINEER) (LEAD) (QA) (REVIEWER)
Report on Baseline
Reports on Baselines are implemented via RCI, RCP and RDS from the command-line. Report on Items The RCI command: This produces a report for all baselined items found in the product-structure. If no export file is specified, the file name defaults to item_list.out. You may order by item identifier only. Report on Parts The RCP command: This produces a report for all baselined design parts found in the product structure. You may order by part identifier (default) or part number. Report on Product Structure The RDS command: This produces a structure-level report for the baselined product-structure down to a certain number of levels (or to all levels), optionally including items, requests, user roles and usage relationships. As an example, the reports generated by choosing the baseline FS:CABIN_BL1 are shown below:
20
REPORT CURRENT ITEMS Parameters : RCI tmp_file_xrep_33c3.tmp /NEW /SORT=IID /BASELINE="FS:CABIN.A;1 User Date USER1 17/Mar/99 18:37
17/Mar/99 18:37 Item id CABIN CABIN CABIN AIR CABIN AIR CABIN DOOR CABIN DOOR CABIN LIGHTS CABIN LIGHTS
CURRENT ITEMS REPORT Item Type OBJ SRC OBJ SRC OBJ SRC OBJ SRC Revision 1 2 1 2 1 2 1 2
BASELINE: CABIN_BL1 Filename cabin.o cabin.c cab_air.o cab_air.c cab_door.o cab_door.c cablight.o cablight.c
Page 1 Ver 1 2 1 2 1 2 1 2
REPORT CURRENT PARTS Parameters : RCP tmp_file_xrep_33c3.tmp /OLD /SORT=PID /BASELINE="FS:CABIN.A;1 User Date USER1 17/Mar/99 18:37
Reports Guide
21
Chapter 2 Dimensions Standard Command-Line and ASCII Reports 17/Mar/99 18:37 Part id CABIN CABIN AIR CABIN DOOR CABIN AIR PRODUCT: FS Var A A A A PCS 1 1 1 1 CURRENT ITEMS REPORT Local Part no. BASELINE: CABIN_BL1 Description Cabin Envrnmnt Sub-system Cabin air conditioning systems Cabin door Cabin lighting systems Page 1
Part no.
Selection Criteria
All request reports cover a selection from the full set of requests recorded in the system. Some of the criteria used for this selection are mandatory for all reports, but there are other optional criteria that are useful in special cases.
22
Change Management Reports The first criterion is the report type, which may be: /CATALOGUE /CATALOGUE/SECONDARY /PENDING Most reports are provided for all types, but some (notably USER_CHDOC) are only available in one type. The report type is combined with other selection criteria to affect the choice of requests for a report, and this is discussed below. The other mandatory criteria are the product-id for the product owning the requests to be reported, and the request category. The request type should also be specified. There follows a set of optional criteria, which must be matched exactly if specified (i.e. no wild cards), or which default to "any" if not specified. Part_Id Phase This specifies the phase which all requests to be selected are currently in. So a report could cover just documents in the WORK phase. This may specify a user's login identity, and this is combined with the report type in selecting requests. See below. This may specify a starting date, and this is combined with the report type in selecting requests. See below. This may specify a finishing date, and this is combined with the report type in selecting requests. See below.
The report type is combined with these last three criteria in the selection of requests for the report. For a "main/secondary catalog" report, requests will be selected (subject to the other criteria) if they have been actioned or created by the specified user within the given period. The defaults are, of course, "any user" or "any date". In the case where neither a user nor a period is given, a "catalog" report will be able to cover all requests including those that have reached the end of their lifecycles. For a "pending" report, requests will be selected (subject to the other criteria) if they have been passed for actioning to the specified user within the given period, and are still awaiting action by that user. The defaults are, of course, "any user" or "any date". In the case where neither a user nor a period is given, a "pending" report will be able to cover all requests that are still to be actioned by some userthat is any request apart from those that have reached the end of their lifecycles. As well as all the above, the request selection may be further refined by specifying (if required) the request identity, current lifecycle status and the values of certain user-defined attributes including attribute-1 (conventionally the request title).
Reports Guide
23
Report Types
The table shown below lists the available report types. The left column gives the report type and the right column gives the title. Reports must be selected from either the Catalog or projects as defined by the middle column of this table. Report Type CH_DOC_LIST CH_DOC_LIST CHDOC_PART_ITEM CHDOC_PART_ITEM DEPENDENCY_REP DEPENDENCY_REP USER_CHDOC FULL_HISTORY FULL_HISTORY ACTION_HISTORY ACTION_HISTORY PART_CHDOC_ITEM_R PART_CHDOC_ITEM_R PART_CHDOC_ITEM_S PART_CHDOC_ITEM_S PARM_11_12 PARM_11_12 PARM_12_11 PARM_12_11 BASELINE_DETAIL Catalog or Pending C P C P C P P C P C P C P C P C P C P n/a
Title The ch_doc catalog The ch_docs pending Ch_docs and all related design parts and items Ch_docs and all related design parts and items Ch_docs and their dependent requests Ch_docs and their dependent requests Ch_docs outstanding for users Ch_doc action or update history report Ch_doc action or update history report Request History Report (Action History) Request History Report (Action History) Recursive: design parts, related ch_docs, items Recursive: design parts, related ch_docs, items Single: design parts, related ch_docs, items Single: design parts, related ch_docs, items Ch_doc catalog ordered by report parameters 11 and 12 Ch_docs pending ordered by report parameters 11 and 12 Ch_doc catalog ordered by report parameters 12 and 11 Ch_docs pending ordered by report parameters 12 and 11 Baseline detail report
24
DEPENDENCY_REP
USER_CHDOC
FULL_HISTORY
ACTION_HISTORY
PART_CHDOC_ITEM_R
PART_CHDOC_ITEM_S
PARM_11_12
Reports Guide
25
Chapter 2 Dimensions Standard Command-Line and ASCII Reports Type PARM_12_11 Description This report lists all requests which match the selection criteria, and includes user-defined attributes 2 and 3 which are identified as parameters 11 and 12. This report is sorted according to user-defined attribute 3 (parameter 12). This report lists all baselines which match the selection criteria. The items listed within the baseline are reported, together with a list of requests which cite those items. The report is sorted such that items which are cited in requests are listed before items which are not. The report can only print user-defined attributes 1, 2, 3, 12 and 20; and can only sort by user-defined attributes 2 and 3.
BASELINE_DETAIL
26
Serena
The ch_doc catalogue Request Catalogue List The ch_doc catalogue Dimensions Report Parameters: 1 Product id 2 Change Category 3 Ch_doc Type 4 Ch_doc Phase 5 Ch_doc Status 6 Ch_doc_id 7 Design Par User name: USER1 File name : report.rpt1 : FS :1 : PR :% :% :% : %.%
20-Mar-1999 14:03
This report lists requests. The requests selected are those which match the parameters above
The character % on its own means select all, combined with other characters means select matching patterns. This is a catalogue report, so it will include all requests which meet the selection criteria and which have been created or actioned by all Users, or by a specified User, between the dates shown as Period From and Period To.
Reports Guide
27
PROBLEM SOLVED
21-FEB-1999
21-FEB-1999
1_critical
A Continuous Bleeping occurs when invoking print function FS_PR_2 FS_PR_3 FS_PR_4 FS_PR_5 FS_PR_6 AN+WORK AN+WORK yet again AN+WORK yet again again AN+WORK AN+WORK RAISED RAISED 14-MAR-1999 14-MAR-1999 14-MAR-1999 14-MAR-1999 2_severe 3_mderate user3 FS fails, core dump Emilio's Change Document No.1 FS_PR_7 FS_PR_8 FS_PR_9 junk FS_PR_10 test [End of Report] AN+WORK RAISED 2_severe AN+WORK AN+WORK AN+WORK RAISED RAISED RAISED 4_minor 1_critical 4_minor This a test prob report from JP <user_id> FS fails, core dump RAISED 24-FEB-1999 24-FEB-1999 2_severe RAISED RAISED 24-FEB-1999 24-FEB-1999 24-FEB-1999 24-FEB-1999 3_mderate 2_severe This is to set up training
28
Reports Guide
29
30
Reports Guide
31
The color of the report definition icon indicates the operating system: VMS UNIX Windows Select the top-level Reports icon to view a list of all the report definitions for the applied filter:
Select any report definition to view its details and associated report files in the content area.
32
User Reports Administration Main Window If you select the User Report Files tab, the navigation area allows you to: Select the top-level Report Files icon to view a list of all the report files in the base database.
Select any report file to view its details in the content area.
Then the content area displays... A list of report definitions that exist in the base database, based on the filter applied. : Select one or more objects. : Select all objects. : Display a summary of the objects in an HTML page (suitable for printing). : Display a summary of the objects as comma-separated values in a text file.
A report definition
General section: displays details about the selected report definition and allows you to edit them. Report Parameters section: displays the parameters defined for the report and allows you to edit them. Report File section: lists the report files assigned to the report definition. Allows you to add, assign, export, import, and unassign report files, as well as designate a report file as the default executable file.
Reports Guide
33
Chapter 3 User Reports Administration On the... User Report Files tab If you select... The top-level Report Files icon Then the content area displays... A list of report files that exist in the base database. : Select one or more objects. : Select all objects. : Display a summary of the objects in an HTML page (suitable for printing). : Display a summary of the objects as comma-separated values in a text file. User Report Files tab A report file General section: displays details about the selected report file. Used By section: displays details about the report definition(s) to which the report file is assigned.
Enter the ID for the report in the Name field, up to 25 characters. Select the operating system of the Dimensions server against which the report will be run from the Op System list.
34
Creating User Report Definitions WIN: Windows operating systems. VMS: VMS operating systems NOTE On Dimensions 8 and later, you cannot run any VMS- based reports.
UNIX: UNIX operating systems. 5 Select the functional area of Dimensions to which the report will belong from the Scope list: All Scopes: Accessible from the change management, design part, and version management functional areas. Change Management: Accessible from the change management area only. Design Part: Accessible from the design part area only. Version Management: Accessible from the version management area only. 6 7 Optionally, complete the rest of the fields in the dialog box. Click OK.
Reports Guide
35
Enter the report file name in the ID field, up to 25 characters. Enter the revision level for the report file in the Revision field, up to 15 characters. Enter the name and location of the file to be added to the database in the File location to add from field, or use the browse button to select it. Enter the name of the report file to be run in the Filename when running report field, up to 240 characters. (optional) If assigning the new report file to a report definition, select the Runs Report? check box to designate this report file as the main file for executing the report. Click OK.
36
Managing User Report Files To assign an existing report file to a report definition: 1 From the User Reports Administration main window, on the User Reports Definition tab, select the report definition to which you want to add the report file in the navigation area. In the Report Files section of the content area, click the Add button: Existing Report File. The Assign Report File dialog box appears. 3 4 5 Select the report file that you want to assign from the Existing report file list. Optionally, select the Runs report? check box to execute this file when a user runs the report. Click OK. and select
To unassign a report file from a report definition: 1 2 In the Report Files section of the content area, select the file that you want to unassign or delete. Click the Delete button: The Unassign Report dialog box appears. 3 4 Optionally, uncheck the Delete report file from database? check box if you want to keep the report file in the database. Click Yes to unassign the report file. NOTE You cannot unassign a report file if it's designated as the default report. Assign another file as default and then delete the report file. To set a report file as the default executable file: 1 2 3 In the Report Files section of the content area, select the file that you want to set as the default executable file. Click the Set as Default button: .
In the Set Default Report dialog box, click OK to confirm that you want this file to be executed when the report is run.
Reports Guide
37
Chapter 3 User Reports Administration 3 Click the Export Report File button: The Export Report File dialog box appears. 4 5 In the Export File location field, enter the name and location of the file to contain the contents of the report file, or use the browse button to select it. Click OK.
To import a report file: 1 2 In the Report Files section of the content area, select the file that you want to import a new file for. Click the Import Report File button: The Import Report File dialog box appears. 3 4 In the File location to add from field, enter the name and location of the file with which to update the report file, or use the browse button to select it. Click OK.
38
Running User Reports Stage Description Dimensions executes the main user report file with the statement: UNIX /bin/sh <command script file> \ <product-range> <other parameters> Windows <command script file> - <product-range> <other parameters> Dimensions outputs the report to the specified file.
5 6
For help with using the RUR command, see the Command-Line Reference and the User's Guide.
Reports Guide
39
40
Reports Guide
41
Introduction
From time-to-time users may require access to the database, particularly when they wish to supplement the standard reports with specially written reports. One method is to write programs in C, using the API routines described in the related document Developer's Toolkit Reference Guide to extract information from the database. It may be preferred to use a report writer, and several are available that enable users to interrogate a database and to format the results into useful reports. Such users need database views that can be maintained even when there are changes in the underlying database schema. The views described in this document are of two types: those that need to be generated to incorporate definitions taken from the user's current schema and those that are supplied in fixed form. Schema objects other than the Views defined in this document should not be used for Report purposes as Serena reserves the right to modify the underlying schema at any time in the future. The majority of objects managed by Dimensions are associated with a Unique Identifier (UID) which is held in the corresponding database tables. The UID for any object is a number uniquely allocated to the object at its creation. The UID is used to join different tables referring to the object, and it has no other meaning. Many of the views return UIDs for relevant objects, so that these may be used in subsidiary queries.
42
Reports Guide
43
44
Reports Guide
45
46
Reports Guide
47
48
Reports Guide
49
50
Reports Guide
51
52
Reports Guide
53
54
Reports Guide
55
56
Reports Guide
57
Chapter 4 The Published Views lc_seq The sequence number of the current lifecycle status within the normal lifecycle. workset_uid The UID of the project from which the baseline was created. workset The name of the project from which the baseline was created.
58
Reports Guide
59
60
pcms_baseline_norm_lc
This view provides information on the normal lifecycle for types of baselines. product_id The name of the product to which the baselines belong. baseline_type The baseline type. type_uid The UID corresponding to the baseline type as defined on the relevant product. state_seq_no The sequence number of the lifecycle state within the normal lifecycle. status The name of a state in the normal lifecycle for the baselines of the type and product concerned. lifecycle_id The lifecycle ID.
Reports Guide
61
62
Reports Guide
63
64
Reports Guide
65
66
Reports Guide
67
68
Reports Guide
69
70
Reports Guide
71
72
Reports Guide
73
74
Reports Guide
75
76
Reports Guide
77
78
Reports Guide
79
pcms_bln_rels2
This view provides information on baseline relationships. rel_uid The unique identifier of the relationship. obj_uid The unique identifier of the baseline. related1_uid The unique identifier of the first related object. related2_uid The unique identifier of the second related object. reltype_uid The unique identifier of the relationship type. user_name The user who created the relationship. date_time The date and time when the relationship was created.
80
Reports Guide
81
82
Reports Guide
83
84
Reports Guide
85
Chapter 4 The Published Views delegated_site The site to which the request has been delegated. locked This is 'Y' or 'N' to indicate whether the request ownership is locked or not. reference_only This is 'Y' or 'N' to indicate whether the request is reference only (cannot be updated). user_name The login identity of the last user to action the request. seq A number indicating the ordering of multi-valued attributes. Attribute fields One attribute field corresponding to each possible attribute as defined through Object Type Definitions in the process model. The field name in each case is the same as the variable_name, and the retrieved length of the field is either the maximum length as defined in the Process Model, or 1978, whichever is the shorter.
86
Reports Guide
87
88
Reports Guide
89
90
Reports Guide
91
92
Reports Guide
93
94
Reports Guide
95
96
Reports Guide
97
98
Reports Guide
99
100
The Published Views owner_site The site that owns the request. delegated_site The site to which the request has been delegated. locked This is 'Y' or 'N' to indicate whether the request ownership is locked or not. reference_only This is 'Y' or 'N' to indicate whether the request is reference only (cannot be updated). cat_loc This is 'M' for a request in the main catalog or 'S' for a request in the secondary catalog. title The value of the first attribute field for the request: that is, the value of attribute number 1. This is normally used to hold the title of the request. If attribute definitions have been changed in the Process Model, or if it is desired to access the values of other attributes, the pcms_chdoc_data view (page 85) should be used instead (see also "Notes about Published Views" on page 43).
Reports Guide
101
102
Reports Guide
103
104
Reports Guide
105
106
Reports Guide
107
108
Reports Guide
109
110
Reports Guide
111
112
Reports Guide
113
Chapter 4 The Published Views format The format of the item (upper case). on_line This is either 'Y' or 'N' to indicate whether the item file is online in its item library, or has been placed offline by means of Dimensions ART. lib_file_length The library file length of the item lib_checksum The current checksum of the item.
114
Reports Guide
115
116
Reports Guide
117
118
Reports Guide
119
120
Reports Guide
121
122
Reports Guide
123
124
The Published Views primary_cons This is 'Y' or 'N' to indicate whether it is a requirement for actioning items that there should be exactly one user with a primary role at the resulting state, or not. leader_cons This is 'Y' or 'N' to indicate whether it is a requirement for actioning items that there should be exactly one user with a leader role at the resulting state, or not. all_user_overwrite This is 'Y' or 'N' to indicate whether (if the overwrite_initial flag is 'Y') an item revision may be edited at the initial state by any user with the appropriate role (Y), or only by the originator (N). checksum_on This is 'Y' or 'N' to indicate whether checksum calculation is enabled, or not. use_gui_editor This is 'Y' or 'N' to indicate whether the inline editor will be used for items of this type, or not. cntrl This is 'Y' or 'N' to indicate whether Change Management Rules are enabled or not. chdoc_req This is 'Y' or 'N' to indicate if a valid request is required before an item of this type can be created.
Reports Guide
125
pcms_life_cycles - lifecycles
This view returns details on lifecycles. Each row corresponds to one transition within a lifecycle. The following fields are returned: lifecycle_id The name of the lifecycle. doc_status The name of the state at the start of the transition. role The role for which the transition is enabled. next_doc_status The name of the state at the end of the transition. norm_lc This is 'Y' if the transition is part of the normal lifecycle.
126
Reports Guide
127
128
Reports Guide
129
view pcms_item_data on
130
Reports Guide
131
132
Reports Guide
133
134
Reports Guide
135
136
Reports Guide
137
138
pcms_privileges - privileges
This view returns details about privileges. The following fields are returned: priv_no The number of the privilege. priv_id The name of the privilege. priv_type The type of privilege. This can be any of the following: 1 (part) 2 (item) 3 (base database) 4 (baseline) 8 (request) 12 (product) 16 (release) 64 (project) description The description of the privilege.
Reports Guide
139
140
Reports Guide
141
142
Reports Guide
143
144
Reports Guide
145
146
Reports Guide
147
148
Reports Guide
149
Chapter 4 The Published Views no_network Online or offline (air gap) replication.
150
Reports Guide
151
152
Reports Guide
153
154
LOG_CHDOC
LOG_BASELINE
LOG_INFO
obj_uid If "log_type" is "LOG_ITEM" this field identifies the uid of the item: join with "item_uid" in the standard view pcms_item_data - current item information on page 113 for details on the item revision. If "log_type" is "LOG_CHDOC", this field identifies the uid of the request: join with "ch_uid" in the standard view pcms_chdoc_data - current request information on page 85 for details of the request. If "log_type" is "LOG_BASELINE", this field identifies the uid of the baseline: join with "base_seq_no" in the standard view pcms_baseline_info - current baseline information on page 57 for details of the baseline. line_order_seq This field is supplied for convenience when using ORDER BY clauses. It can be used to show the line order of the transfer log. The values themselves have no intrinsic meaning. log_text The log text.
Reports Guide
155
156
Reports Guide
157
158
LOG_CHDOC
LOG_BASELINE
LOG_INFO
obj_uid If "log_type" is "LOG_ITEM", this field identifies the uid of the item revision: join with "item_uid" in the standard view pcms_item_data - current item information on page 113 for details of the item. If "log_type" is "LOG_CHDOC", this field identifies the uid of the request: join with "ch_uid" in the standard view pcms_chdoc_data - current request information on page 85 for details of the request. If "log_type" is "LOG_BASELINE", this field identifies the uid of the baseline: join with "base_seq_no" in the standard view pcms_baseline_info - current baseline information on page 57 for details of the baseline. line_order_seq This field is supplied for convenience when using ORDER BY clauses. It can be used to show the line order of the transfer log. The values themselves have no intrinsic meaning. log_text The log text.
Reports Guide
159
160
The Published Views user_name The login identity of the last user to action the request. seq A number indicating the ordering of multi-valued attributes. Attribute fields One attribute field corresponding to each possible attribute as defined through Object Type Definitions in the process model. The field name in each case is the same as the variable_name, and the retrieved length of the field is either the maximum length as defined in the Process Model, or 1978, whichever is the shorter.
Reports Guide
161
162
Reports Guide
163
164
Reports Guide
165
pcms_rules
This view returns details on rules, including the rule number, ID, and description. rule_no The rule number. rule_id The rule name. description Description of the rule.
166
pcms_rule_privileges
This view returns details on which rules are applicable for each privilege, including the privilege number, privilege ID, rule number, and rule ID. priv_no The privilege number. priv_id The privilege name. rule_no The rule number. rule_id The rule name.
Reports Guide
167
168
Reports Guide
169
170
Reports Guide
171
172
Reports Guide
173
174
Reports Guide
175
176
Reports Guide
177
178
Reports Guide
179
180
Reports Guide
181
Chapter 4 The Published Views default_value The default value for the attribute as defined in the Administration Console. all_revisions_same_value Flag which can be Y or N which sets whether the attribute value is the same for subsequent revisions.
182
Reports Guide
183
184
capability The capacity in which the request has been actioned to the user. This may be P (for primary), S (for secondary) or L (for leader).
Reports Guide
185
186
Reports Guide
187
188
Reports Guide
189
190
Reports Guide
191
192
Reports Guide
193
194
Reports Guide
195
Nested Queries
This example is a report listing all requests of type PR on the product PAYPHONE, and for each request listing all related design parts and all related requests. This is done by three queries: one outer query enclosing two inner queries. The outer query is very similar to the first example: select ch_uid, ch_doc_type, doc_seq, ch_doc_id, status, create_date, originator, title from pcms_chdoc_data where product_id = 'PAYPHONE' and ch_doc_type = 'PR' and seq = 1 order by 2, 3; This query is arranged to return ch_uid into a host variable :outer_ch_uid (the syntax varies between report writers). For each request returned by the outer query, two inner queries are performed. The first of these gets the related design parts: select product_id, part_id, variant, pcs, reltype_name, parent_class_name from pcms_chdoc_related_parts a, pcms_part_data b where a.from_ch_uid = :outer_ch_uid and a.to_part_uid = b.part_uid order by 1, 2, 3, 4; The second inner query returns the related requests:
Reports Guide
197
Chapter 4 The Published Views select product_id, ch_doc_type, doc_seq, ch_doc_id, status, title from pcms_chdoc_related_chdoc a, pcms_chdoc_data b where a.from_ch_uid = :outer_ch_uid and a.to_ch_uid = b.ch_uid and seq = 1 order by 1, 2, 3;
Hierarchical Queries
Reports of the "family tree" type require the use of the CONNECT BY construct of the SQL language. Queries incorporating this construct are known as hierarchical queries, and (for technical reasons) can only be done using certain views. These views are identified in their preambles in this document. This kind of report is often suited to the use of nested queries. However, an example of a hierarchical report performed by a single query is to list all the design parts related by breakdown to a given design part and its descendants. Each line of the report gives the parent and child design parts for one relationship in the tree. The query is: select substr (p.product_id, 1, 10), substr (p.part_id, 1, 25), substr (p.variant, 1, 4), substr (p.pcs, 1, 3), substr (c.product_id, 1, 10), substr (c.part_id, 1, 25), substr (c.variant, 1, 4), substr (c.pcs, 1, 3) from pcms_part_data p, pcms_part_data c where (p.part_uid, c.part_uid) in (select parent_part_uid, child_part_uid from pcms_parts_structure where type_of_rel = 1 connect by parent_part_uid = prior child_part_uid start with parent_part_uid in (select part_uid from pcms_part_data where product_id = 'PAYPHONE' and part_id = 'RINGER' and variant = 'AAAA' and pcs = '1')); The SUBSTR function is used to limit the displayed length of the various fields. The database allows much longer data in some of these columns, and users should have regard both to the lengths of their data, and to report formatting considerations.
198
Index
A
ASCII reports 16 Dimensions Reports introduction 14 documentation set 10
B
build area, see deployment area build stage, see deployment stage
E
examples of views 196 export (report) file 16
C
change document reports catalog report 23 pending report 23 selection criteria 22 category 23 optional 23 product-id 23 report type 23 types 24 ACTION_HISTORY 24, 25 BASELINE_DETAIL 24, 26 CH_DOC_LIST 24, 25 CHDOC_PART_ITEM 24, 25 DEPENDENCY_REP 24, 25 FULL_HISTORY 24, 25 PARM_11_12 24, 25 PARM_12_11 24, 26 PART_CHDOC_ITEM_R 24, 25 PART_CHDOC_ITEM_S 24, 25 USER_CHDOC 24, 25 change document, see request command-line reports 16 command-line, ASCII format reports 14 CONNECT BY construct hierarchical queries 198 contacting technical support 11 conventions, typographical 9 Crystal Reports 14
F
family tree report CONNECT BY construct 198
H
hierarchical queries CONNECT BY construct 198
I
inbox 10 installing published views 42
O
online help for the command-line interface 9
P
pending list, see inbox printing manuals 11 product name changes 9 product structure report 16 based on current product structure 17 based on export file 17 based on product structure secured by baseline 17 project 10 project working location 10 published views
D
defining published views 42 deployment stage 10 Dimensions CM documentation set 10
Reports Guide
199
Index attribute mapping 47, 53, 56, 79, 118, 136, 142, 183 baseline attribute information 55, 180 baseline changes made by CRB 65 baseline information 57 baseline templates 66, 67 baseline update history 56 baseline update history with attributes 79 baselines and their attributes 48, 55 basic change document information 100 branches replicated 147 change document action description 82 change document and related baselines 92 change document current action description 97 change document delegations 87 change document detailed description 88 change document history 89 change document history with attributes 90 change document type information 98 change document user lists 99 change documents and related baseline 64 change documents and related items 94 change documents and their attributes 49 change documents for transfer 157 change documents on normal lifecycle 178 change documents received 153 command statistics 102 current change document information 85 current change document information for reports 160 current item information 113 customer information 103 defining 42 design part and attribute update history 136 design part attribute information 132 design part history with attributes 135 design part information 134 design part type information 137 design part update history 135 details on archives that have been created 44 Dimensions lifecycles 126 Dimensions Make commands used to make an item 179 environment items definitions 107 historic change document attribute information 83, 84, 169 historic design part attribute information 133 historic product item attribute information 112 historic secondary change document attribute information 170 history of item revisions 123 history of items 117 installing 42 inward transfers received 152 Serena Dimensions CM 10.1.1 item delegations 115 Item Processor Definitions registered against a product 110 item releases 145 item revisions received 154 item update history with attributes 118 items and their attributes 50 items and their file details contained in a baseline 59 items and their related design parts 122 items checked out by users 116 items for transfer 158 items in a baseline 60 items in worksets 193 items that are contained in an archive 45 made-of list 131 made-of list for items resulting from Dimensions Make 130 network nodes used in the Dimensions Make process 127, 128, 129 normal lifecycle for change documents 91 normal lifecycle for product items 119 one-to-one derived build relationship 106 outward transfers 156 parts and their attributes 51 parts in a baseline 63 pedigree of revised and merged baselines 62 product attribute information 141 product attribute update history 142 product item attribute information 111 product item type information 124 products and their attributes 52, 141 registered base database sites 177 registered branch names 81 registered Dimensions users 187 registered replication configurations 147, 149, 156 related change document information 93 release information 144 release templates 146 releases forwarded to customers 104, 105, 190 role sections 162 roles allocated to users 186 secondary change document action description 168 secondary change document current action description 176 secondary change document detailed description 172 secondary change document history 173 secondary change document history with attributes 174 secondary change document information 171 secondary change documents on normal lifecycle 175
200
Index structural relationships between design parts 138, 139, 140 subordinate definitions in a master definition 151 text logs associated with outward transfers 159 text logs received 155 user and pending change document information 185 user and pending change documents and related design parts 95 user attribute update history 183 user audit trail 184 user defined attributes 181 user-defined attributes for user. 53 user-defined relations between items 121 users and their attributes 180 users and their items to be actioned 120 valid sets 188 workset history 191 workset information 96, 192, 195 USER_CHDOC 24, 25 report current items 17, 20 report current items report 17 report current parts 17, 20 report current parts report 17, 22 report design structure 17, 20, 22 report design structure report 17 select design structure 17 user-defined 30 reports Crystal Reports desktop 14 user-defined command script product-range parameter 31 request 10 RPT 22 running user-defined reports 38
S
select design structure reports 17 SQL statements for various reports 196 standard Dimensions reports supplemented with specially written reports 42 standard report typical users 14
R
RCI 17, 20 RCP 17, 20, 22 RD 17 RDS 17, 20, 22 report export file 16 pre-processor 16 product structure 16 product structure report based on current product structure 17 based on export file 17 based on product structure secured by baseline 17 report change documents ACTION_HISTORY 24, 25 BASELINE_DETAIL 24, 26 catalog report 23 category 23 CH_DOC_LIST 24, 25 CHDOC_PART_ITEM 24, 25 DEPENDENCY_REP 24, 25 FULL_HISTORY 24, 25 optional criteria 23 PARM_11_12 24, 25 PARM_12_11 24, 26 PART_CHDOC_ITEM_R 24, 25 PART_CHDOC_ITEM_S 24, 25 pending report 23 product-id 23 report type 23, 24 selection criteria 22
T
technical support contacting 11 terminology changes build area 10 build stage 10 change document 10 custom list 10 deployment area 10 deployment stage 10 in box 10 library cache area 10 list of 10 pending list 10 privilege 10 project 10 project working location 10 request 10 request list 10 user interface profile 10 user list 10 work area 10 workset 10 workset root directory 10
Reports Guide
201
U
unique identifier (UID) 42 user list, see custom list and request list user report definitions about 30 adding report file to 36 assigning report files to 36 creating 34 editing 35 roles 31 user report files about 30 adding 36 assigning 36 exporting 37 importing 37 unassigning 36 user-defined reports command script product-range parameter 31 user-defined reports, running 38 users of reports 14
W
workset root directory, see project working location workset, see project
202