Promote method for dynamic scored features

Our users often have the need of creating new feature definitions on-the-fly that are only relevent for a particular job, if not just a single map. While these could be defined in the GSA, we refrain from during so since

  1. The procedure is cumbersome (our users need to contact us, we have to allocate time for creating the feature definition, metadata/workspace files must be exported and distributed, and they must update their local files)
  2. We don't want the GSA-schema to be flooded by lots of feature definitions that are rarely used
  3. We are unable to predict all of the cases in which our users could possibly have need of a new feature definition

In the pre-Bentley Map era, creating a new feature definition would be accomplished by creating a new level, setting up the symbology and start working on this level. This method seems to transit well into the Bentley Map GSA-setup as the first element drawn on the new level will adopt the geometry type from the element and create a new feature definition in the Session-category within the Command Manager. Every subsequent feature created using this new entry in the Command Manager will be a native feature using the symbology defined by the level.

This works well, but the usage is limited to creating new features by hand using the placement method created when the feature was dynamically scored. The reason for this is the lack of creation of a corresponding promote method. As such, our users are unable to perform tasks such as

  1. Apply the dynamically scored feature definition on elements created from standard Microstation drawing tools
  2. Morph existing native features into the dynamically scored feature definition

Is it somehow possible to control what methods the DSF-engine produces (i.e. Promote in addition to Place)? If not, I would like a change request on the matter.