# Common action properties

Certain properties are shared across all actions, ensuring consistency and flexibility in configuration. These common properties allow you to define behaviors, appearance, and functionality that apply universally, regardless of the specific actions used. This simplifies the setup process and helps maintain uniformity across different jigs.

## Icons in actions

Adding an `icon` property in an action only applies to `swipeable`, `secondary`, and `header` actions. Primary actions do not support icon setups.

## Working with parent & child actions

When configuring actions across parent and child jigs, the following behavior applies:

* If both the parent and child jigs have an `action` configured, the child’s configuration takes precedence and overrides the parent’s.
* If only the parent has an `action`, it automatically applies to the child.
* If only the child has an `action`, it is used in the parent jig as well.

## Dual action buttons

{% columns %}
{% column %}
Configure `actions` to display two action buttons on the jig's main screen. In this example, the first button has a secondary button `style` applied, by default, the button normally uses the primary color. Additionally, you can set up a third action, referred to as a secondary action button, that appears when the ellipsis (...) is tapped. This allows multiple action options to be accessible within a single jig.
{% endcolumn %}

{% column %}

<figure><img src="/files/6hxVZ5gqBbRfkj0crccW" alt="Dual action buttons &#x26; secondary button"><figcaption><p>Dual action buttons &#x26; secondary button</p></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

| Property                 | Description                                                                                                                                          |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| `numberOfVisibleActions` | Configure this property to display multiple action buttons on the screen. The recommended number is two. A numerical value is expected, such as `2`. |

```yaml
actions:
  # Number of visible buttons displayed on the jig.
  - numberOfVisibleActions: 2       
    children:
      # First action button.
      - type: action.go-back
        options:
          # Apply a style to the button. 
          style:
            isSecondary: true
          title: Back
      # Second action button.                
      - type: action.go-to
        options:
          title: Continue
          behaviour: new
          linkTo: contact  
      # Third action button configured (secondary action).
      # The button displays when the ellipsis is tapped.    
      - type: action.execute-entity
        options:
          title: Save  
          provider: DATA_PROVIDER_DYNAMIC
          entity: default/contacts
          method: create
          data:
            firstName: =@ctx.components.firstName.state.value
            lastName: =@ctx.components.lastName.state.value
            email: =@ctx.components.email.state.value
            phone: =@ctx.components.phone.state.value
            jobTitle: =@ctx.components.jobTitle.state.value
            companyName: =@ctx.components.companyName.state.value    
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.jigx.com/examples/readme/actions/common-action-properties.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.