Skip to main content


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

Technical considerations for the Create stage in existing case types

Updated on March 29, 2022

To ensure that your application works correctly after you add the Create stage to your existing case types, consider the actions that you need to take in different technical scenarios.

The Create stage in existing case types

To understand how the Create stage can impact your existing case types, consider the following scenarios:

  • If you configured your existing case type to skip the Create view when users create a case, Case Designer marks the first stage in your case type as the Create stage by adding a green bar to the stage header.
  • If you configured your existing case types to display the Create view, Case Designer adds the Create stage as the first stage in your case type.
  • Your case types are independent of the pyStartCase or any other starting process. As a result, any security settings or other configurations that you define on the starting process rule are inapplicable to the case type.
  • If you configured your case type to create temporary cases, the option is not applicable after adding the Create stage. All the case types that include the Create stage create persistent cases.
  • When you configure the Create stage in a case type, the system immediately creates a case every time you enter the Create stage. If you do not want to include cases that are in the Create stage or have the Resolved-Canceled status in your dashboards or reports, update the relevant report definitions to filter out such cases.

To decide which scenario applies to your needs, consider the configuration of the starting process in your application:

The case type rule has only pyStartCase configured as a starting process without modifications

Consider the following circumstances:

  • You need to configure the view for the Create step in the newly added Create stage.
  • The only data transform that works upon creation of a case with the Create stage is pyDefault. If you configured another data transform to work upon a case creation in your existing case type, Pega Platform automatically changes the data transform to pyDefault. To apply your custom configurations, call your data transform from the pyDefault data transform or configure a process in the Create stage to transform data.
  • If you configured any validations on case creation, you need to reconfigure the validations to apply to the next stage after the Create stage.

The case type rule has only pyStartCase configured as a starting process with modifications or the case type rule has many starting processes configured

Consider the following circumstances:

  • You need to configure the view for the Create step in the newly added Create stage.
  • You need to move any pre-processing or post-processing logic from the pyStartCase starting process to the Create stage.
  • The only data transform that works upon creation of a case with the Create stage is pyDefault. If you configured another data transform to work upon case creation in your existing case type, Pega Platform automatically changes the data transform to pyDefault. To apply your custom configurations, call your data transform from the pyDefault data transform or configure a process in the Create stage to transform data. For more information, see Data transforms.
  • If you configured any validations on case creation, you need to reconfigure the validations to apply to the next stage after the Create stage.

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