Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
7 subscribers
Views
3004 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi, Has anyone managed to catch the exceptions thrown by Appian and
Rully
over 11 years ago
Hi,
Has anyone managed to catch the exceptions thrown by Appian and handle the exception via the process model? I want to be able to show a generic screen to the user when an unhandled exception occured and send it to the relevant developers rather than let it bubble up through alerts.
Thanks,
Rully...
OriginalPostID-80813
OriginalPostID-80813
Discussion posts and replies are publicly visible
0
Rully
over 11 years ago
We are using Appian version 6.6.1 by the way.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
venkateshr
over 11 years ago
Integration nodes are generally what cause exceptions (that aren't obvious during design time) and are required to be handled. The method to handle such excpetions differ based on the node that is used. For example, DB nodes come with a provision to pause or exception or continue with error. Web service nodes could be wrapped in a sub-process with a timer/retry logic in the parent model. An automated process to review the process with problem report is another option to handle exceptions.
Here are some links that provide good documentation on error handling/exceptions:
forum.appian.com/.../Exception_Handling
forum.appian.com/.../Handling_Process_Exceptions
forum.appian.com/.../Prevent_and_Recover_from_Common_Process_Problems
forum.appian.com/.../Configuring_Automatic_Error-Handling
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rully
over 11 years ago
Hi Venkateshr,
Thanks for the links. I have seen some of the links that you provided. In general, most of the those information describe preventive actions as such the errors must be handled/resolved during development & testing stages. Although I don't disagree with the idea, I doubt that we could come across those errors and handle them 100%.
What I would like to do is basically inform the users in an informative and graceful manner that an error has occured (rather than going back to the dashboard page as if nothing happen) and then we can email the corresponding team to deal with the problem. At the moment, we can only do this for any errors coming from the web service by showing a custom error page and send the alert forwarding the fault text or custom error message sent back from the web service. If we can do the same for the other nodes then that we would have a consistent approach to deal with any process exceptions globaly within Appian.
Any suggestion/work around?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Rully
over 11 years ago
Furthermore, it would probably be nice to build a custom plug-in or suggest Appian dev team to enhance the product by introducing a new node to catch the global exceptions within the process model and allow the process designer to develop an exception path starting from that node. Not sure if anyone has developed the plug-in for this (or if it's possible to do in custom plug-in?). I haven't seen it being posted in the "shared components" section. Surely it will be a very useful feature for everyone here :)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel