Okay, so the first decision to be made... do you want to put the button inside Atrium? Or inside each Genie/Rich Display session? The difference is that if you put it in Atrium, you will have one button with the potential for many applications running. So it might be hard to discern which application the user is having trouble with. If you put it inside your Genie skin, however, it'll be on each session (so a separate button in each Atrium tab) which might be a better choice. The Rich Display environment also has an HTML file, very similar to the one in the Genie skin, that you could add a button to if you wish to launch Rich Display sessions without going through Genie.
I'm a bit confused as to your answer to #1, however, since you say you're using Atrium to launch Rich Displays and to launch Genie, but later you want to launch the Rich Displays via Genie via Atrium. If the Rich Displays are working satisfactorily through Atrium directly, why would you want to add the extra overhead of a Genie session later? Ususally it works the other way around. People start launching everything via Genie because it's too hard to convert all the 5250 screens, and Genie lets you use both Rich and 5250 together. Once everything has been converted to Rich, they eliminate the Genie. For some reason you've suggested that you are going the other direction, working with some Rich Displays that aren't through Genie, but you want to convert them to use Genie later. Why would you do that?
With regards to screen shots... we have a variable inside both RDF and Genie sessions called pui.savedJSON. This contains all of the data sent from the IBM i to the JavaScript library (before Genie customizations were added.) You can use this to "re-play" the screen... so you can put Profound UI through the paces of re-drawing what the user had on their screen.
So my suggestion to you is this:
1) Edit the start.html file in your Genie skin, and maybe also in your Rich Display environment to add a small button. When you add it to this HTML file, it will be on all screens, so no need to code it into each program.
2) Have the button run a JavaScript function of your creation.
3) The JavaScript function can use an AJAX call to pass any relevant details that you've provided, as well as our pui.savedJSON variable, to a program running on IBM i. This can be written in any language... RPG works well, but it could also be PHP, Node.js, Java, whatever. It should be a web program, though... not a traditional RPG program. If you use RPG, our Univeral Display File tool should make this pretty easy to code.
4) The RPG program can generate an e-mail to send to your support staff including the information from the display. The savedJSON file should be sent as a text file attachment in the e-mail.
5) The support staff can save the JSON data to a web-accessible IFS file, and re-play it with a URL like
http://yoursystem/profoundui/genie?json ... o/jsonfile
This is just my opinion, of course. Please understand that I am not volunteering to write it for you.... just offering pointers to help you get on the right track. (I say this because the last person to ask something like this INSISTED that I write it for him.)