Take Screenshot and attach it in Email

To get the most similar look and feel of the Appian screen I strongly recommend to use XSL-FO option from (dynamic document Gen plugin) , which is a way to control the whole PDF.

For me the scenario is like they need to report an issue and the error notification differs. Is there any other solution for this Josep

Well if you want to really make screenshots of the screen and send it thru mail, then you can start thinking about some robots, blueprism for example, you can take screen shots after opening Appian. But this is something extra to Appian.

But if you are reporting errors, please define what is an error?

for example SAIL exceptions(red box) because there are coding malpractices, then I think this can be solved.

If you are talking about external systems, then the robot can be a good option.

How often are you getting errors? Do you really need to automate the issues reporting?

Anyway if you are automating the error capture I think the most time consuming is to document how you got it, in this case you can make use of the process history and or implementing your own transition log. And the user can help you to get the screenshot.

You can always ask Appian to incorporate extra functionality like this,

Are you using an standard browser (everybody uses the same browser)? What about doing it thru the browser for example have an extension that take the screenshot and send an email to Appian, then appian starts the process based on the received email?

Are you in cloud? Using mobile app? Or just web?

Hope this helps,

José Pérez

If you intend to make this for testing purposes there are lot of tools which can help you.

Please give us more detail on your use case

we have already thinking of this option of using the RPA (BP) and get the doc from the output.

we are not using it for Testing purpose this is like if there is any issue in the screen we need to report it helpdesk.

Are you reporting Appian issues? Or external systems?

I think is Appian error, correct?, in this scenario RPA can work, or the robot class, or an extension in the browser, or an external application(screenshot tool) that at the end sends all the information to Appian, for example using WEBAPI.

Anyway, can you give examples of the errors you want to capture? How can this not be catch in the program/code?

BTW, when I said testing purposes I meant user acceptance, but as you said help desk sounds like production.

I think is Appian error, correct?, in this scenario RPA can work, or the robot class, or an extension in the browser, or an external application(screenshot tool) that at the end sends all the information to Appian, for example using WEBAPI.

Anyway, can you give examples of the errors you want to capture? How can this not be catch in the program/code?

BTW, when I said testing purposes I meant user acceptance, but as you said help desk sounds like production.

Its more of both Appian and Business errors