Creating custom case type templates
After you add a new case type, you can quickly create additional case types with similar features by copying the case type and saving it as a template. When adding more new case types, select the new template.
Pega Customer Service
Implementation Guide
Only configure a case type to be a template if it has the following attributes:
- The case type must be in the PegaCA-Work-Service class, or in a work pool class that inherits from it.
- The case type must use stages and it must be configurable in App Studio. This ensures that case types created from it are also editable in App Studio.
- The case type's decision-based steps must be built in App Studio.
- If the case type contains reusable assets that were built using Dev Studio, the assets must be configured as relevant records to ensure that they are editable in App Studio.
- In the header of Dev Studio, search for and open the pyPopulateCaseTemplates data transform.
- Save a copy of this data transform in your application layer if it is not already present.
- Add a new Append and Map to action for the case type that
you want to use as a template. Follow the pattern used by the out-of-the-box templates as shown in the following figure:
- Save the changes.
- In the header of Dev Studio, search for and open the cyApplyCaseTypeTemplate data transform.
- Save a copy of this data transform in your application layer if it is not already present.
- Add a new Append and Map to action for the case type that
you want to add as a template. Follow the pattern used in the pyPopulateCaseTemplates data transform.
- Save the changes.
Previous topic Configuring the Confirm harness Next topic Remote case types