Mobile Business Object Relationship Properties

Modify the relationship of two mobile business objects using the Properties view.

Relationship Properties
Tab Contents
General
  • Source object – the source MBO.
  • Source attribute – identifies the name of the source of the relationship, and is independent of any MBO attribute.
  • Target object – the target MBO.
  • Target attribute – identifies the name of the target of the relationship, and is independent of any MBO attribute.
  • Comment – a description of the relationship.
  • One-to-many, one-to-one, or many-to-one – select the type of relationship. By default, the relationship is one-to-many.
  • Composite – create, update and delete operations on a parent MBO automatically cascade changes to the child entity. For example, deleting the parent Customer MBO cascades directly to the child MBO Sales Order. This option is disabled for many-to-one relationships.
  • Bi-directional – indicates a two-way relationship and optional for all relationships, which enables selection of unidirectional, one-to-many, and many-to-one relationships.
Mapping View or change the mappings for this relationship. While attribute-to-attribute mapping is explicitly supported, you can also map:
  • Argument-to-argument mapping, including structure arguments (structure MBOs) – requires that you set a propagate to attribute for the argument, then map the argument from the relationship mapping tab. For example, the Customer MBO has an attribute named state and an argument named state_name, from the attributes Load Arguments tab, select state as the propagate to attribute for the state_name argument. Then map the state_name argument in a relationship.

    You must map sub-arguments when mapping structured arguments. For example, if Customer[] is the structured argument, and it contains state as a sub-argument, you must map the state sub-argument, and not the Customer[] argument.

  • Attribute-to-argument and argument-to-attribute mappings are also supported.
Appearance Modify the appearance of the text and line that represents the relationship. For example:
  • Fonts and Colors – changes the appearance of the relationship text displayed in the Mobile Application Diagram.
  • Routing – changes the routing of the relationship connector line displayed in the Mobile Application Diagram.
  • Line and arrows – changes the style of lines and arrows.
  • Smoothness – changes the Smoothness of the relationship line.
  • Jump links – changes the placement and appearance of any jump links.