ForEach task problems
|Target version:||RapidDeploy - 5.0-FIX|
|Affects Version:||5.0-FIX||Additional version details:|
It's me again. :) Here attached please find a printscreen of sample project where I tried to add nested ForEach loop. It's not possible through "Conds&Loops" button but is still possible to do through "+ Task" button. But there is one difference: in case when loop task is added through "+ Task" button it does not have "hasNext?" node. Please compare the upper node and a lower one.
- Status changed from New to Marked for Closure
- Assignee set to Vadim
- Target version set to 5.0-FIX
Unfortunately it is not possible to nest loop tasks in the orchestration.
You can include an "IfTask" inside an "IfTask", a "ForEachTask" or a "WhileTask"; but you can not include a "ForEachTask" or a "WhileTask" recursively inside a "ForEachTask" or a "WhileTask".
That's the reason it is disabled in the main panel. We still need to disable them inside the "+ Task" menu also though, I already passed a note to my team.
If this is something that generates a big inconvenience to you, let me know and we'll try to find a workaround together. ;-)
It is also worth to mention the conditionals and loops in the orchestration are not meant to be for complex constructions but to allow a more efficient relationship between the tasks.
I found this in our documentation:
Conditionals and loops are meant to create simple ‘code’ constructs between tasks to allow you to orchestrate the relationship between tasks more efficiently. If you have more complex code for specific actions, that cannot be accomplished in the set of existing tasks, then add a ‘Script Code Runner’ task and enter your bash, shell, perl, ruby or python code directly into it.
I hope this makes it a bit clearer! :-)
- Status changed from Marked for Closure to In Progress
- Assignee changed from Vadim to Mariano
I'm assigning this to you so you can fix that little problem about allowing to include loop tasks recursively inside loops from the "+ Task" button.
Let me know if you need any help!
- Status changed from Resolved to Marked for Closure
- Assignee changed from Rafael to Vadim
RapidDeploy 5.0.20 is already out with a fix for this, please feel free to close this ticket if you're happy with it or we will just time it out in a few days time.