One feature we have been missing for a long time is to sort operations alphabetically in the tree. We have some web services with 20-50+ operations. After we do a "update definition" the new operations are added to the end of the tree. After a while this looks pretty messy 🙂 I have added this feature on trunk version 4.5.0-SNAPSHOT and created a patch which I hope you would consider to add.
Hmm, I don't know why the me of 2010 thought this was about the pending patch. The issue here is that file move prims in named patches are displayed in the alphabetical order rather than the order performed, which can be confusing from a UI point of view.
I don't think there's much we can do about this one. It may have to be a wont-fix.
Why is this a bad idea? I have to keep deleting my project and recreating it to get an alphabetically ordered view of my webservice operations. Super annoying. I'm not interested in the order in the WSDL, nor the order in which they were added.
If you really want to make new ones appear at the end, then at least provide a right click context menu operation to sort the operations. That would be an acceptable workaround.
I second this request. We need Order Operations (ie method names). Ordering Requests is not the same thing. Not sure why smart bear support is confused about this. Order Requests is not the same thing as Order Operations. Please add Order Operations.