Hi Sudhir,

You can use pxAttachContent control in your section to browse and attach it. But it has some limitation, it allow users to attach image files to an application only.

Kindly refer below links, as it contains details regarding implementation :-

https://pdn.pega.com/sites/pdn.pega.com/files/help_v722/procomhelpmain.htm#rule-/rule-html-/common/commonlayoutattachcontent.htm

Kindly notify, if it helps.

Adding to design implementation with screen-shots:-

https://pdn.pega.com/using-attach-content-control

Kindly let me know, if it helps.

Besides the restriction that DWA url's be "static", there's only one post allowed from the browser to the server.  So, for example, you click the link you received in the email and the Pega application launches and you see a flow action screen.

You fill in values on the screen and click "submit".   That "submit" uses a post to send the values to the server that you filled in on the form.  That post is the only one that is allowed.

So, if you can design a flow action screen that allows you to package up the file you want to attach, such that the entire file is sent in that one post, you may be able to get an attachment to work through DWA.  I have not tried this.  You can also see if the post-activity defined on your flow action rule (hmmm, this is a confusing different use of the word "post"!) is allowed to do soap calls.  If so, maybe you only need to convey the folder and name of the file you want to attach in the original post, and your flow action post-activity could do a soap call to talk back to a file server running on your computer to receive the actual file contents being attached.

In summary, the point is, to make attach work from a DWA-initiated screen, you need to limit that screen to ONE post.

Here's yet another article that describes the restriction:  https://pdn.pega.com/how-customize-directed-web-access

/Eric