Exception Handling.

RE: Exception Handling.

Robert Shankin — Mon, 18 Mar 2019 14:35:09 GMT

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 changes without notice.

RE: Exception Handling.

davel001150 — Mon, 18 Mar 2019 13:47:16 GMT

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.

RE: Exception Handling.

paulc919 — Wed, 13 Mar 2019 09:27:18 GMT

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 ?

RE: Exception Handling.

Abhay Dalsaniya — Wed, 13 Mar 2019 09:25:05 GMT

Try using try() function. Syntax: try(<smart service call>, <code exception handling>)

RE: Exception Handling.

Chris — Thu, 05 Jan 2017 20:40:19 GMT

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

RE: Exception Handling.

Dastagiri Dudekula — Thu, 05 Jan 2017 09:55:02 GMT

@csteward where should I find this option?

RE: Exception Handling.

Chris — Thu, 05 Jan 2017 00:28:06 GMT

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.

RE: Exception Handling.

bhanuprakashm — Wed, 04 Jan 2017 17:52:25 GMT

@dastagrid,please look into this link.
forum.appian.com/.../e-239253
its related to same post.

RE: Exception Handling.

sparshs — Wed, 04 Jan 2017 17:47:29 GMT

Can you please elaborate this issue?

RE: Exception Handling.

rodgraham — Wed, 04 Jan 2017 17:22:07 GMT

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

RE: Exception Handling.

Dastagiri Dudekula — Wed, 04 Jan 2017 13:08:25 GMT

*no not know