Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Defining purpose of a case type by creating specifications

Updated on November 22, 2021

Engage with your stakeholders and communicate goals that you want your case type to achieve by creating specifications. Specifications represent actions that users can perform by using your application so that all parties involved in the development process have a common understanding of the purpose of your application.

For example, for a Hiring a job candidate case type, you can create specifications that describe the following actions:
  • HR worker can collect personal information from the candidate
  • Job candidate can upload documents
  • Hiring manager can accept the candidate
Before you begin: Create specifications that you want to associate with your case type. For more information, see Creating a specification.
Associating specifications with case types is suitable for advanced developers. To describe the purpose of your application in a low-code and more user-friendly way, create features. For more information, see Tracking feature-driven development.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Process category, and then click Case Type.
  3. In the list of case type instances, open the case type that you want to edit.
  4. On the Specifications tab, click Click to associate specifications.
  5. In the Name column, press the Down arrow key, and then select a specification that you want to associate with the case type.
  6. Optional: To add more specifications, repeat steps 4 through 5.
  7. Click Save.

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