Use Actions in the platform

Action types can be seamlessly integrated across applications in Foundry. Read on to learn how to configure and apply an Action from Object Explorer and Workshop.

In the examples below, we use the term Single Action type to refer to an Action type using an object reference parameter, and Bulk Action type to refer to an Action using an object reference list parameter.

Object views

Actions can be added to an Object View using the Actions section.

When configuring the Actions section you have the option to:

• Add any Action as a button in the section.
• Give each button its own label and color.
• Change the default on-click behavior from opening the form to applying the Action immediately using the default values (if valid).
• Specify whether the button should be hidden or disabled if a non-visible parameter is invalid (the idea being that visible parameters could be corrected upon opening the form).
• Provide a default value for each parameter; this can be a property value of the current object or a "local" value (current user, current timestamp, current object, or a manually entered value).
• Override the visibility of each parameter.

As shown above, you can therefore use this section to offer multiple structured versions of the same generic Action (“Delay 10 minutes”, “Delay 30 minutes”, etc.).

Object Explorer

Actions will automatically be shown in three places across Object Explorer:

1. From the Actions dropdown in the Exploration View (top right).

Using the current set of objects, this dropdown is automatically populated with applicable bulk Actions.

2. From the Object Actions dropdown in the Object View (top right).

Using the current object, this dropdown is automatically populated with applicable single and bulk Action types.

3. From the Linked objects view section in the Object View (top).

Using the selected object(s), this dropdown is automatically populated with applicable single and/or bulk Action types.

Workshop

In Workshop, Actions can be configured and applied using the Button group widget.

This widget has the same configuration options as the Actions section in an Object View, with a few notable extensions:

• There are three possible layouts, all of which are shown above.
• The buttons have additional display options, including left/right icons, minimal styles, and tag styles.
• In addition to an Action, an individual button can trigger a Workshop event, URL, or object set export.

And one difference:

• A default value can be a variable, the current user, or the current timestamp

Read more about Actions in Workshop, or read the full reference for the Button Group widget to learn about all available configuration options.