Posted: 6 Jan 2017 11:19 EST Last activity: 9 Jan 2017 23:04 EST
Pega External Assignment and its limitations
We have implemented external assignment using DWA flow. We would like to add a UI control that allow user to browse the file and attach it. I understand Ext Assignment would not allow any server calls but is there any control that can be used for this purpose? Any prompt help will be appreciated.
Thanks Asif for prompt respose, we are using "Attach Content" control only but getting "Access Denied" error on click of it. Seems like this is exiting issue with external assignment based on below artical on PDN. Not sure if we have solution for the same.
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.