For GN4 applications

GN4 applications load configurations (*_tabitems.xml and *_config.xml) in the following order:

•Shell4: Shell4_xxx.xml

•Admin4: shell4_xxx.xml, Admin4_xxx.xml,

•EdAdmin4: shell4_xxx.xml, admin4_xxx.xml, edadmin4_xxx.xml

•Ted4: shell4_xxx.xml, ted4_xxx.xml

•Fred4: shell4_xxx.xml, ted4_xxx.xml, fred4_xxx.xml

The loading order is important as the duplicated items get overwritten. An example: you have the same dialog defined in shell4_xxx.xml, ted4_xxx.xml and in fred4_xxx.xml. When running Ted4, the active dialog will be the one defined in ted4_xxx.xml - it overwrites the same dialog defined in shell4_xxx.xml. But, when running Fred4, the active dialog will be the one defined in FREd4_xxx.xml - it overwrites the same dialog defined in files loaded previously.

Note: the load configuration is changed in version 1.6. Moved pubDest and SendCalendarObject related objectUIs from Admin4_config.xml to shell4_config.xml.

 

For browser