While using Intent for drawing creation, it would be very useful to be able to use a workpoint as an entity to attach a balloon/leader to.

It would be very useful if we had a couple of dropdowns that included Children, Methods, and Rules as it is with .net.  In .net, it lists all of the methods in the active class.  This would be useful in the Design Editor as well as in Visual Studio when you are working with design files.

This would be especially useful on large designs where you may have lots of rules and/or children.  You should be able to click on an item (ex. "Length") and the window will jump to that rule.

Sorting by the values in the properties grid will give us the ability to more easily find rules based on the expected values.  This is especially helpful when working on datasets by others who have not properly documented the rules in a way that it is easy to find the rules in question.  In the case below, I know that the tank is 72 inches tall from my measurement of the Inventor model.  If I could sort by the Values then I would be able to very quickly find that the associated rule is very likely TankHeight.  My understanding is that the grid below is a DevExpress grid and column sorting is a property setting.  That simple and quick change would be quite helpful for debugging.

It would be very useful to be able to sort the ivPartsList in Inventor ETO.  The user should be able to select a property to sort on and the direction of sortation.  

This functionality already exists in Inventor.

Inventor ETO should have the capability to reverse engineer and configure from an existing iPart / iAssembly factory + incorporate rules from iLogic. There should also be an option to create configurations through a flowchart / flowdiagram rather than through code.

Have a field in the ETO adoption wizard (parameters window) menu that identifies parameter being driven by iLogic. This  would prevent both iLogic & ETO from trying to modify the same parameter.

As it stands, the ETO documentation has improved greatly from a year ago.  What's lacking is documentation describing when to use specific features.  I suggest to make a best practices knowledgebase which answers questions for anyone looking to start a new project.

Some example answers might include:

• Benefits of Server vs series. Is there any reason to use server if everything will be used internally?
• What is the best way to build a large ETO project when considering performance?
• When should we use intent code vs push a function into a dll?(again considering performance)
• If we wanted all out parts to be stored in a database that ETO can just call, what would be the first steps to set up the database and ETO to make them work together?
• Best practices for using ETO to generate a document. (The current example is too small scale.  Maybe have an example that generates a document that will insert items to a loop of bookmarks)

This may look like a lot of suggestions at once.  All I'm asking is for someone who has built a number of ETO projects to put a bunch of advice somewhere ETO developers can read it.  The more topics covered the better.  

I'd be happy to clarify since each of these are problems I've run into over the last year. I'd be happy to clarify or give a longer list if anyone wants.