You can put the following variables within the <Dict> node of the EditorialConfig configuration file. For instructions, see Adding or overriding variables in your EditorialConfig.

Find the actual values of such variables in EditorialConfig item in EdAdmin4, the Application Configuration > Client Applications, searching for EditorialConfig. The data is common for all titles in the system.

Should you need to specify different values of variables for different typographies, look for instructions at the Typography-dependent overridable variables.

Since 1.4.1599.x, you can define on the global level which elements are to be added to an article when creating it, either from scratch or from a story.

There’s a global preference EdConfig.glbNewArtElts.

By default, it’s an empty string, thus the GN4 system behaves as before – it always adds a body element, and it adds some extra elements, if they’re selected in the user’s personal preferences.

If you add the below line to the <Dict node of the Editorialconfig, e.g.

<Item Name="glbNewArtElts" Value="head,subhead,intro" />

… taking care to write-in only the names of the valid article elements, delimited by comma (without the leading and trailing spaces, without trailing comma), e.g. as in above example, putting “head, subhead,intro”, on each creation of an article in Ted or Fred or during merge, all the listed elements will be added to the article automatically, overriding related personal preferences.

Important notes

•System doesn’t check if the content of the glbNewArtElts string represents a series of valid article elements – il will go to error if you write a nonsense name(s).

•System doesn’t take out leading and trailing spaces, extra commas or similar – it will go to error. Don’t use spaces, count well the commas.

•Body element is added by default, so don’t write it in the Value.

•The order in which article elements are entered is not important.

•As for now, if the head element is specified in the string, it will be added to the article when merging a wire, but the head content will not be populated automatically.

•If your custom add-ins contain a newarticle sub, remove it - it’s not needed anymore, the standard subs will handle the above as explained.