Edit Actions and Links

You add actions or links in two steps:

1. Define an action or link for an object.

2. Use Application Composer's work area configuration pages to add that action or link to a user interface page, such as a list page or details page.

You can also manage the Actions menu by hiding or showing menu items, rearranging the action groupings or display sequence, and managing the toolbar by hiding or showing icons and buttons. You can also configure the Actions menu and buttons in Create and Edit subtabs.

To define an action or link for an object::

1. Sign in as an administrator.

2. Click Navigator > Configuration > Sandboxes. You can either create a new sandbox, or use an existing one and set it to active.

3. After you activate the sandbox, open Application Composer.

4. In the Application Composer, select CRM Cloud from the Applications drop-down list.

5. On the main Overview page in Application composer, select a standard or custom object in the object tree..

6. Select the Actions and Links node.

7. In the Create Action or Link page, enter a descriptive name in the Display Label field.

8. In the Type field, select either Action or Link.

9. In the Source field, select either Script or URL.

10. In the Script region click the New icon to build your script.

    • If the source is a URL, you can enter a static URL enclosed in double quotation marks. Or, you can define the URL by using the expression builder, which provides access to this object's fields to assist you in constructing the URL. .

      If this object has a parent or relationship with a source object, then optionally change the context to access another object's fields for URL definition. Any new functions that you create will be added to the Method Name choice list.

      If functions were already created for the object, then you can select one of them from the Method Name choice list. Object functions that are created elsewhere through other flows, such as server scripts, can also be used here. To switch the context to the object's parent or related source object, for access to the object's fields for the URL definition, check the Select alternative context check box

    • If the source is a script, you can either select a predefined object function from the Method Name choice list, or create a new object function using the expression builder. Any new functions that you create will be added to the Method Name choice list.

      If functions were already created for the object, then you can select one of them from the Method Name choice list. Object functions that are created elsewhere through other flows, such as server scripts, can also be used here.

      When creating custom actions based on a script for top-level custom objects, you can specify how you would like the action to conclude at runtime, after the script completes:

      • Save the record and return to the previous page (save and close)- Select this option to save the record and close the page.

      • Save and edit the record (save and continue)- Select this option to save and continue working.

      • Do not save the record (run the script only)- Select this option to perform the action but don't save the record, and run the script only.

      Note: Use the "Do not save the record" option so that the custom action is available and the user can select the action in the UI pages. If you select the first two options, the user can't select the action button.

    Points to consider when defining actions:

    • If you define a custom action and expose it on a list, ensure that you include a check for active record row, and that the UI supports users selecting any record as the active row before invoking the custom action.

    • Do not create custom buttons to populate the mandatory or required fields on the UI. End users must enter the values in the mandatory fields manually.

11. When finished, click Save and Close.

After you save actions or links, you can expose them on UI pages by configuring Application Composer options available in the Edit Summary Table page in the Pages node of an object. When displaying a link, you select it just as you select to display standard or custom fields. This is because, at runtime, the UI displays the URL link as if it's a field in a table.