Object-Specific Quick Actions Considerations

• The Quick Actions card supports a maximum of 10 quick actions for each object. Each object can have up to 10 layouts, including the default. If you define more than 10 layouts, the card shows the default layout and the top remaining layouts. The mobile app won’t use a quick action if it exists in a matching layout pattern, but isn't one of the 10 allowed quick actions.
• Similar to global quick actions, object-based quick actions are shown only on cockpit pages and are sorted by name in ascending order.
• It’s assumed that Consumer Goods (CG) Cloud mobile-specific global actions will also appear in other apps if they show global actions.
• When you try to open an object-specific quick action, the mobile app only checks whether the main record linked to it is loaded. It doesn't check if there are any pending updates or related changes for that record.
• To verify that object-specific quick action can be launched, the mobile app framework checks if the record for the object-specific QA request is uploaded. However, it doesn't check for pending updates or if all dependent changes for the record are pushed.
• Use the mobile application's namespace to derive the full object name. Do not use objects from a different namespace.

Modeling Considerations

You can link each page in the CG Cloud mobile app to multiple business objects. To make quick actions appear, the business logic must specify the relevant object. To achieve this in your customization project, configure the platformObject property in the business object contract by using these guidelines:

• Each business object contract contains the platformObject property in the header. In the platformObject property, specify the name of the object for which quick actions should be shown.
• You can reference only 5 unique platform objects in a deployment package.
• In the business object contract, you must define one simple property with ID as true. This ID is passed in the context as the record ID when object-based quick actions are launched.
• If needed, specify recordTypeId of type DomIdto identify the layout for which quick action metadata should be applied, especially when multiple record types are defined for the same object.

  <BusinessObject name="BoExample" platformObject="<name of the object for which quick actions should be shown>" <Omitted other items for brevity> >
      <SimpleProperties>
          <SimpleProperty id="true" name="<name of the key>" type="<type>" dataSourceProperty="<data source property>" />
          <SimpleProperty name="recordTypeId" type="DomId" dataSourceProperty="<data source property holding record type id>" />
      </SimpleProperties>

• Determine the primary business object in CG Cloud mobile app with MainBO. Each process can link to several business objects. To identify the primary object for which the object-based quick actions should be shown, the app uses the business object with the name MainBO. After identifying the MainBO, the quick actions defined for the platform object associated with that MainBO determines the quick actions to be shown.

  <Process name="<process name>" <Omitted other items for brevity>>
    <Entry>
      <ProcessContext>
        <Declarations>
          <Declaration name="MainBO" type="<BO type>" />
        </Declarations>
      </ProcessContext>
   
      <!-- <Omitted existing details for brevity/> -->
  </Process>

• You can associate a process flow with multiple user interfaces (UI). As platform object data is associated with a process, all the UIs associated with the same process work with the same platform object data.