Posted: 11 Jan 2019 6:40 EST Last activity: 17 Jan 2019 6:00 EST
How does Agile Workbench screenshot functionality work in Chrome?
I'm trying to enable screenshot functionality in Pega CSR 7.3.1 in Chrome and have found that the Agile Workbench has a working screenshot functionality that uses the Pega Screen and Video Capture extension for Chrome.
I'm trying to enable this functionality from the Interaction Portal and have made some progress but need some help, preferably from a Pega developer.
How the screen capture seems to work:
Clicking the "Capture Screen" button in Agile Workbench (see Agile Workbench.PNG) triggers two functions "cleanBeforeStart_GI" and "screenCaptureInit_GI", both available in pzagilesmartfeedback.js (see pzagilesmartfeedback.txt and pzagilesmartfeedback.PNG). These in turn trigger a bunch of other functions available in either pzagilesmartfeedback.js or pzpega_ui_gapidentifier.js (see pzpega_ui_gapidentifier.txt and pzpega_ui_gapidentifier.PNG).
The result is a small screen capture window (see Capture Screen.PNG). Clicking "Capture screen" here triggers the function "captureScreen_GI" (this is the part I'm interested in).
As far as I can tell the Pega Screen and Video Capture extension takes over from here (see Share screen.PNG).
Once the screenshot has been "shared", Pega takes back control and adds it to a user story in the Agile Workbench, but I assume this could be changed so the attachment could be added to another work item.
What I have done:
If anyone knows how the Screen Capture function in Agile Workbench works or how I can further debug the functionality, your support is greatly appreciated.
Note: I raised an SR (SR-C84483) but it was quickly dismissed as "out of scope" and I was directed to the forum. I have also added the information in my old post
Pega does not recommend to change the internal scripts and do not provide support for the customized ones by the end users. Currently the capture screen and record video functionalities are very much tied to Agile Workbench work items in Chrome only and there are some plans in the roadmap to expose these as some sort of generic APIs.
I don't plan to change the internal scripts. I just want to copy the functions I need to call the extension from my own custom script. However, Pega has made it very hard to understand what is going on in the internal scripts, which is why I was hoping someone could enlighten me.
I'm fully aware that this only applies to Chrome and is therefore not a cross-browser solution.