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
6 replies
Subscribers
8 subscribers
Views
3091 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
catch error in SAIL interface
eliav
over 7 years ago
Hi All,
does exist a method to catch all raised errors in a form , send detail to environment administrator and show to the user only a message like "An error occurred, please contact System Admin" ?
Thank you
Elia
OriginalPostID-268539
Discussion posts and replies are publicly visible
0
Alok Patro
over 7 years ago
What kind of errors do you want to deal with ?
Is it validation errors or something else you are talking about ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
eliav
over 7 years ago
All errors can be raised by rules
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
AFAIK, there's no OOTB functionality to do this, but design errors (i.e. errors that came up in SAIL) are captured in design_error.csv
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
The file I mentioned (design_error.csv) is a system log file you can access if you have Admin level access.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jamalc8231
over 7 years ago
As reginaldm377 stated, there is no OOTB functionality to do this on the sail side, but you can do error handing in the process model to send an email to a group/users to if a stored procedure fails.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
josephh
A Score Level 3
over 7 years ago
Ideally your forms wouldn't error to begin with. There's a sort of catch 22 here which makes it at the very best difficult in Appian. To my knowledge there is no out of the box functionality to trigger an action when an error occurs, so to implement this you would need to identify the sections of your code that are causing the error, and display the desired message. But if you know where in the code the errors are, best practices state that you should fix the issue rather than displaying an error message. A custom plugin might be able to address this by detecting the error in Java and firing off actions based on what occurred, but that's probably more work than simply testing more rigorously to find issues before your users do.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel