Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Securing an attachment field

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

Assign an attachment category to an attachment field to control which actions a user can take on an attachment.

The actions a user can take are determined by the attachment category configuration. By default, attachments are associated with an attachment category with the same name as your attachment field.
  1. Access the field, based on the way that it is defined in your data model.
    • To view fields in a data object:
      1. In App Studio, click the Open runtime toolbar icon.
      2. Click Turn editing on.
      3. In the navigation panel, click Data to display the Integration Designer
      4. Click the name of a data object.
      5. Click the Data model tab.
    • To view fields in a case type:
      1. In App Studio, click the Open runtime toolbar icon.
      2. Click Turn editing on.
      3. In the navigation panel, click Cases to display the Case Type Explorer.
      4. Click the name of a case type.
      5. Click the Data model tab.
      6. Optional: To display fields that are inherited by your application, click Show reusable fields.
    • To view fields on a form:
      1. In App Studio, click the Open runtime toolbar icon.
      2. Click Turn editing on.
      3. In the navigation panel, click Cases to display the Case Type Explorer.
      4. Click the name of case type.
      5. On the Views tab, click the name of a form.
  2. Click the Configure field icon in the row of the attachment field.
  3. Press the Down Arrow key in the autocomplete field that is displayed and select the name of an attachment category. Alternatively, you can enter a unique name to create a new attachment category.
  4. Click Submit.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us