You defined a data-triggered action in a data-triggered action group.

Data-triggered action rules define when and whether data-triggered actions shall be executed. There is a limited number of activities which can be coupled with data-triggered actions. Data-triggered actions can be executed on inline editing in data workbenches, content areas and guided data entry views. In addition, creating, editing and deleting objects in data workbenches via generic create, edit, and delete operations can trigger data actions if the creation is via editor and not assigned to a workflow or wizard. In standard Alfabet views, data-triggered actions can be executed after successful execution of class-based buttons and after inline editing. All other button interactions like changes done in wizards, workflows, standard views, and custom reports cannot trigger data actions. You must define separate rules for changes done via inline editing and changes done via editors, including runtime editors. You can specify multiple rules for the same action.

  • An Operation-Based Data-Triggered Action Rule triggers actions on execution of inline editing of data in data workbenches, content areas and guided data entry views. In addition, creating, editing and deleting objects in data workbenches via generic operation buttons can trigger actions via this type of data action rules.
  • A View-Based Data-Triggered Action Rule triggers actions on execution of class-related buttons in standard views. Buttons for general activity like, for example, export of the view, cannot trigger actions. A view must be specifically assigned to an object class to trigger an action. If a standard view's name starts with the prefix of the object class, it is automatically having a class context. Views which are available for multiple object classes, like, for example, the Attachments view, must be embedded in a content area of the object class to trigger the action on button execution. Actions are triggered after successful execution of the button activity.

    Data-triggered actions have a base object. This is the object the query can refer to with the Alfabet parameter @BASE . This object is not necessarily identical with the object class the data-triggered action rule is defined for. For example, if you are having a platform matrix report within an application content area, the data-triggered action rule is defined for the Application target class and the PLATCOM_Matrix view. If you define the rule for the button to create new local components for the application's platform, the base class of the data-triggered action is the LocalComponent object class.

  1. Go to Configuration > Data-Triggered Actions > Data-Triggered Action Rules. Expand a section of the dataset for an Alfabet class to see the details of existing data-triggered action rules.
  2. Click + New.
  3. Select the type of data-triggered action you want to create and click OK.
  4. Define the data-triggered action rule in the editor.

    Mandatory attributes:

    • Technical Name: Define a unique technical name for the data-triggered action rule.
    • Name: Define a caption for the data-triggered action.
    • Target Class: Select the object class or object class stereotype of the object a user needs to change, create, or delete to trigger the actions. If you define the object class and object class stereotypes exist for the object class, the data-triggered action is executed for all stereotypes of the object class.
      • Some buttons in standard views do not handle stereotypes. If the data-triggered action defined for a button does not work with a stereotype specification, change the target class to the object class only.
      • Data-triggered actions have a base object. This is the object the query can refer to with the Alfabet parameter @BASE . This object is not necessarily identical with the object class the data-triggered action rule is defined for. For example, if you are having a platform matrix report within an application content area, the data-triggered action rule is defined for the Application target class and the PLATCOM_Matrix view. If you define the rule for the button to create new local components for the application's platform, the base class of the data-triggered action is the LocalComponent object class.
    • Definition of the user activity triggering the action:

      For operation-based data-triggered action rules:

      • Target Class Operation: Select the activity type that will trigger the actions.
      • Target Class Property: If the action shall be triggered on inline editing of object data, select the object class property for which a change triggers the action. If the action shall be triggered on closing an editor after any change to the object, do not set this attribute to any property.

        If you set a target class property, the action is NOT triggered when the property is edited in an editor, including runtime editors. If you want the data-triggered action to be executed also on closing of an editor, define a rule triggering the same action and leave the Target Class Property field empty.

      For view-based data-triggered action rules:

      • Target View: Select the standard view containing the button triggering the action. The view must be designed for the selected target class.

        All views starting with the object class prefix of the selected target object class can be selected. There is a number of views available for multiple object classes, like, for example, the Attachments view. For those views, the action can only be triggered if the view is embedded in a class-based content area for the target object class. To see which general views are applicable for an object class, you can use the class-based content areas listed in the Presentation tab under Content Areas > Standard Content Areas as a reference. If a standard view is added to the standard content area of the object class, you can also select it here as a target view.

      •  Target Button: Select the button for which successful execution will trigger the action. You will see only the subset of buttons which are capable of triggering actions in the drop-down menu. A button must meet specific requirements to trigger actions:
        • For example, it must be executed for an object class. Buttons triggering general activities like view export are not selectable.
        • It must be executed for a single object.
        • It must not open a wizard. Triggering of actions for wizard is handled via the wizard configuration.
    • Data-Triggered Actions: Select one or multiple data-triggered actions to be executed for the specified activity on the Alfabet user interface.

    Optional attributes:

    • Description: Enter a description that specifies the meaning of the data-triggered action.
    • Set Execution Order: If you have defined multiple data-triggered actions, you can change the order of execution in this field. Execution follows the specified order from top to bottom. Click the handle that appears when you hover over an entry and drag the entry in the execution order.