In Studio, you can create buttons that will show up on edition forms next to the Save button, and you can bind any automation chain to them.
If you are not already familiar with User Actions and Automation Chains, you might want to take a look at the "Use Content Automation" howto first.
This is what you should see after completing this howto:
Add a button on the editing form
- Create a new user action, and set the action category to Document Edition Form.
- Customize your action like you would do with any other actions (label, enablement...).
- Save your modifications.
On the next next deployment of your project, your button will show next the Save button of the edition form.
If you select "Document creation form" as the action category, the button will be displayed on the creation form.
Automation chain specific parameters
When your button is created, you need to bind it to an automation chain. Here are the parameters that your chain must hold:
- For automation chains bound to a user action in edition forms, you have to start you chain by fetching the document you are editing. You need to use the operation Fetch > UI Changeable Document to do that.
- At the end of your automation chain, it has to save all the modifications the user has done. The proper operation is User Interface > Save Document in UI. It will save the document like it is done by hitting the Save button.
Example: here is an automation chain that increments a major version automatically when the button is clicked.