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
actionconfigured, 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
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.

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.
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: [email protected]
lastName: [email protected]
email: [email protected]
phone: [email protected]
jobTitle: [email protected]
companyName: [email protected] Last updated
Was this helpful?