I have come across that Pega has marked temporary cases as deprecated. I saw several questions on this board that confirm that fact, and a couple Pega resources stating “We have requested our documentation team for a technical explanation on why temporary cases are now deprecated. (FDBK-82664 and US-443539 )”
Where can I find documentation that outlines the reasoning behind deprecating this useful feature?
I am aware of the “workaround” via the setting on the case type rule and am making use of it.
@Nick Morgano The documentation about the previous functionality can be found here:
Open the Case Management book
US-443539 was closed with the explanation
Temporary cases are only stored in memory on the clipboard and not in the Pega Platform database so the reason for deprecating temporary cases is attributed to the following:
" pega is moving towards stateless microservice architecture. So, keeping user data in database is only possible option. But for temporary work object all the case data is not stored in database making it difficult for stateless architecture."
Please see: Temporary work objects in Pega 8.5
“Due to the stateless nature of the DX APIs, temporary cases aren’t supported.”
See: DX API and Temporary cases
@ArunSarada might be able to comment more.
@MarijeSchillern So we need a JS to clean up unresolved persisted temporary cases?
@GaneshKumarC3200 I’m afraid I don’t have an answer for that. I’ll check internally…
Can you clarify what you mean when you say you have unresolved persisted temporary cases? How do these manifest?
Does the documentation Persisting temporary Cases answer your question?
@ArunSarada can you help here?
