Branch logic is great. A fantastic compliment would be a loop action. It would get linked with a model and start with row zero. Following the “Start loop” action, It would perform the action sequence on row zero of the model, then when it hits the “end loop” action, anything between Start Loop and End Loop in the action sequence would run on row 1… then row 2… then row 3… etc… row n… It would be like a mass action on steroids. You could use it in any button or model action… it could be nested in a larger sequence of actions. Combined with branch logic you could do really advanced stuff like "adopt rows into a twin model for all rows in the model that have the type “pending”, Then update the owner of those records to the running user, save the twin model, query the original model and display the twin model in a table in a popup in edit mode. Optionally, end loop could be assigned a merge variable (whole number) instead of being linked to a model. The user could then choose to have the loop run 6 times if they want to create six duplicate records as part of a product ordering system.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.

