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
6 subscribers
Views
1756 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Here is a grid in a form, when I input several rows data and continue, then here
simony
over 12 years ago
Here is a grid in a form, when I input several rows data and continue, then here are some nodes such as "script tasks", "sub-process" and etc.I met a weird phenomenen, if the rows rearch a threshold, the subsequent nodes can't be finished normally, especially "input task",the form can't show automatically and I need to move forward via open this task on Tempo or Portal. I think it caused by nodes limit setting. As I know, the limit is 50 on our cloud client. Or may be something wrong with my process model. I really have no idea, does any one can help me? Thank you so much...
OriginalPostID-38004
OriginalPostID-38004
Discussion posts and replies are publicly visible
0
akhileshn
over 12 years ago
If the "input task" is working as expected (apart from open this task on Tempo or Portal) then activity chain breaking is the issue. To know exact reason try debugging the process in monitor mode with data > threshold
It seems manipulations are done on individual rows of grid and subsequent activity chaining breaks when it crosses certain limit. If this is the case, then you can try using doforeach expression function.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
simony
over 12 years ago
Thank you so much, I tried several times again and I don't think it caused by chaining breaking. That's a good function.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
simony
over 12 years ago
I tried again in monitor mode,If the rows in grid reached a threshold, the flow stopped at the "input task" and the form showing needs to Initiate manually. If under the threshold the form could initiate automatically. So I think it caused by nodes limit.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
akhileshn
over 12 years ago
One other option to resolve this issue is by increasing the node limit. But still the best approach would be to avoid spawning of tasks.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel