topic RE: Standardize exception naming in Digital Exchange

Standardize exception naming

rogerbro — Fri, 03 Jul 2020 08:33:00 GMT

We would like to "standardize" our exception naming in the way that every exception is in a format like "[object name] - [page / tab name]: some text"
Instead of doing this manually, we are looking for a more generic approach.

Is there a possibility to read the current object name and page name?
In this way we could have an "exception template" (with [object name] & " - " & [page name] & ": some more text" ), and only have to add the additional information / text.

We are automating a pretty big process with many application / objects.
Sometimes it is not so obvious from where the exception was thrown, especially for the people doing the operation / monitoring.

Thanks,
Roger

------------------------------
Roger Broechin
Developer
Helevetia Insurance
Europe/Zurich
------------------------------

RE: Standardize exception naming

mark-joseph.apostol — Fri, 03 Jul 2020 14:02:00 GMT

Maybe you can use local variable for page name and Global variable for object name then you can use it on Exception details

------------------------------
Mark Joseph Apostol
RPA Developer
Merck Business Solutions Asia Inc.
------------------------------

RE: Standardize exception naming

John__Carter — Mon, 06 Jul 2020 07:52:00 GMT

Hi Roger unfortunately there are very few 'context' functions available to a process or object, and none to enable your idea. I've previously raised this issue via an internal enhancement request and you can do the same here. When enough people 'up vote' and idea, it goes to the product design team for consideration.

------------------------------
John Carter
Professional Services
Blue Prism
------------------------------