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.

Creating a contextual case

Updated on November 22, 2021

You can use the Create case shape to create a case in the context of your current case. By defining relationships, you can share data among cases in your application.

  1. Add the Create Case shape to the life cycle of your case.
    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 Workflow tab, click Life cycle.
    3. Hover over a process in a stage, and then click + Step MoreAutomations Create Case.
    4. Click Select.
  2. Choose an option from the Create the following case list.
    • [Case type] - creates an instance of the case type that you select.

    • Create new Case type - creates an instance of a new case type, based on the value that you provide in the Case type name field.

      By default, instances of new case types are children of the current case.

  3. To create more than one case, provide a list.
    1. Select the Create multiple cases using a list check box.
    2. In the List field field, press the Down Arrow key, and then select a field group, which is a property of type Page List.
  4. Propagate data from the current case to the new case.
    1. Select the Transfer information to new case check box.
    2. In the Transfer information dialog box, select the check box next to a field to copy its value from the current case to the new case.
    3. Optional: To change which field stores the value in the new case, enter a field name in the To field field.
    4. Click OK.
  5. Enter the audit note.
  6. 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