Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Raghavendra Harish Deevi (deevh)
PEGA
Application Engineer, Healthcare Care Management
Pegasystems Inc.
IN
deevh Member since 2021 11 posts
PEGA
Posted: Jan 27, 2021
Last activity: Sep 29, 2021
Posted: 27 Jan 2021 10:31 EST
Last activity: 29 Sep 2021 6:18 EDT
Closed

Temporary work objects in Pega 8.5

From Pega 8.5 after doing some R&D and going through articles in PDN observed that Temporary work objects cannot be created.The reason I found in some articles is from 8.5 there is a "Create stage"(stage name) is being created automatically after a casetype creation.In older versions we had pyStartCase flow after casetype creation but this is not present from 8.5 .It mean from 8.5 Temporary work objects are no more supported? what may be the exact reason for this expected behaviour?

***Edited by Moderator Marissa to update Content Type from Discussion to Question; update Platform Capability tags***
To see attachments, please log in.
Pega Platform
Case Management
System Architect

  • Naga Sai Jonnalagadda peihang gu Pradeep Yarlagadda Lenka Rolinek SOLAIYAPPARAJA B
Posted: 3 years ago
Updated: 3 years ago
Posted: 27 Jan 2021 11:34 EST
Updated: 27 Jan 2021 16:24 EST
Saikat Chakrabortty (Saikat_Chakrabortty)
Capgemini
Pega Developer
Capgemini
IN

@HarishD4292

This is very good finding. Pega has deprecated the temporary case concept. But we can still enable it from the case type advanced tab.

Not sure about the business justification for the same, but temporary case was a really a good concept.

 

Thanks

Saikat

 

To see attachments, please log in.
Posted: 3 years ago
Posted: 30 Jan 2021 13:52 EST
Saikat Chakrabortty (Saikat_Chakrabortty)
Capgemini
Pega Developer
Capgemini
IN

@HarishD4292

I can think of an technical justification, 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.

 

-Saikat

To see attachments, please log in.
Posted: 3 years ago
Posted: 14 Apr 2021 2:40 EDT
MEKALA Mekala (MohanVenkatSaiM)
Coforge DPA
Software Engineer
Coforge DPA
IN

Hi @HarishD4292 We can create a temporary case n 8.5 also.

For that App explorer-->Case type-->Process-->Flow-->Create form--> Advanced Tab, scrolldown and tick the checkbox in temporary case.

 

Thanks

Mohan

To see attachments, please log in.
Posted: 3 years ago
Posted: 29 Sep 2021 6:18 EDT
Praveen Kamble (PraveenK8346)
Capgemini India PVT Ltd

Capgemini India PVT Ltd
IN

Hi @MohanVenkatSaiM,

Thanks for sharing. Just a small correction in steps to follow.

App Explorer >> Process >> Case Type >> pyDefault >> Advanced Tab >> Scroll down and check “Create temporary case that is not saved until a 'Persist case' step is reached”

or

Open Flow >> Process tab >> Click on "Open case type definition" >> Advanced Tab >> Scroll down and enable the check box “Create temporary case that is not saved until a 'Persist case' step is reached”

Thanks

Praveen

To see attachments, please log in.
Posted: 3 years ago
Posted: 11 May 2021 5:02 EDT
Lenka Rolinek (rolil)
PEGA
Lead System Architect
Pegasystems Inc.
AU

Keen to also hear what Pega best practice is going forward for scenarios where temp cases used to be used, e.g. check application status.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice