Share this page

# Reference Relationships

For some references, you can create a functional dependency between the package and the referenced entity. For example, you can specify that a request is a predecessor to the package. This means the package cannot continue until the request is closed.

- Predecessor Relationships. Predecessor relationships dictate that action is not allowed on one entity until the referenced entity closes. For example, a package cannot complete any workflow action until the referenced task is closed (Completed, Bypassed, or Cancelled). The package status is Pending Task. After the task closes, the package can be acted upon after more. This does not stop other request fields from being edited.

- Successor Relationships. Successor relationships dictate that action is not allowed on the referenced entity until the entity closes. For example, a referenced task cannot change status until the original package is closed. The task status is Pending Request. When the package closes, the task can again be changed. This does not prevent other task fields from being edited.

Table 2-1 lists the references, their definitions, and possible dependency relationships.

Table 2-1. References and relationships
Reference | Reference Description | Possible Relationships | Relationship Description
--- | --- | --- | ---
Attachment | Attach a file from a local machine to the current package. The attached file is copied to the server. | Standard attachment interaction | (Informational) The attachment is related to this package.
Packages (Existing) | Reference an existing package. | Duplicate package | (Informational) The referenced package is a duplicate of the package.
Run before this package in a release | (Informational) In a release, the selected package must be run before this package.
Run after this package in a release | (Informational) In a release, the selected package must be run after this package.
Predecessor | (Blocking) Action is not allowed on the package until the referenced package closes.
Successor | (Blocking) Action is not allowed on the referenced package until the package closes.
Packages (New) | New packages can also be created from a package. 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 packages. | Run before this package in a release | (Informational) In a release, the selected package must be run before this package.
Run after this package in a release | (Informational) In a release, the selected package must be run after this package.
Predecessor | (Blocking) Action is not allowed on the package until the referenced package closes.
Successor | (Blocking) Action is not allowed on the referenced package until the package closes.
Programs | Reference a program in Program Management. | Related to This program | (Informational) Selected program is related to this package.
Projects | Reference a project in Project Management. | Related to This package | (Informational) Selected project is related to this package.
Releases | Reference a release in Deployment Management. | Contains this package | (Informational) The package is contained in the selected release.
Request (Existing) | Reference an existing request. | Parent of this package | (Informational) The referenced request is the parent of the package.
Related to this package | (Informational) Referenced request is related to this package.
Predecessor | (Blocking) Action not allowed on this package until the referenced request closes.
Successor | (Blocking) Action not allowed on the referenced request until this package closes.
Requests (New) | New packages can be created from existing packages. Also, if configured as part of the workflow, you can spawn a package from a package. When this happens, a reference to that package is automatically generated, establishing a two-way link between the packages. | Parent of this package | (Informational) The referenced request is the parent of the package.
Related to this package | (Informational) Referenced request is related to this package.
Predecessor | (Blocking) Action not allowed on this package until the referenced request closes.
Successor | (Blocking) Action not allowed on the referenced request until this package closes.
Tasks | Reference a task in Project Management. | Related to this package | (Informational) The referenced task is related to this package.
URL | Reference a Web address. Documents at the URL must be in MIME format. | Standard URL interaction | (Informational) The URL is related to this package.

## Predecessor Relationships

Predecessor relationships dictate that action cannot be performed on one entity until the referenced entity closes. For example, a package cannot complete any workflow action until the referenced task is closed (Completed, Bypassed, or Cancelled). The package status is Pending Task. After the referenced task closes, the package can be acted on again. This does not prevent the editing of other request fields.

## Successor Relationships

Successor relationships dictate that action is not allowed on a referenced entity until the entity closes. For example, a referenced task cannot change its status until the original package is closed. The task status is Pending Request. After the package closes, the task can be acted on. This does not stop other task fields from being edited.

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: