cancel
Showing results for 
Search instead for 
Did you mean: 
Jonas
Level 4
Status: New
The fact that only the latest screenshot is shared per VM, not linked to which process / queue item that was processing, is not very convenient.
The following features would make this functionality more powerful in terms of debugging & troubleshooting;
  • store a (browsable) history of screenshots, not just the latest
  • create a link between screenshots and their triggering exceptions 
    example usage: open screenshot, click 'go to exception' and immediately have the process/VBO open with the screenshot next to it, ready to debug.
  • link queue exceptions to their respective screenshots
    example usage: when looking at a certain failed queue item, click 'view screenshot' (if available) and see what went wrong for this specific queue item.
2 Comments
fkargman
Level 3
I agree that this should be an available feature. Meenwhile, you could use this object from the digital exchange to take a screenshot when ever you want in your process flow: https://digitalexchange.blueprism.com/dx/entry/4714/solution/rmr---utility---screenshot
LubosGurka
Level 5
I have my own screenshotting c# object using during exceptions. Works nicely, no need to rely on BP. With unique naming schemes its even easier to identify the issue.