Form Personalizations: Custom Menu, Changing LOV, Exporting Hidden Canvases

Creating a custom menu to call another form;
In R12 adding new menu(button) under Tools is quite easy. Selecting Action Type as "MENU" and then assigning a menu-special (one of the first 15) is enough. Though to start another action via this button, one more personalization is required which has the assigned menu as trigger event.

Changing LOV using Forms Personalization requires 2 actions:
1- Builtin> Builtin Type:Create Record Group from Query, Arguments:"your select", Group Name:"your select's name".
2- Property> Object Type: LOV, Value:"your select's name"
Selecting the exact columns for the LOV is critical; for example to change a lookup code, "lookup_code" should be selected besides "meaning"

Exporting hidden canvases;
Lets think of a case you want to export purchase order lines including the information in "note to supplier". Because of being under a different canvas exporting the same line twice is the solution. But there is a personalization for this (starting with R12):
when new form instance
object type: block
target object: line
property name: export hidden canvases
values : true

Note: For form personalizations using a database value or using a form value both possible! Example of usage for a forms value ":po_lines.attribute1", for a database
value: "${item.po_lines.attribute1.database_value}" and of course a query can be written to use the database value.