Define Merge Actions for Detailed Field Properties

Use the Properties page in the Field Properties window to define whether or not to overwrite the following property merge areas:

  • Whether the field is required.
  • Whether the field is read-only.
  • Values: Default and calculated values, as well as values to set before a Business Object is saved.
  • Options based on lifecycle state: Behaviors and values based on the Business Object's lifecycle state (only applicable if the Business Object has defined lifecycle states).

    For CSM 10.2.0 or later versions, use the Business Object Lifecycle Editor to add a lifecycle to a Business Object. See: Open the Lifecycle Editor.

    The Field Properties window is available in the Business Object Editor (accessed from within the Object Manager in the mApp Editor).

Good to know:

  • You can only configure separate merge actions for individual Business Object fields and field properties if the Business Object is set to Merge in the Business Object Properties window (mApp Solutions page). If the Business Object is set to any other option, or if Include in mApp Solution is cleared, then you cannot configure separate merge actions for individual Field properties.
  • For more information about behavior properties, refer to Define Behavior Properties for a Field.
  • If you are configuring merge actions for Business Object fields that were previously applied as part of a Protected mApp™ Solution, the main differences are:

    • You see a shield icon next to each content-protected field.
    • If a Business Object field is content-protected, it cannot be deleted. This includes menu, context menu, toolbar, and related buttons.
    • Default fields in a content-protected Business Object cannot be edited in any way but you can add new fields and then edit or delete them.
    • When a Business Object is content-protected, you can increase its field length from the default and decrease it back to the original default length.
    • You can use a content-protected Business Object property field in a Full Text Search by selecting the check box on the Search Results page.
    • See Protected mApp™ Solutions.

To define merge actions for field behavior properties:

  1. Add a Business Object to a mApp Solution using the Add Business Object to mApp wizard.
  2. Open the Field Properties window for a field in the Business Object you just added to the mApp Solution:
    1. In the Object Manager within the mApp Editor, select the Edit Business Object task in the Structure area.

      The Business Object Editor opens, displaying the list of fields with a mApp Action column to show the merge actions selected for the fields in the Add Business Object to mApp wizard (either Overwrite or Do Not Overwrite. The mApp Action column is blank for fields set to Do Not Overwrite). If you set the Business Object to Merge in the Business Object Properties window (mApp page), then the selections made in the Defaults section (Default Behavior for Fields drop-down list) are also reflected in the mApp Action column.

      You can also select Edit Business Object Business Object Button on the mApp Editor toolbar to open the Business Object Editor.

    2. Select a field, and then select Field Properties.
  3. Set the individual field to Merge:
    1. Select the mApp page, and then select Include in mApp.
    2. In the Options area, select Import to Target System.
    3. From the If Already Present drop-down list, select Merge as the merge action for the field.
  4. Select the Properties page.

    Properties page of Field Properties window

  5. Select mApp [variable here] Merge Actions next to each property merge area, and then select a merge action:
    • Do not overwrite the <n> rule: Select this option to leave the specific property unchanged in the target system when the mApp Solution is applied.
    • Overwrite the <n> rule: Select this option to overwrite the specific property in the target system when the mApp Solution is applied.
  6. Select OK.

  7. Prepare the mApp Solution for Distribution (File > {Prepare mApp for Distribution), or save the mApp Solution (File > Save mApp to Disk) to continue making other changes.