Cache Tool Container Output

[tavakian]

It would be great if Tool Containers had an I/O connector icon where you can connect the last tool in that container to and then Cache the container so that it wouldn't have to run every time.

For example, in the diagram below, the output of the Spatial Match would connect to an object such as the "I" that I drew below. We would then be able to cache the output of that container so that all objects in the container wouldn't have to run each time. The "O" would be the cached output and would feed the rest of the workflow. 

[KylieF]

Thank you for your idea!

We appreciate all the feedback we get and it's great to hear how we can improve users experience and understanding how containers are being used. It looks like you're relatively new to the idea board (welcome!) so if you haven't yet be sure to check out our Submission Guidelines as it goes over the idea board process in a bit greater detail including what happens after you post.

[SeanAdams]

This is a great idea - it makes use of existing caching, while allowing you to develop one container at a time and then just cache that piece

(gets around the fact that you can only have one cache point on a workflow at the moment)