Skip to main content

Delete PR_LOG and PR_HISTORY tables using DDL scripts

Submitted by on

We had an issue on one flow of our application, that generated a lot of records on pr_history and pr_log tables, due to a loop in a wait shape (more than 15.000 records per case).

We need to purge these records, since they are not useful, and they are occupying more than 60% of Pega's tablespace.

Is it safe to delete them manually, using a DDL script?

Thanks in advance,

Fabio A.

How to check the MIME Type of a file before upload

We have implemented the file type(extension) checking based on file name (sample.txt) and restricting the user to upload certain types of files.

There is a possibility of changing the extension of different file type and upload to the application.

Ex: User has an executable file webex.exe and this can be changed to webex.png by renaming it and can be uploaded.

How to check the file type(or mime type) based on the content (not just the filename)?

Resolving issue with a stale WorkLink

Submitted by on

Post upgrading from v7.21 to 7.3 to a new infrastructure (a new app url), a case management feature making use of WorkLink  correspondence fragment was found degraded. The direct link to work object (embedded in outgoing emails) pointed users to the old environment.

Troubleshooting:

Verified below Dynamic-System-Setting  is set with current application url.

Pega-ProCom • PublicLinkURL (Pega-ProcessCommander)

Root cause:

Getting Error in retrieving a class definition in find when doing Property-Set-XML

I am doing Property-Set-XML based on the XSD structure imported into the application. All the properties are set in the XML stream rule based on mapping but in the last step of Property-Set-XML, i see FAIL step and below error :

** Error in retrieving a class definition in find **

Due to this, the Connect-REST step is also not executed. Has anyone seen this issue before ?

Please suggest.

Pega Platform 7.3.0 and Pega Marketing 7.22

I am trying to configure an agent to call a remote API and then update the return status back to database. In the following step in the agent, it will retrieve those records with errors and send emails to the campaign creator to notify them of the errors. 1 agent process can pick up multiple campaign result, and these campaigns may be created by various marketing users.

I know I will need to do the following:

1) Use RDB-List to retrieve the list of error records

2) Do a loop in OOTB function.

Subscribe to 7.3

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