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
5 replies
Subscribers
5 subscribers
Views
2076 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
On a given exception the parallel bypass for the given process did not work
Dhiraj Kumar
over 7 years ago
We have a parent process model that called a sub-process )( calling a web-service ) . The sub process failed while mapping the CDTs in the process model and we got the foloowing exception
ERROR:An error occurred while evaluating expression: individualQualifileResponse_cdt:ac!outMap[1].spvv (Invalid index: Cannot index bean property 'spvv') (Data Outputs)
This was the first problem .
The other problem was that the Exceptions path for this was not picked up . The exception path was configured on the sub-process based on a timer ( 1 minute ) .The script task configured on this is not getting invoked after the elapse time
OriginalPostID-235817
Discussion posts and replies are publicly visible
0
sanjays0006
over 7 years ago
Dhiraj,
For the 1st issue, try mapping the process variables instead of activity class parameters.
I don't think you can map activity class paramters as input or output for a subprocess node.
For the 2nd issue, unless the sub process node is started,the exception timer would not be activated.
As of now in the issue shown, sub process node is stuck with an error before even getting started.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
PhilB
A Score Level 1
over 7 years ago
Have a look here:
forum.appian.com/.../Exception_Flows.html
- "Error events are not currently supported as exception flow triggers."
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Stefan Helzle
A Score Level 3
over 7 years ago
I think a failed node will NOT trigger ANY exceptions. A solution could be to have a timer in parallel to the sub process to catch possible errors inside.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
harshav
over 7 years ago
We had a similar issue where we kept a timer in front of the Node and retriggered if the status is not met for the timer, and once it is not triggering for more than 2 times or so, we made the flow go through exception path.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
harshav
over 7 years ago
Exception path in the sense in an other alternate way.... not from the exception path of the failed node...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel