Table of Contents

Configuring attachment exists assertions


Only available versions of this content are shown in the dropdown

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.

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.

  • Defining expected test results with assertions

    Use unit test cases to compare the expected output of a rule to the actual results returned by running the rule. To define the expected output, you configure assertions (test conditions) on the test cases that the test, when run, compares to the results returned by the rule.

  • Converting unit tests to test cases
  • Creating unit test cases for rules

    For most rules, you can create a reusable test case by converting a unit test to a test case, configuring case details, and then defining expected test results with assertions (test conditions). When the test case runs, the test results are compared to the expected results defined for the rule’s assertions. If the test results do not meet the defined assertions, then the test fails.

  • Attaching content to a case

    You can use the Attach Content shape to control the kind of information that is added to a case. By attaching relevant correspondence and documentation, you can centralize the supporting information for a case.

  • Sending automatic emails from cases

    By using email, you can share information about a case with stakeholders and case participants. Add the Send Email shape to your business process, to control the number of recipients and the message format. For example, you can inform stakeholders about the approval of a job candidate in a hiring process.

Suggest Edit

Have a question? Get answers now.

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