Skip to main content

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

Configuring a data model for a case

Updated on May 11, 2022
Applicable to Cosmos React applications

Configure a data model to define the data that you want to use in a case. For example, to include a user email address in a case, add an email address field to the data model.

Before you begin:
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. On the Data model tab, click Add field.
    Note: You can also add new scalar fields to the data model from a view in the User Interface tab.
  3. In the field configuration dialog box, in the Field name field, enter a descriptive name.
    For example: Enter Email address.
  4. In the Type list, select a field type.
  5. If more configuration options are available for the field type that you select, perform the following actions for a field:
    Add a text paragraph to the form
    1. In the Type list, select Text (paragraph).
    2. Click the Configure paragraph icon.
    3. In the Display as list, define whether to display the paragraph as plain or rich text.
      Result: The following figure shows a rich text paragraph at run time that users can use to describe symptoms while booking a doctor's appointment in an application:
      Rich text paragraph
      Text paragraph field with a rich text editor.
    Add a picklist to the form
    1. In the Type list, select picklist.
    2. In the Display as list, define a display mode for the picklist.
    3. In the Picklist options list, define choices for the picklist.
      You can create your own choices or source them from a data page.
    4. If you add your own choices, click Add choice, and then provide an option for users to select.
    5. If you use a data page to provide choices, select the data page that you want to use.
      Result: The following figure shows a picklist with radio buttons at run time that users can use to select an office location:
      A field of a picklist type at run time.
    Add an attachment field to the form
    1. In the Type list, select Attachment.
    2. In the Attachment category list, select the category.
      Result: The following figure shows an attachment field at run time that users can use to add documents to a case:
      Attachment field
      Attachment field at run time.
    Add a user reference to the form
    1. In the Type list, select User reference.
    2. In the Display as list, define whether users can search for a user ID by using a search box or a drop-down list.
      Result: The following figure shows a user reference field at run time configured as a search box that users can use to select a doctor while booking an appointment in an application:
      User reference field
      User reference field at run time.
    Add a field to capture dataFor more information about adding a field to capture data, see Creating fields for capturing data.
  6. Click Save.
What to do next: Configure a view for your case type that includes the fields from the case type data model. For more information, see Views for cases.
  • Referencing a case type

    Build transparent and automatic relationships between case types by creating case references. When you reference a case type, you can pass data about one case type to another case type, and you can clearly view connections between case types and their instances at run time. You also save time and take advantage of low-code tools because you can view relations between case types without creating complex report definitions.

  • Creating fields for capturing data

    To decrease application development time and costs, reuse data objects across your application by creating fields that capture data. You can reference data between fields in several ways that help you to efficiently reuse resources without detailed knowledge about how the system stores data.

  • Configuring primary fields

    Define primary fields to automatically add the most relevant fields to your cases and reduce the amount of UI configuration that is necessary.

  • Embedding data in a case

    Manage your resources more efficiently by embedding data and connecting information directly to a case. Consequently, you avoid sourcing data from any other object. Embedding relevant data directly in a case if the case is the only object that uses this piece of information helps you to organize data in your application in a more transparent way.

  • Referencing a data page

    Provide data for your case types from integrations in your application by querying a data page. When you source data for your case directly from a data page, you reuse your resources in a transparent and prescriptive way.

  • Validating case data

    Help users enter data values in a valid format by preventing processing errors when the users create or save a case. To save time, add validation on a case-wide level instead of validating recurring fields on each individual assignment.

  • Calculating values with decision tables

    To deliver an application that automatically at run time provides the most appropriate solutions, create logic with decision tables. Decision tables test a group of properties to match specified conditions and ultimately improve the flexibility of your application. By creating decision tables by using the low-code App Studio environment, you deliver software that can respond dynamically to varied conditions in business processes.

  • Authoring decision tables in App Studio

    Respond to dynamically changing business situations by calculating values in your business processes automatically. With decision tables, you can define conditions that include multiple elements and result in different outcomes. Consequently, you deliver an application that helps users successfully resolve business processes in various and dynamic scenarios.

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