The actions provided for the component are Open component with data, Close component, Maximize component, Minimize component, Restore component
and Clone Component with data
. These actions are executed for the component, which means that the component itself does not implement anything on its end.
Each action has an input parameter with a formatted name. The name follows the format: event.component.XXXX
. For example, event.component.restore
. Each action is enabled to call a second action after the component action has been called. To call an action, you must specify in the component properties what action or actions to call with the key name <event id>.action
. For instance, event.component.open.action
. This can optionally be a list of actions using two semicolons to delimit the action names. The actions must be part of the target component and enabled at the time of the event.
The close component action closes the viewpart. Any data passed into the action is ignored.Maximize component
The maximize component action performs a show view with the Maximize flag passed in.Minimize component
The minimize component action performs a show view with the Minimize flag passed in.Restore component
The restore component action does a show view with the Restore flag passed in.Open component with data
This action is registered whether the component is visible or not. In addition, it takes the input of the action and can optionally assign the value as a string to the target component's data area. This means the component can have new data posted to its composite application preferences for when it is opened.Clone component with data
The action works off a special preference on the component. The preference tells the action what preference should contain the property as a string when the component is opened. The key is event.component.open.data.key. An example of this is a Notes® view.
The clone action is similar to the Open action, except that it actually clones the component and allows a specified number of them to be on the screen at once. This is useful if you have a reusable component for which you want to open multiple windows (or tabs) and initialize it with different data.Parent topic: Using component windowing properties and actions with composite applications