Events are activities that occur during the execution of a GUI application, such as windows opening and closing, controls being clicked, and so on. These events can result from user interaction, from the GUI application itself, or both.
The CA Gen runtime keeps track of these events. Event processing is a notification mechanism. A CA Gen-generated GUI application can be notified after an event occurs. After the GUI application is notified, it can respond by executing procedure action diagram (PrAD) logic. You associate the PrAD logic with the event.
Notice that the notification occurs after an event has taken place. Event processing is not a capability of deciding what events do and do not happen. The application cannot change the event after it has occurred. The application can, however, be notified that an event has occurred and then process PrAD logic.
You can create the following types of events with the Navigation Diagram tool:
Different controls can be associated with different event types. For more information, see the Toolset Help.
Event processing does not change the overall process of creating applications, including client/server applications. It does make it easier, however, to design the user interface and create the PrAD logic as concurrent activities. You can chain back and forth between the PrAD logic and the Navigation Diagram tool conveniently.
As far as the design of client/server applications is concerned, events are only client based because they involve GUI applications. Event processing provides the capability to do more flows to a server because the flows could be from event actions. An application could flow to a server at almost any time based on the events that trigger the flow.
|
Copyright © 2013 CA.
All rights reserved.
|
|