We are using more and more ruby scripts and currently you can only assign them to the custom buttons etc. It would be very useful to set them up in a similar way to layer liost groups, Stored Query groups, themes groups etc. so that you can import, export, save them, drag and drop them in to a model. This would significantly improve how they are managed etc.
Disclaimer: The development, release, and timing of any features or functionality described or discussed for our products in this User Feedback Forum for Autodesk Water Products and Services remains at our sole discretion. This User Feedback Forum for Autodesk Water Products and Services is not a commitment, promise, or legal obligation to deliver any functionality, is intended solely to outline and gather feedback about our general product direction, and should not be relied on in making purchasing decisions.
With wider use of Ruby scripts like this, I think it would be worth adding some basic safety measures as well, such as detecting if a script is likely to load any potentially dangerous libraries (e.g. fiddle, win32api) and warning the user, or maybe restrict them altogether from this kind of UI script being stored in the DB.
This would also be very useful in ICM