Skip to main content

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

Setting required attachments for stage entry

Updated on March 29, 2022

Maximize efficiency and speed up the case resolution process by verifying that the user provides required, relevant documentation and correspondence before a case enters the next stage.

For example, in a case for a car insurance claim, you can verify that the policyholder attaches photographs of their damaged car before the case enters the stage in which the insurance company validates the policyholder's claim.

Before you begin: Add attachment categories that reflect your business needs to your case type and ensure that you select the Required for resolution checkbox in step 5 in Categorizing case attachments.
Note: You cannot define entrance criteria for the Create stage. For more information, see The Create stage.
  1. In the navigation pane of Dev Studio, click Case types, and then click the case type that you want to open.
  2. On the Workflow tab, click a stage name.
  3. In the Stage property pane, click Validation.
  4. In the Attachments required for stage entry section, click Add required attachment to display the list of attachment categories that your case type supports.
  5. Select an attachment category from the list.
    For example: The following figure shows a design-time configuration of a stage with a required attachment. Users that process a case have to provide an attachment of the selected category to submit the case.
    Setting a required attachment for stage entry
    Stage property pane with a required attachment of the File type selected for stage entry.
  6. Click Save.
Result: At run time, users need to provide at least one attachment in each of the required attachment categories, otherwise the application displays an error.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us