Working with the PegaRULES database Link tables

This topic describes PegaRULES database tables with names that start with one of these values:

pc_link

pr_link

The following tables can hold instances of concrete classes derived from the Link-base class:

Table	Description
pr_link_attachment	Supports the association of a work item attachment with a work item, as instances of the Link-Attachment class. Contains one row for each attachment.
pc_link_folder	Supports the association of a work item with a folder, as instances of the Link-Folder class. This can be a many-to-many relation.
pr_link_work_tag	Supports the association of a tag with a work item. Corresponds to the Link-Tag class. See Understanding tagging.
pc_link_topcase	Supports the Link-TopCase class, which links a subcase to the top case that it is associated with. Used to retrieve the top case of a subcase or to get a list of covered subcases.
pr_link_usecase	Supports the association of an Application Specification rule with an activity, flow, or other rules that provide the implementation of that specification. Also supports the association of an Application Requirement rule with an application rule. Corresponds to the Link-Requirement and Link-UseCase classes. See About Application Specifications and About Application Requirements.
pr_link_pmf_rulechanges	Supports the Link-Project class to display and report on rule changes associated with project items via the View Rule Changes link on the Project Worklist.
pr_link	Not used by any standard class. Default table for instances of other Link- classes.

	attachment, folder, Link- base class, subcase, top case, specification
	Atlas — Initial Database Table data instances Atlas — Standard classes derived from the Link- base class

Working with the PegaRULES database