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.

It is not recommended instantiating an action just to invoke it once programmatically. For such tasks, use the corresponding API method instead. For example, when you write a piece of code that needs to publish content, use the API method PublicationService#publish(content, callback) instead of creating a temporary PublishAction.