Share this page
Request detail page, References section
This section describes the details of the References section of a request detail page.
Overview
The References section of the request detail page contains additional information related to the request. For example, you can add a URL to a request or delete an outdated document from a request. The References section is included in the request creation process and remains through to request resolution. References can be added or deleted from the request.
Use the Reference Additions subsection to add references to the request. Saved references are organized based on reference type. For example, all saved reference packages are saved in the Packages section.
In some cases, you can create a functional dependency between a request and the referenced entity. For example, you can specify that a package is a predecessor to the request. This means the request cannot continue to the next workflow step until the package is closed. For a list of the references, their definitions, and possible dependency relationships, see References and relationships.
References and relationships
The following table lists the references, their definitions, and possible dependency relationships.
|
Reference |
Reference Description |
Possible Relationships |
Relationship Description |
|---|---|---|---|
|
Attachment |
Attach a file from a local machine to the current request. The attached file is copied to the server. |
Standard attachment interaction |
(Informational) The attachment is related to this request. |
|
Packages (Existing) |
Reference an existing package. |
Child of this request |
(Informational) The selected package is the child of the request. |
|
Related to this request |
(Informational) The selected package is related to the request. |
||
|
Predecessor |
(Blocking) Action is not allowed on the request until the referenced package closes. |
||
|
Successor |
(Blocking) Action is not allowed on the referenced package until the request closes. |
||
|
Packages (New) |
New packages can also be created from a request. If configured as part of the workflow, you can spawn a package from a workflow step. When this happens, a reference to that package is automatically generated, establishing a two-way link between the request and package. |
Child of this request |
(Informational) The selected package is the child of the request. |
|
Related to this request |
(Informational) The selected package is related to the request. |
||
|
Predecessor |
(Blocking) Action is not allowed on the request until the referenced package closes. |
||
|
Successor |
(Blocking) Action is not allowed on the referenced package until the request closes. |
||
|
Projects |
Reference a project in Project Management. |
Related to this request |
(Informational) Selected project is related to this request. |
|
Releases |
Reference a release in Deployment Management. |
Contains this package |
(Informational) The request is contained in the selected release. |
|
Requests (Existing) |
Reference an existing request. |
Duplicate request |
(Informational) The referenced request is a duplicate of the request. |
|
Original duplicate requests |
(Informational) The referenced request is the original of the two duplicate requests. |
||
|
Parent of this request |
(Informational) The referenced request is the parent of the request. |
||
|
Child of this request |
(Informational) The referenced request is the child of the request. |
||
|
Related to this request |
(Informational) Referenced request is related to this request. |
||
|
Predecessor |
(Blocking) Action not allowed on this request until the referenced request closes. |
||
|
Successor |
(Blocking) Action not allowed on the referenced request until this request closes. |
||
|
Requests (New) |
You can create new requests from an existing request. Also, if configured as part of the workflow, you can spawn a request from a request. A reference to that request is automatically generated, establishing a two-way link between the requests. |
Duplicate request |
(Informational) The referenced request is a duplicate of the request. |
|
Original duplicate requests |
(Informational) The referenced request is the original of the two duplicate requests. |
||
|
Parent of this request |
(Informational) The referenced request is the parent of the request. |
||
|
Child of this request |
(Informational) The referenced request is the child of the request. |
||
|
Related to this request |
(Informational) Referenced request is related to this request. |
||
|
Predecessor |
(Blocking) Action not allowed on this request until the referenced request closes. |
||
|
Successor |
(Blocking) Action not allowed on the referenced request until this request closes. |
||
|
Tasks |
Reference a task in Project Management. |
Related to this request |
(Informational) The referenced task is related to this request. |
|
URL |
Reference a Web address. Documents at the URL must be in MIME format. |
Standard URL interaction |
(Informational) The URL is related to this request. |
Predecessor relationships dictate that an action cannot be performed on one entity until the referenced entity closes. For example, an action is not allowed on a request until the referenced package closes. After the package closes, users can again act on the request. (This does not prevent users from editing other request fields.)
Successor relationships dictate that action is not allowed on a referenced entity until the entity closes. For example, users cannot perform an action on a referenced package until the request closes. The package status is Pending Request. After the request closes, users can act on the package again. This does not prevent users from modifying other task fields.
Finish/Finish Predecessor Relationships
Finish/Finish, or FF, predecessor relationships dictate that the two entities complete at the same time. For example, a referenced package cannot have a status of Complete until the original request is closed. After the resource working on the original request is finished, and the status is set to Completed (% Complete is set to 100%), the referenced package acquires Completed (Pending Request) status.After the request is closed, the referenced package is set to Completed. (This does not prevent users from editing other request fields.)
Search and download references
You can search for a reference by text strings contained in the target reference subsection:
-
Locate the target reference subsection and click the Search icon at the top right.
Note: If you are in the Program Details page: References tab or the Package Details page, you can find the Search icon at the top right of the References section. You can use this Search box to search for references of all types.
-
Type a text string in the Search box. The reference that has the text string contained in the subsection will filter itself out.
You can download the attachment reference of a request:
-
To download a single attachment, click the name of the attachment you want to download. The attachment is downloaded automatically.
-
To download all the attachments of a request, click Download All. All of the attachments added to the request are downloaded as a Zip file.
