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.

Configuring case resolution

Updated on November 22, 2021

Configure a resolution method in a stage to control the final status and processing that occurs when a case reaches the end of its life cycle.

  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 if Optional actions is selected.
  3. Decide which stage resolves the case, which is typically the last primary stage in the life cycle or an alternate stage.
  4. Click the stage.
  5. On the General tab of the property panel, click Resolve the case.
  6. Optional: Change the default final status for resolved cases, by using one of the following techniques.
    • To use an existing status, press the Down Arrow key in the Resolution status field, and then select a status value.
    • To create a new status, enter a unique name in the Resolution status field by using the format Resolved-[your status name].
  7. Optional: Clean up dependencies when the current case is resolved.
    1. Select the Resolve open child cases check box.
    2. In the Resolution status of child cases field, enter a final status for child cases by repeating step 7.
  8. Click Save.
Result: When all steps in the stage are completed, the case and its open child cases change status to the values that you provide. If you do not provide status values, the current case is set to Resolved-Completed and open child cases are set to Resolved-Unspecified.

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