You can use the Device Application Designer to create device applications that use structure mobile business objects as the data source.
When a mobile business object (MBO) is dropped from Workspace Navigator to the Flow Design page, the screens and their relationships are created automatically. The screens consist of the Cell listing screen, a Detail screen, and Operation forms screens, which include the create, update, and delete operations. Any existing relationship creates more screens by repeating the process on the relationship MBO.
You should not drag and drop a structure MBO from WorkSpace Navigator because it will be treated like an unstructured MBO, so any references from this MBO to other structures (attribute types with an array type of “structure []”) are returned with a relationship, which means that these “sub-structures” will also create a full set of screens. You can drag and drop an unstructured MBO that references a structure MBO onto the Flow Design page. This will ensure that the screens will be created correctly.
MBO operations that reference a structure in the operations (without the type being an array “[]”) are flattened as single parameters in the Device Application Designer.
If the MBO structure reference is an array of structures, a screen set is generated that allows you to see the list of the structures and handle the create, update, and delete operations, as well as the details of the structure.
An operation that references a structure array type which in turn references another structure array, is not supported in the Device Application Designer.
When a personalization key is assigned as a single value inside the structure, the key is mapped as a normal personalization key in the operation dialog for a flattened parameter. For flattened items, no parameters are generated in the operations, so a form without these parameters is generated and the operation dialog shows the personalization key assigned, but the user cannot change the configuration.