Skip to main content


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

Configuring attachment exists assertions

Updated on December 13, 2021

For flows and case types, you can verify that the flow or case type has an attachment of type file or note (attached using the Attach Content shape) or email (attached using the Send Email shape) attached.

Before you begin: Open the unit test case. For more information, see Opening a unit test case.
  1. On the bottom of the Definition tab, click Add expected result.
  2. From the Assertion type list, select Attachment exists.
  3. From the Attachment type list, select one of the following options, and then provide the value for each field:
    • File: Select to specify that the attachment type is file, and then enter the following values:
      • Description: Enter the text that was provided as the description in the Attach Content shape.

      • Name: Enter the name of the file that was provided in the Attach Content shape.

    • Note: Select to specify that the attachment type is note, and then enter text that was entered as the note description in the Attach Content shape.
    • Email: Select to specify that the attachment type is an email, and then enter the email subject that was provided in the Send Email shape.
  4. Repeat steps 1 through 3 to add additional attachment assertions.
  5. Optional: To add a comment, click the Add comment icon, enter a comment, and click OK.
  6. Click Save.
  • Attachment exists assertions

    On case types and flows, you can test whether an attachment of type file or note, which were attached in the Attach Content shape, or email, which was attached using the Send Email shape, exists.

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