- Odoo Development Cookbook
- Table of Contents
- Odoo Development Cookbook
- Credits
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Installing the Odoo Development Environment
- 2. Managing Odoo Server Instances
- 3. Creating Odoo Modules
- 4. Application Models
- Introduction
- Defining the Model representation and order
- Adding data fields to a model
- Using a float field with configurable precision
- Adding a monetary field to a Model
- Adding relational fields to a Model
- Adding a hierarchy to a Model
- Adding constraint validations to a Model
- Adding computed fields to a Model
- Exposing Related fields stored in other models
- Adding dynamic relations using Reference fields
- Adding features to a Model using inheritance
- Using Abstract Models for reusable Model features
- Using Delegation inheritance to copy features to another Model
- 5. Basic Server Side Development
- Introduction
- Defining model methods and use the API decorators
- Reporting errors to the user
- Obtaining an empty recordset for a different model
- Creating new records
- Updating values of recordset records
- Searching for records
- Combining recordsets
- Filtering recordsets
- Traversing recordset relations
- Extending the business logic defined in a Model
- Extending write() and create()
- Customizing how records are searched
- 6. Advanced Server Side Development Techniques
- 7. Debugging and Automated Testing
- Introduction
- Producing server logs to help debug methods
- Using the Odoo shell to interactively call methods
- Using the Python debugger to trace method execution
- Writing tests for your module using YAML
- Writing tests for your module using Python unit tests
- Running server tests
- Using the Odoo Community Association maintainer quality tools
- 8. Backend Views
- Introduction
- Adding a menu item and window action
- Having an action open a specific view
- Adding content and widgets to a form view
- Adding buttons to forms
- Passing parameters to forms and actions: Context
- Defining filters on record lists: Domain
- List views
- Search views
- Changing existing views: View inheritance
- Document-style forms
- Dynamic form elements using attrs
- Embedded views
- Kanban views
- Show kanban cards in columns according to their state
- Calendar views
- Graph and pivot views
- QWeb reports
- 9. Module Data
- 10. Access Security
- 11. Internationalization
- 12. Automation and Workflows
- 13. Web Server Development
- 14. CMS Website Development
- 15. Web Client Development
- 16. Server Deployment
- Index
We added a button in the previous form, but there are quite different types of buttons to use. This recipe will add another button; also put the following code in to the previous recipe's header element.
Add a button referring to an action:
<button type="action" name="%(base.action_partner_category_form)d" string="Open partner categories" />
The button's type attribute determines the semantics of the other fields, so we'll first look into the possible values:
action: This makes the button call an action as defined in the ir.actions.* namespace. Thenameattribute needs to contain the action's database id, which you can conveniently look up with a python format string containing the XML ID of the action in question.object: This calls a method of the current model. Thenameattribute contains the function's name. The function should have the signature@api.multiand will act on the currently viewed record.workflow: This sends a workflow signal to the current record. Thenameattribute needs to contain the signal's name. Use thestatesattribute to make the workflow buttons only available in states where they actually do something, that is, in states that have transitions triggered by the signal in question.
The string attribute is used to assign the text the user sees.
Use CSS classes btn-primary to render a button that is highlighted (currently blue) and btn-default to render a normal button. This is commonly used for the cancel buttons in wizards or to offer secondary actions in a visually unobtrusive way.
The call with a button of type object can return a dictionary describing an action, which will then be executed on the client side. This way you can implement multi screen wizards or just open some other record.
You can also have content within the button tag, replacing the string attribute. This is commonly used in button boxes as described in the recipe Document style forms.
-
No Comment