Each Go To Task should have its own Number of Cycle, and each "Number of Cycle" should be available in XML too :
(https://roadmap.strategyquant.com/tasks/sq4_9929/edit)
2/ As long as a Go To task is not hit, its number of cycle should stay = 0. The number of cycle should be added only when its Go To task is hit.
3/ On a Go to task , once the condition is false on the "Number of Cycle", then the Go To Task is not active, we should have the the option Reinitiate the "Number of Cycle" to = 0 in the config task (via XML)
Like that, we could use the Go To task as a For Next loop
Actually we can not have 2 Goto task in one Custom Project, this is really a challenge to not have this goto task working correctly
Goto Task are fundamental in a Custom Project construction, we really need this to be fixed, please make it a normal priority, (we had this bug in B135 already.)
Please see : https://drive.google.com/file/d/1Xjf2g9VI7bJtQcobhfZLiVF8Qm1M-li0/view?usp=share_link
Description changed:
Each Go To Task should have its own Number of Cycle, and each "Number of Cycle" should be available in XML too :
(https://roadmap.strategyquant.com/tasks/sq4_9929/edit)
As long as a Go To task is not hit, its number of cycle should stay = 0. The number of cycle should be added only when its Go To task is hit.
2/ On a Go to task , once the condition is false on the "Number of Cycle", then the Go To Task is not active, we should have the the option Reinitiate the "Number of Cycle" to = 0
Like that, we could use the Go To task as a For Next loop
Actually we can not have 2 Goto task in one Custom Project, this is really a challenge to not have this goto task working correctly
please see : https://drive.google.com/file/d/1JdiTEZdEhy5nqjP8vF2HcIRppGgRA5BF/view?usp=sharing
Description changed:
Each Go To Task should have its own Number of Cycle, and each "Number of Cycle" should be available in XML too :
(https://roadmap.strategyquant.com/tasks/sq4_9929/edit)
As long as a Go To task is not hit, its number of cycle should stay = 0. The number of cycle should be added only when its Go To task is hit.
2/ On a Go to task , once the condition is false on the "Number of Cycle", then the Go To Task is not active, we should have the the option Reinitiate the "Number of Cycle" to = 0
Like that, we could use the Go To task as a For Next loop
Actually we can not have 2 Goto task in one Custom Project, this is really a challenge to not have this goto task working correctly
Goto Task are fundamental in a Custom Project construction, we really need this to be fixed, please make it a normal priority, (we had this bug in B135 already.)
please see : https://drive.google.com/file/d/1JdiTEZdEhy5nqjP8vF2HcIRppGgRA5BF/view?usp=sharing
Description changed:
Each Go To Task should have its own Number of Cycle, and each "Number of Cycle" should be available in XML too :
(https://roadmap.strategyquant.com/tasks/sq4_9929/edit)
As long as a Go To task is not hit, its number of cycle should stay = 0. The number of cycle should be added only when its Go To task is hit.
2/ On a Go to task , once the condition is false on the "Number of Cycle", then the Go To Task is not active, we should have the the option Reinitiate the "Number of Cycle" to = 0
Like that, we could use the Go To task as a For Next loop
Actually we can not have 2 Goto task in one Custom Project, this is really a challenge to not have this goto task working correctly
Goto Task are fundamental in a Custom Project construction, we really need this to be fixed, please make it a normal priority, (we had this bug in B135 already.)
Description changed:
Each Go To Task should have its own Number of Cycle, and each "Number of Cycle" should be available in XML too :
(https://roadmap.strategyquant.com/tasks/sq4_9929/edit)
2/ As long as a Go To task is not hit, its number of cycle should stay = 0. The number of cycle should be added only when its Go To task is hit.
3/ On a Go to task , once the condition is false on the "Number of Cycle", then the Go To Task is not active, we should have the the option Reinitiate the "Number of Cycle" to = 0 in the config task (via XML)
Like that, we could use the Go To task as a For Next loop
Actually we can not have 2 Goto task in one Custom Project, this is really a challenge to not have this goto task working correctly
Goto Task are fundamental in a Custom Project construction, we really need this to be fixed, please make it a normal priority, (we had this bug in B135 already.)
Description changed:
Each Go To Task should have its own Number of Cycle, and each "Number of Cycle" should be available in XML too :
(https://roadmap.strategyquant.com/tasks/sq4_9929/edit)
2/ As long as a Go To task is not hit, its number of cycle should stay = 0. The number of cycle should be added only when its Go To task is hit.
3/ On a Go to task , once the condition is false on the "Number of Cycle", then the Go To Task is not active, we should have the the option Reinitiate the "Number of Cycle" to = 0 in the config task (via XML)
Like that, we could use the Go To task as a For Next loop
Actually we can not have 2 Goto task in one Custom Project, this is really a challenge to not have this goto task working correctly
Goto Task are fundamental in a Custom Project construction, we really need this to be fixed, please make it a normal priority, (we had this bug in B135 already.)
Please see : https://drive.google.com/file/d/1Xjf2g9VI7bJtQcobhfZLiVF8Qm1M-li0/view?usp=share_link
Status changed from In progress to Fixed
Attachment image-0.png added
Attachment image-0.png added
Number of cycles (current Go To EVALUATED)
Number of cycles (current Go To ACTIVATED)
Please check the attached screenshot for more details.