Errors in code stages should have the option to include the stacktrace

[JordanHarvey]

As a developer within Blue Prism RPA, I find myself adding functionality via code stages frequently to add missing core functionality.

Sometimes however a code stage can throw an exception with the following exception which makes debugging extremely difficult:

ERROR: Internal : Could not execute code stage because exception thrown by code stage: Object reference not set to an instance of an object.

It would be useful if Blue Prism could have an option to enable a "verbose" logging function which rather than rewriting the root exception, it compliements the rewritten exception with a full stacktrace.

[robert.nicklin]

Hi @JordanHarvey,

Thanks for taking the time to raise an idea.

In the latest release of Blue Prism Enterprise (v7.4) we've introduced a lot of new capabilities related to code stages. One such new capability is the option to add trace logging to code stages to allow you to declare more detailed logging statements within the code itself which I think would allow you to determine more easily which part of the code an error is coming from. Additionally, we've also introduced the ability to debug code stages in an external IDE such as Microsoft Visual Studio or Visual Studio Code - when debugging using this integration users have access to all the tools available within the IDE.

Can you confirm whether this enhancement would meet your needs around more verbose logging for code stages? I'm going to mark this idea as Needs More Info awaiting your reply.

Regards,

Rob