The purpose of this mapping is to define a block layout for a module. It holds equivalent information to the layout editor in the application settings. The difference is that blocks can be defined to contain different options and that we can have many maps/configurations for the same module, whereas in settings you can have only one layout for all users of the application.
This map is currently not being used in the application. Its goal is to export different layouts to portal/external applications.
There are 6 types of blocks:
The accepted format is:
<map> <originmodule> <originname></originname> </originmodule> <blocks> <block> <label></label> <sequence></sequence> <type></type> ApplicationFields | FieldList | RelatedList | Widget | CodeWithHeader | CodeWithoutHeader <blockid></blockid> <layout> <row> <column>fieldname</column> </row> </layout> <loadfrom></loadfrom> related list label or id | file to load | widget reference <loadcode></loadcode> <handler_path></handler_path> <handler_class></handler_class> <handler></handler> </block> </blocks> </map>
If loadfrom is Widget then the directives handler_path, handler_class and handler, if given, will be used to construct the Detail View Widget reference object.
If loadcode is given the file indicated as the value will be executed inside the context of the record being loaded.