Create temporary case in pega case type
In the Behavior section, select the Create temporary case that is not saved until a 'Persist case' step is reached check box.
The above option is removed in Pega 8.5+ onwards. Is there any way to create temporary case type in Pega?
Accepted Solution
Updated: 13 Apr 2022 12:36 EDT
Pegasystems Inc.
GB
@NizamThe required workaround is listed in another user question on the forum.
I believe you are referring to the functionality as documented in Creating Temporary Cases and Persisting Temporary Cases.
"You can only create a temporary case for case types without the default Create stage. Case types that you create in Pega Platform 8.5 and later have the Create stage included by default. You can only create a temporary case for case types that you migrate from Pega Platform 8.4 or earlier. For more information, see The Create stage."
Also see The Create stage FAQ
"If your business scenario absolutely requires creating temporary cases, you can create a temporary case on a case type rule form in Dev Studio.(...)"
We have requested our documentation team for a technical explanation on why temporary cases are now deprecated. (FDBK-82664 and US-443539 )
Lventur
IN
Yes you can create temporary case in pega v8.5 also. Please open your case type rule and under Advanced tab you will be having an option to enable temporary case creation process.
Tech Mahindra
IN
@Gunasekaran Baskaran Thanks for sharing the screenshot. But this option is deprecated from 8.5 onwards. Do you know why this is deprecated and removed from case type settings.
Infomatics Corp
US
@Nizam My thoughts is As pega is moving on to leverage to DX Api which is stateless, supporting temporary cases in Stateless behaviour may not be possible. I might be incorrect but with the way of DX APi implementation i see this is one of the reason for deprecating.
Tech Mahindra
IN
@Abhilash_K But it will impact other scenarios as well right.
Lventur
IN
We are not having any article which shows why pega deprecated temporary case creation logic...
As @MarijeSchillern mentioned, we need to wait until pega releases a document with proper explanation why his feature has been deprecated to know the exact business..