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

 Madhukar Ganesh Chatra (mganeshchatra3)
Ernst & Young LLP

Ernst & Young LLP
US
mganeshchatra3 Member since 2017 1 post
Ernst & Young LLP
Posted: Apr 2, 2018
Last activity: Apr 6, 2018
Posted: 2 Apr 2018 10:53 EDT
Last activity: 6 Apr 2018 9:14 EDT
Closed

Storing the Case Attachment to a customised table

Hi,

I have a requirement of saving a case attachment to my own customized table rather than PRPC default Data-WorkAttach. (I have a requirement to store the data to a table with Key and Blob as columns).

I am trying with a approach where I am changing all OOTB rules related to saving attachments by replacing Data-WorkAttach- class with my own class linked to the table. It is creating the attachment instance in my own customized class but its not saving the data in the back-end DB.

Kindly let me know if there is any other approach or my own approach has some flaws.

Regards,

Madhukar Chatra

To see attachments, please log in.
Low-Code App Development
Case Management
Data Integration

Posted: 6 years ago
Posted: 6 Apr 2018 8:56 EDT
Anil Vanaparthi (vanaa)
PEGA
Senior Manager, Services Engineering, Case Management
Pegasystems Inc.
IN

As the OOTB rules will be final , you wouldnt be able to edit them. 

You can achieve this by customizing the  Work-.pyAttachContent flow action and write your own custom post processing activity to upload the files to your specific class or db.

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