The ECM Connector 2.0 feature is not exposed via Form API or publicly supported URLs. The only supported solution for including it in a form is via the element. There is nothing to prevent you from reverse engineering the URL, but things may change in future releases and you will have to redo you customizations.Your point about ECM 1.1 being more flexible than ECM 2.0 is spot on. A toolkit with source code is always more flexible than a productized feature. On the flip side, the ECM Connector 2.0 is easier to configure, more robust and has many additional features (search, direct import, MediaBin runtime params, etc.). I will file a feature request for proper "Form API access", but I can't make any promises about when it will be available.Best Regards,Cliff