A workflow that uses construct features for creating a new feature currently have no access to the abilities of feature templates. It would be nice for newly-constructed features to be able to use map-level defaults like these, rather than having to depend on setting subtypes in the geodatabase back-end.
I'm trying to think of other alternate methods for creating features that could benefit from feature templates, but can't come up with any off the top of my head.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.