Hi,
I would have a theorical question :
Let's say I have a very complex process that count 60 nodes, and the latter can not reach the end because of the 50 nodes limit.
Let's admit that 30 first nodes car be executed in parallel with the 30 remaing nodes. Does the limit of 50 nodes will occur nevertheless?
(using an AND gateway for the 2 paths)
Discussion posts and replies are publicly visible
Yes, that limit still occurs. However, using a sub-process or the start process smart service you can execute those 30 nodes in parallel and get around the limit.
Thank a lot for your reply Danny.
You mean one of these patterns ? (is it a second AND to reconcile the 2 paths?)
It seems like you might be forgetting that this "limit" almost exclusively applies to continuous Activity Chaining between two user input tasks. If user input tasks do not come into play, then the 50-node limit should almost never be relevant.
In my example, the nodes are chained together and there is no input task between the nodes.
But what do you mean ?
Why do the nodes in your example need Activity Chaining enabled, then?
Oups, sorry Mike, this is an error in my screenshot... I should have remove the activity chaining...
Then where is the Activity Chaining that breaks the 50-node limit taking place?
I thought it was not the activity chaing that cause the error, but the number of nodes.
the scenario I had in my head that cause the limit error is :
Input Task 1 -> subprocess with 60 nodes -> input task 2
I think we need to take a step back. Can you please clarify in detail:
Mike, we have already experienced the 50 nodes issue from many interfaces.
Here is an example:
We work on an application that displays a rich interface with a lot of section and fields.
When the user submit the data (from a button), a big process is called (with more of 50 nodes that are mainly composed of script tasks and DB data updates), and then after the end of the process, the main screen does not display the updated data.
When we look at the DB, all the data are correct (all new, deleted or updated records are fine).
All is nearly fine except the screen is not refreshed.
When we press F5 to refresh the browser, the screen is fine with all the data.
2 years earlier, we've asked the question to an Appian architect, which have explain us the 50 nodes limit, and advised us to reduce the number of nodes (or to group update data in a multiple DP store smart service).
In our case, we've reduced the number of nodes, and indeed, is has solved the issue.
The process in question, is a big process that contains many sub processes but no input task.