The help topics in this section describe actions that you can use in scripting application behavior in USoft Definer and USoft Window Designer.
actions vs. actions
USoft product documentation uses 'action' and 'action' with the same meaning.
Unlike 'action', the term 'action' implies a relationship with a class that exposes that action.
Most of these are technically methods defined for GUI classes and exposed by GUI objects. The relationship between GUI objects and the actions they expose is most clearly visible in the Object Activator tool in USoft Windows Designer. From this tool, you will typically write scripts with the syntax
In many other USoft scripting environments, the relationship to the current GUI object is understood and you will only write the action name:
Also, many actions are unrelated to GUI design. They are more data-centered. For example, the action:
is related to the current transaction.
Because of these two reasons, in many USoft contexts the relationship between actions and classes is not prominent. This reference section lists actions simply by their name. Where appropriate, the relationship with one or more classes is indicated in a section headed "Exposed by".