More about Attachment Category rules

Default attachment categories

Each of the five standard attachment types is supported by its respective default attachment category (Rule-Obj-AttachmentCategory rule type in Work- class). In the absence of a custom category, the default is assigned to the appropriate type. For example, the ScanDocument type is supported by a standard category named ScannedDocument. The default allows unrestricted security access to the attachment. The default's name is used as header text in attachment lists and other reports. You create custom instances in your work classes to give the categories meaningful names and define access privileges for specified attachment types.

Default when rules

Standard when rules exist that enable you to qualify without further configuration an attachment category rule for all operators or managers in your application at the organization, division, or organization unit levels. You select the appropriate when rule for either the work object (Work- class) on the WorkPage or for the attachment (Data-WorkAttach- class) on the AttachmentList page. For example, if the attachment rule is qualified with the when rule called AnybodyInTheWorkObjectOrgUnit, the category rule will evaluate to true if the operator's organization unit is on the work page.

Upgrading attachment categories created in V5.1 - V5.4

Attachment categories created (using the Attachment Wizard) in V5.4 or earlier could only be used with file attachment types. Security was limited to create and edit operations based on privileges. When upgrading an application to V5.5, you may choose to replace existing category definitions with attachment category rules. Doing so lets you take advantage of the rule's extensive security features for all attachment types.

To upgrade, create a new attachment category rule and enter the existing category name in the Category Name field on the new rule dialog. The new rule and its settings override the existing category.

Warnings display when the rule is saved stating that an "old attachment category exists", and "an unexpected privilege exists." The new rule will validate and function without error.

To eliminate the"old category" warning, delete the attachment name in field value .pyAttachmentCategory. To eliminate the" unexpected privileges" warning, delete the Create_<attachment category name>and Edit_<attachment category name> rules. Alternatively, select the Create and Edit options on the rule form so that they correspond to the original configuration. If you think you might revert to the original category definition, do not delete the rules.

The privileges Work-.DeleteAnyAttachment. and Work-.DeleteOnlyOwnAttachment are available if needed. They can be used to override any attachment's Delete Own and Delete Any rule settings. For an example, see the Pega Developer Network article PRKB-24074 How to enable users to delete attachments.

Neither these privileges nor attachment category rules allow anyone to delete correspondence items, a special form of file attachment. The system retains correspondence as a permanent record of information that was conveyed to an outside party or system.

	attachment category, attachment type
	Understanding work object attachments How to use attachment categories
	Atlas — Standard Attachment Category rules

About Attachment Category rules