AFTER INPUT block

The AFTER INPUT block is executed when the focus is lost by a group of fields driven by an INPUT or INPUT ARRAY sub-dialog. This trigger is invoked if a field of the sub-dialog loses the focus, and a field of a different sub-dialog gets the focus. When the focus is in a list driven by an INPUT ARRAY sub-dialog, moving to a different row will not invoke the AFTER INPUT block.

If the focus leaves the current group and goes to an action view, this trigger is not executed, because the focus did not go to another sub-dialog yet.

In singular INPUT and INPUT ARRAY instructions, the AFTER INPUT is only executed once when dialog ends, while the AFTER INPUT block of the DIALOG instruction is executed each time the group of fields loses the focus.

AFTER INPUT is executed after the AFTER FIELD, AFTER ROW blocks and before the AFTER DIALOG block.

When using an INPUT ARRAY sub-dialog, the DIALOG.getCurrentRow() method returns the index of the current row when it is called in the AFTER INPUT block.

Executing a NEXT FIELD in the AFTER INPUT control block will keep the focus in the group of fields. Within an INPUT ARRAY sub-dialog, NEXT FIELD will keep the focus in the list and stay in the current row. You typically use this behavior to control user input.

In this example, the AFTER INPUT block is used to validate data and disable an action that can only be used in the current group:

   INPUT BY NAME p_order.*
     AFTER INPUT
      IF NOT check_order_data(DIALOG) THEN
        NEXT FIELD CURRENT
      END IF
      CALL DIALOG.setFieldActive("validate_order", FALSE)