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.

Skipping forms to collect information before case processing

Updated on November 22, 2021

Speed up case creation and provide flexibility for your cases by skipping the Create dynamic view. When you need to capture user input as a part of case processing, you can skip the Create dynamic view. In that scenario, the case enters the first stage immediately, while users provide information during case processing. Then you can create the form to collect information from users to precisely meet your specific needs.

The Create dynamic view displays all fields that your application associates with the case data model. The application starts processing a case after users, such as customers, complete the fields in the Create dynamic view. When you need to display the fields in two columns, or when the data model contains fields that only customer service representatives use, you can customize the Create dynamic view.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.
  2. In the case working area, click the Settings tab.
  3. In the settings properties panel, click General.
  4. In the Behavior section, select the Skip 'Create' view when users create a new case check box.
  5. Click Save.
Result:

The next time that you create a case type instance, the case skips the Create form and moves directly to the first stage in the case life cycle.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us