Components

A given component, depending on its type, supports certain types of actions and events. When the component is used as the source of the link, it can send the supported events to the receiver component. In the receiver component, only certain types of actions can be triggered.

EVENT examples

• on_double_click
  The event is triggered when the double-click action is executed in the source component.
  
  
• on_selection
  The event is triggered when the selection action is executed in the source component.
  
  

• on_navigate
  The event is triggered when a selection is made from the drop-down list enabled for each row or card in the source component.

  To enable the drop-down list in User mode, the on_navigate event needs to be linked with more than one action. Each link sourced in the same on_navigate event represents a possible selection from the drop-down list enabled in the source component. You can have more than one receiver component linked with the same on_navigate event.
  The drop-down is displayed:
  – for tables, in the Actions dedicated column.
  – for cards, in the top-right corner of each card, once you point to it.

  To change the name of the actions available in the drop-down, in the link configuration panel click one of the links sourced in the relevant on_navigate event to edit. In the Edit link, enter a label in the Label (optional) field. Do the same for each link.

ACTION examples

• set_filter
  When a specific event in the source component triggers the set_filter action in the receiver component, data available in the receiver component is filtered by a given set of dimensions.

  Configuration:

  • Broadcast - if enabled, the event sent through the link triggers the same action on all the different instances the user is logged in.
    
  • Dimensions to filter by - select the dimensions to be published in the receiver component when the set_filter action is triggered by an event from the source component.
    
  • Timeout - if you click multiple items in the source component within the set timeout period, only the last click is sent to the receiver component. Timeout period is set in milliseconds.
    
    

• set_context
  When a specific event in the FusionCapital Curves source component triggers the set_context action in the receiver component, a ReportDataSourceID is sent to the reporting API. FusionCapital Curves then retrieves data based on the ID and sends it to the receiver component. This event handler is provided for FusionCapital Curves components, but it can be configured for other business solutions too.

  Configuration:

  • Broadcast - if enabled, the event sent through the link triggers the same action on all the different instances the user is logged in.
    
  • Notify component - if enabled, the onComponentSave event is triggered once the data is received by the receiver component. The receiver component is then automatically refreshed.
    
    

• set_options
  When a specific event in the source component triggers the set_options action in the receiver component, data available in the receiver component is grouped by a given dimension. This event handler is provided only for table components.

  Configuration:

  • Broadcast - if enabled, the event sent through the link triggers the same action on all the different instances the user is logged in.