Actions combine some functional parts of your application with UI details to be attached to a component. Buttons, for example, are commonly associated with an action. The difference between designing an action and attaching a mere event handler to a component is that an action combines the handler code with UI details such as a name or a button icon, which simplifies reuse. CoreMedia Studio defines actions that work on content objects, for example for creating new content objects or publishing contents.
Actions are most commonly used in conjunction with buttons or (context) menu items. In
general, you should avoid invoking Actions directly - use the corresponding API method
instead. For example, assume you want to publish some content programmatically. You should
not invoke PublishAction in this case; instead, use the API method
PublicationService#publish(content, callback).
 |  |  |
 |