I’m not sure how this would be possible or if it would be possible that it would be great if we could get a preview of how many elements would be affected or selected based on our category and filter selections before running a task.
A scenario that led me to this idea was when I was trying to create elevations based on Windows or storefront in my project. I thought I had set up the rules to capture only the unique instances of those based on a variety of filters and the unique element selection options but once I ran the task it took longer than expected. When it finally completed I found that I had not set up my rules correctly initially. Having the ability to preview the number of elements that would be impacted by the filters would be a huge benefit because it would save me and others the time of earning a task and realizing that it was set up incorrectly.
That’s a great idea! I’ll make sure to add it to our roadmap. In addition, we’re considering adding a warning or message to let users know when a task might take longer than expected due to the number of elements selected.
@Elliottk Just wanted to also chime in to say that I love this idea! Perhaps we could compute just the elements that meet your selected filter, every time you update the filter/selection criteria, and show a blue preview number in the corner or something, like so?
Perhaps the message could turn orange or red, and/or have a warning icon or something, if we think this task will take a long time. Anyway, just spreading some ideas!
Of course, this wouldn’t work for bundles, because sometimes the second task won’t know how many elements it will have until the previous task completes.
Yes! The screen shot you share is precisely what I was envisioning. It is enough to give the user a warning that the task set up will create 2,000 elevation views vs the 24 they might be expecting.
I understand the bundle limitation.. that one is much trickier to workaround. It may still be helpful to know how many elements the first task in a bundle will impact. Using the same example as above.. If I had a bundle that created, dimensioned, and tagged views, it would still be beneficial to know My first task was only going to crate 24 views and not 2,000.
