Other tags

There are situations in which you might want to deviate from the strict layout groups prescribed. For example, if you want the name field of a record to be rendered as a heading, the field's label will interfere with the appearance. In this case, don't put your field into a group element, but instead into a plain HTML h1 element. Then, before the h1 element, put a label element with the for attribute set to your field name:

<label for="name" /> 
<h1><field name="name" /></h1> 

This will be rendered with the field's content as a big heading, but the field's name written in a smaller type, above the big heading. This is basically what the standard partner form does.

If you need a line break within a group, use the newline element. It's always empty:

<newline /> 

Another useful element is footer. When you open a form as a popup, this is a good place to put the action buttons. It will be rendered as a separate bar too, analogous to the header element.

Don't address XML nodes with their string attribute (or any other translated attribute, for that matter), as your view overrides will break for other languages because views are translated before inheritance is applied.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset