si viewcpentries
displays the net effect of a set of change packages, or the net effect of all of the change packages on a selection of items.
Synopsis
si viewcpentries [--fields=field1[:width1],field2[:width2]...] [--format=value] [--height=value] [--width=value] [-x value] [-y value] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)] [--hostname=server] [--password=password] [--[no]persist] [--port=number] [--quiet] [--settingsUI=[gui|default]] [--status=[none|gui|default]] [--user=name]
Description
si viewcpentries displays a list of the change operations that occurred on a set of change packages or on all change packages for a selection of items, if those operations were tracked in change packages or related to change packages. The displayed information can be used to identify changes related to a certain feature, report on the changes that went into a release or component, or as part of investigating defects that may have resulted from those change operations.
The following is an example of using the command to return a list of all affected members and subprojects in a selection of change packages and items:
si viewcpentries 1 2 3 2:1 3:4 5
The following are key considerations when using this command:
• This command accepts a selection of either change package IDs or Windchill RV&S Item IDs or both.
• This command returns changes that were recorded in selected change packages or all change packages for a selection of items.
• Operations that do not reside on the server, including deferred entries, are not represented in the command output. Also, operations that are not recorded in change packages, such as a restore project (or commands that used the bypass value for --changePackageId), are not represented in the command output.
• Modifications to member attributes are not included in the command output.
• If subprojects were added using a change package, only that operation is included in the command output. The members that were added with the subproject are not included in the command output because they were not recorded in the change package. Similarly, reconfigured subprojects appear in the command output, but modifications to the members of the subproject do not appear in the command output.
• When propagations cause an update to a revision number, the intervening revisions are not included in the command output because the operation that created them is not in the change package for that time frame.
Options
This command takes the universal options available to all
si commands, as well as some general options. See the
options reference page for descriptions.
• --fields=field1[:width1],field2[:width2]...
• allows you to select fields to be printed, specified in the format field1[:width1],field2[:width2]....
Specifying the column [:width] (in pixels) for each field is optional. Fields are separated with a space.
The fields available for printing can be one or more of the following:
• bytesadded
displays the number of bytes added by the operation. For text files, this field displays 0.
• bytesdeleted
displays the number of bytes deleted by the operation. For text files, this field displays 0.
• configpath
displays the configuration path of the change package entry.
• id
displays the change package ID.
• istext
indicates if the change package entry has a text archive; true or false. If false, the entry is a binary archive.
• linesadded
displays the number of lines added by the operation. For binary files, this field displays 0.
• linesdeleted
displays the number of lines deleted by the operation. For binary files, this field displays 0.
• location
displays the archive location for members or the location of the parent project for subprojects (the canonical path).
• member
displays the name of the member or subproject affected by the operation.
• membertype
displays the type of project element affected by the operation (member or subproject).
• project
displays the name and path of the project where the operation was performed. If the operation occurred in a shared subproject, the subproject name and path are displayed. If the operation involved two different projects (for example, moving a member from one project to another), the command returns two entries, with the first entry the originating project and the second entry the destination project.
• revision
displays the member revision number.
• server
displays the server the change package resides on.
• summary
displays the change package summary.
• timestamp
displays the timestamp of the selected change package.
• type
displays how the member was added to the change package.
• user
displays the ID of the user who added the member to the change package.
• variant
displays the names of variant projects associated with the member.
• --format=value
defines an output format for user-formatted text. The default formatting is suitable for interpretation by most users; the various formatting options are provided for programmatic control.
This option and the --fields option are mutually exclusive.
--format options use the same values as --fields, but similar to a JAVA MessageFormat string (that is, it requires { } to surround each field). The --fields option automatically adds a newline on the end, but you must supply the newline for formats with a \n, for example: si viewcpentries --format="{project},{member},{revision}\n"
Diagnostics
See the
diagnostics reference page for possible exit status values.
See Also