Does Studio support definition of new document types that extend a custom base document type defined in a custom Marketplace package?

I have a custom Base Document Type defined in my own Marketplace package. Would its definition need to be implemented instead in Studio in order to allow me to create document types in Studio that extend it? Or is there a way to “register” my Marketplace package with Studio such that Studio parses and incorporates the relevant configuration information from the Marketplace package? Assuming this feature is not available, would I be able to manually load the relevant XML configuration files into Studio such that my custom Base Document type is available for extension within Studio? How would the manually loaded configuration be maintained moving forward?

Also, is there a scenario in which a Studio package would have a dependency on a Marketplace package? Is this currently supported?

1 votes

1 answers



Hi Ron,

I've just published a blog about this:

Let me know if it answers your question.

1 votes