Skip to main content
Contact a Moderator

Question

1
Replies
161
Views
 Chunzhi Hong (Chunzhi_Hong)
PEGA
Consulting Manager
Pegasystems Inc.
JP
Chunzhi_Hong Member since 2013 141 posts
PEGA
Posted: June 28, 2016
Last activity: June 28, 2016
Posted: 28 Jun 2016 4:58 EDT
Last activity: 28 Jun 2016 21:56 EDT
Closed
Solved

7.2 pyResolvedTimeStamp is missing if work object is restored from archived zip file created by PurgeArchive tool

I found that pyResolvedTimeStamp is missing if work object is restored from archived zip file which is created by PurgeArchive tool.

Is this intended behavior or is this a potential defect of PurgeArchive tool ?

If pyResolvedTimeStamp is not exported, what's the purpose for this behavior?

Case Management Data Integration System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 5 years ago
Posted: 28 Jun 2016 21:56 EDT
Chunzhi Hong (Chunzhi_Hong)
PEGA
Consulting Manager
Pegasystems Inc.
JP

It turns out that the work object doesn't have pyResolvedTimeStamp value from the beginning due to the application bug.

However, the exposed column pyResolvedTimeStamp was updated manually before running PurgeArchive tool, so the work object without pyResolvedTimeStamp in the BLOB also included in the archive file.

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