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
11 replies
Subscribers
6 subscribers
Views
10163 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Exception Handling.
Dastagiri Dudekula
over 7 years ago
Could you please let me know how to catch the exception in the running smart service(esp. when there is know status indicator in the output) and handling?
Scenario, when two parallel updations are occuring on the same record at the same time. One updation results in exception. In this instance I the process becomes stagnant forever unless there is any configuration like exception or deadline.
OriginalPostID-256025
Discussion posts and replies are publicly visible
Top Replies
Abhay Dalsaniya
over 5 years ago
+1
Certified Lead Developer
Try using try() function. Syntax: try(<smart service call>, <code exception handling>)
Robert Shankin
over 5 years ago
in reply to
Abhay Dalsaniya
+1
Appian Employee
As noted by some of the other Community members. Please don't use fn!try(). As it's not documented, it's never been supported for use by Designers at large. It could be disabled or subject to behavior…
0
Dastagiri Dudekula
over 7 years ago
*no not know
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rodgraham
Certified Lead Developer
over 7 years ago
Don't think you can capture it - you can either implement a locking mechanism - either pessimistic or optimistic (whichever best fits your use case) to prevent the issue. You could also put a timeout exception on the failing node to allow it to continue but that wouldn't let you know why it failed
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sparshs
over 7 years ago
Can you please elaborate this issue?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
bhanuprakashm
over 7 years ago
@dastagrid,please look into this link.
forum.appian.com/.../e-239253
its related to same post.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 7 years ago
I'm hoping that eventually we get the 'Continue on Error' setting available again (as it was for the Query DB service) at least for Write to Datastore nodes - that was a great help in designing error handling.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Dastagiri Dudekula
over 7 years ago
@csteward where should I find this option?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Chris
over 7 years ago
dastagirid, this option is only available in the Query DB service - I was commenting on how it would also be helpful if it were available one day in the Write to Datastore service. In Query DB, it is referenced as "Pause Node on Error".
forum.appian.com/.../Query_Database_Smart_Service.html
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Abhay Dalsaniya
Certified Lead Developer
over 5 years ago
Try using try() function. Syntax: try(<smart service call>, <code exception handling>)
Cancel
Vote Up
+1
Vote Down
Sign in to reply
Verify Answer
Cancel
0
paulc919
over 5 years ago
in reply to
Abhay Dalsaniya
I'm not sure that is advisable to call native java functions ? We ought to be using Appian as it is out of the box - if there are enhancements we need then maybe we ought to raise them with Appian ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Dave Lewis
Certified Lead Developer
over 5 years ago
try() is not just native Java function. It's actually native Appian expression language function. Try() accepts 2 parameters, a function or rule reference and a string to be returned instead of pink box if a pink box would otherwise be the result.
It's great stuff, except that it's not documented and thus not recommended that anyone use it for anything ever.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>