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 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 dual action buttons & secondary button 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 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