Uniface 10: Changes in Triggers

Execute Trigger becomes Exec Operation

The Execute trigger of components was always treated as the default operation and exposed as the exec operation in the signature. In Uniface 10, this behavior is made explicit and the Execute trigger has become the exec operation, and is declared as such in the Script container:

operation exec
  public web
  ...
end

In contrast, the Application Execute trigger of the application shell is a system trigger. It has been renamed to apStart:

trigger apStart
...
end

Triggers

Triggers are now explicitly declared in an object's Script container using the trigger statement followed by the trigger name. In Uniface 9, only extended triggers were declared in this way.

Declaring a trigger in a derived object breaks inheritance, even if the trigger only contains non-executable code such as comments, spaces, or an entry.

For triggers that have default behavior, declaring such a trigger in an object that cannot inherit (supertype entity or field, modeled component, or a component that is not derived) disables the default behavior.

Trigger Names

The names of many triggers have been changed. The following table lists the old and new names of all triggers.