Installer - Screens and Actions Groups

     


  Screen and action groups can be configured on the screens & and actions tab.
  Actions and screens can be grouped in the tree of installer elements. Groups of the same type can be nested, meaning that you can put a screen group into a screen group or an action group into an action group.

You can nest as many levels of groups as you wish. Next to the label of the screen or action group in the tree of installer elements, the number of all contained screens or actions is shown in bold font. Elements in nested groups are counted as well.

  Grouping has the following common benefits for screens and actions:
  • Organization
    If you have many screens or actions, groups emphasize which elements belong together. You can add a common comment to the group.
  • Common condition
    Groups have a "Condition expression" property that allows you to skip the group with a common condition instead of having to repeat the condition for each contained element.
  • Single link target
    If you want to reuse a set of adjacent screens or actions in a different part of your project, you can put them in a group and add a single link to that group instead of linking to each element separately.
  • Looping
    A group has a "Loop expression" property that allows you to execute the group repeatedly until the loop expression returns false.

The following benefits are exclusive to screen groups:

  • Jump targets
    When you jump to a screen programmatically (with context.gotoScreen(...)), it is more maintainable to jump to a group instead of to a single screen. You can think of the group as taking the function of a label in this case.

The following benefits are exclusive to action groups:

  • Break group on error
    Action groups have a boolean "On error break group" property. If selected, and one of the contained actions returns with an error, the control flow will step out of the action group and continue with the next element after the group. This behavior only takes effect if the problematic action has its failure strategy set to "Continue on failure".
  • Default error message
    You can define a "Default error message" for the group that is used for all actions that do not have their own error message configured.