Openerp Technical Training v6 Exercises

Technical Training - Exercises Release 6.0.RC1

OpenERP 2010-12-06

Contents 1

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

3 3 3 3 4 4 4 4

Build an OpenERP module 2.1 Composition of a module . . . . . . . . . . . . . . . . . . . . . . . 2.2 Module Stucture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Object Service - ORM . . . . . . . . . . . . . . . . . . . . . . . . Predefined osv.osv attributes for business objects . . . . . . . . . . 2.5 ORM field types . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common attributes supported by all fields (optional unless specified) Simple fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Special/Reserved field names . . . . . . . . . . . . . . . . . . . . . 2.7 Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Action declaration . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

5 5 5 6 6 6 6 6 7 7 7 7

3

Building views: basics 3.1 Generic view declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 8 8 8

4

Objects Relations 4.1 Relational fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 10

5

Inheritance 5.1 Inheritance mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predefined osv.osv attributes for business objects . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 View inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11 11 11 12

2

Configuration 1.1 Open Source RAD with OpenObject . . . . . . . . . . . . . 1.2 Installing OpenERP . . . . . . . . . . . . . . . . . . . . . . OpenERP Architecture . . . . . . . . . . . . . . . . . . . . 1.3 Package installation . . . . . . . . . . . . . . . . . . . . . . 1.4 Installing from source . . . . . . . . . . . . . . . . . . . . . Typical bazaar checkout procedure (on Debian-based Linux) 1.5 Database creation . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

6

ORM Methods 6.1 Functional fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Predefined osv.osv attributes for business objects . . . . . . . . . . . . . . . . . . . . . . . . . .

12 12 13

7

Advanced Views 7.1 List & Tree . . 7.2 Calendars . . . 7.3 Search views . 7.4 Gantt Charts . . 7.5 (Charts) Graphs

14 14 14 15 15 15

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

8

Workflows

16

9

Security 9.1 Group-based access control mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ir.model.access.csv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17 17 17

10 Wizards 10.1 Wizard objects (osv_memory) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 Wizard execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18 18 18 18

11 Internationalization

19

12 Reports 12.1 Expressions used in OpenERP report templates . . . . . . . . . . . . . . . . . . . . . . . . . . .

19 20

13 WebServices 13.1 Python example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21 21

2

Based on a real case, this chapter covers: building an OpenERP module and its interface, Views, Reports, Workflows, Security aspects, Wizards, WebServices, Internationalization, Rapid Application Development (RAD) and Performance Optimization.

1 Configuration 1.1 Open Source RAD with OpenObject OpenERP is a modern Enterprise Management Software, released under the AGPL license, and featuring CRM, HR, Sales, Accounting, Manufacturing, Inventory, Project Management, ... It is based on OpenObject, a modular, scalable, and intuitive Rapid Application Development (RAD) framework written in Python. • OpenObject features a complete and modular toolbox for quickly building applications: integrated ObjectRelationship Mapping (ORM) support, template-based Model-View-Controller (MVC) interfaces, a report generation system, automated internationalization, and much more. • Python is a high-level dynamic programming language, ideal for RAD, combining power with clear syntax, and a core kept small by design. Tip: • • • • • •

Useful links Main website, with OpenERP downloads: www.openerp.com Functional & technical documentation: doc.openerp.com Community resources: www.launchpad.net/open-object Integration server: test,openobject.com Learning Python: doc.python.org OpenERP E-Learning platform: edu.openerp.com

1.2 Installing OpenERP OpenERP is distributed as packages/installers for most platforms, but can of course be installed from the source on any platform. OpenERP Architecture OpenERP uses the well-known client-server paradigm, with different pieces of software acting as client and server depending on the desired configuration.Client software. OpenERP provides a thick desktop client (GTK+) on all platforms, and a web interface is also accessible using any modern browser. Tip: Installation procedure The procedure for installing OpenERP is likely to evolve (dependencies and so on), so make sure to always check the specific documentation (packaged & on website) for the latest procedures. See http://doc.openerp.com/install.

3

1.3 Package installation Windows

All-in-one installer, and separate installers for server, client, and webserver are on the website

Linux

openerp-server and openerp-client packages are available via corresponding package manager (e.g. Synaptic on Ubuntu) OR using BaZaar bzr branch lp:openerp (or openerp/trunk for the trunk version) when identified on Launchpad, then cd openerp (cd trunk in the trunk version) and ./bzr_set.py

Mac

Look online for package installers for the GTK client, as well as tutorials for installing the server (e.g. devteam.taktik.be)

1.4 Installing from source There are two alternatives: 1. using a tarball provided on the website, 2. or directly getting the source using Bazaar (distributed Source Version Control). You also need to install the required dependencies (PostgreSQL and a few Python libraries - see documentation on doc.openerp.com). Note: OpenERP being Python-based, no compilation step is needed.

Typical bazaar checkout procedure (on Debian-based Linux) $ sudo apt-get install bzr $ bzr branch lp:openerp $ cd openerp && python ./bzr_set.py

# install bazaar version control # retrieve source installer # fetch code and perform setup

1.5 Database creation After installation, run the server and the client. From the GTK client, use File / Databases / New Database to create a new database (default super admin password is admin). Each database has its own modules and configuration. Note: Demonstration data can also be included.

4

2 Build an OpenERP module 2.1 Composition of a module

A module can contain the following elements : • Business object : declared as Python classes extending the osv.osv OpenObject class, the persistence of these resource is completly managed by OpenObject, • Data : XML/CSV files with meta-data (views and workflows declaration), configuration data (modules parametrization) and demo data (optional bu recommended for testing), • Wizards : stateful interactive forms used to assist users, often available as contextual actions on resources, • Reports : RML (XML format). MAKO or OpenOffice report templates, to be merged with any kind of business data, and generate HTML, ODT or PDF reports.

2.2 Module Stucture

Each module is contained in its own directory within the server/bin/addons directory in the server installation. The __init__.py file is the Python module descriptor, because an OpenERP module is also a regular Python module. Note: It is possible to declare a personal addons directory in the configuration file of OpenERP (passed to the server with the -c option) using the addons_path option

5

2.3 Menus The menuitem entity is a shortcut for declaring an ir.ui.menu record and connect it with a corresponding action via an ir.model.data record.

Exercise 1 - Module Creation Create the empty module Open Academy, with a corresponding menu entry in OpenERP

2.4 Object Service - ORM Key component of OpenObject, the Object Service (OSV) implements a complete Object-Relational mapping layer, freeing developers from having to write basic SQL plumbing. Business objects are declared as Python classes inheriting from the osv.osv class, which makes them part of the OpenObject Model, and magically persisted by the ORM layer. Predefined osv.osv attributes for business objects _name (required)

business object name, in dot-notation (in module namespace)

_columns (required)

dictionary {field names > object fields declarations }

_defaults

dictionary: { field names > functions providing defaults } _defaults[’name’] = lambda self,cr,uid,context: ‘eggs’

_rec_name

Alternative field to use as name, used by osv’s name_get() (default: ‘name’)

...

...

2.5 ORM field types Objects may contain 3 types of fields: simple, relational, and functional. Simple types are integers, floats, booleans, strings, etc. Relational fields represent the relationships between objects (one2many, many2one, many2many). Functional fields are not stored in the database but calculated on-the-fly as Python functions. Common attributes supported by all fields (optional unless specified) • string : Field label (required) • required : True if mandatory • readonly : True if not editable • help : Help tooltip • select : 1 to include in search views and optimize for list filtering (with database index) business object name, in dot-notation (in module namespace) • context : Dictionary with contextual parameters (for relational fields)

6

Simple fields • boolean(...) integer(...) date(...) datetime(...) time(...) – ‘start_date’: fields.date(‘Start Date’) – ‘active’: fields.boolean(‘Active’) – ‘priority’: fields.integer(‘Priority’) • char(string,size,translate=False,..) text(string, translate=False,...) [Text-based fields] – translate: True if field values can be translated by users – size: maximum size for char fields (→41,45) • float(string, digits=None, ...) [Floating-point value with arbitrary precision and scale] – digits: tuple (precision, scale) (→58) . If digits is not provided, it’s a float, not a decimal type.

2.6 Special/Reserved field names A few field names are reserved for pre-defined behavior in OpenObject. Some of them are created automatically by the system, and in that case any field with that name will be ignored. id

unique system identifier for the object (created by ORM, do not add it)

name defines the value used by default to display the record in lists, etc. if missing, set _rec_name to specify another field to use for this purpose ...

...

Exercise 2 - Define a class Define a new class Course in the openacademy module.

2.7 Actions Actions are declared as regular records and can be triggered in 3 ways: 1. by clicking on menu items linked to a specific action 2. by clicking on buttons in views, if these are connected to actions 3. as contextual actions on an object Action declaration 1 2 3 4 5 6 7 8 9 10 11

action.name [list of 3-tuples (max 250 characters)] {context dictionary (max 250 characters)} object.model.name form|tree form,tree,calendar,graph new

7

Exercise 3 - Define new menu entries Define new menu entries to access courses and sessions under the OpenAcademy menu entry; one should be able to 1) display a list of all the courses and 2) create/modify new courses.

3 Building views: basics Exercise 1 - Customise a view through the view editor of the web interface Create a tree view for the Course object, displaying the name of the course and its description. Views form a hierarchy. Several views of the same type can be declared on the same object, and will be used depending on their priorities. By declaring an inherited view it is possible to add/remove features in a view.

3.1 Generic view declaration view.name object_name form # tree,form,calendar,search,graph,gantt

3.2 Forms Forms allow creation/edition or resources, and correspond to

elements. Form elements Common attributes for all elements : • string: label of the element • nolabel: 1 to hide the field label • colspan: number of column on which the field must span • rowspan: number of rows on which the field must span • col: number of column this element must allocate to its child elements • invisible: 1 to hide this element completely • eval: evaluate this Python code as element content (content is string by default) • attrs: Python map defining dynamic conditions on these attributes: readonly, invisible, required based on search tuples on other field values

8

Field

Automatic widgets depending on the corresponding field type. Attributes: • string: label of the field, also for search (overrides field name) • select: 1 to show the field in normal search, 2 for advanced only • nolabel: 1 to hide the field label • required: override required field attribute • readonly: override readonly field attribute • password: True to hide characters typed in this field • context: Python code declaring a context dictionary • domain: Python code declaring list of tuples for restricting values • on_change: Python method call to trigger when value is changed • completion: 1 to enable auto-completion of values when possible • groups: comma-separated list of group (id) allowed to see this field • widget: select alternative widget (one2many_list, many2many, url, email, image, float_time, reference, text_wiki, text_html, progressbar)

properties

dynamic widget showing all available properties (no attribute)

button

clickable widget associated with actions. Specific attributes: • type: type of button: workflow (default), object, or action • name: workflow signal, function name (without parentheses) or action to call (depending on type) • confirm: text of confirmation message when clicked • states: comma-separated list of states in which this button is shown • icon: optional icon (all GTK STOCK icons e.g. gtk-ok)

separator

horizontal separator line for structuring views, with optional label

newline

place-holder for completing the current line of the view

label

free-text caption or legend in the form

group

used to organise fields in groups with optional label (adds frame)

notebook, page

notebook elements are tab containers for page elements. Attributes: • name: label for the tab/page • position: tabs position in notebook (inside, top, bottom, left, right)

Exercise 2 - Customise tree and form views using XML Create your own tree and form views for the Course object. Data displayed should be: • In the tree view, the name of the course ; • In the form view, the name and the description of the course.

Exercise 3 - Notebooks In the Course form view, display the description under a tab, such that it will be easy to add other tabs later, containg additional information.

4 Objects Relations

9

Exercise 1 - Create classes Create Session and Attendee classes and add a menu item and an action to display the sessions.

4.1 Relational fields • Common attributes supported by relational fields – domain: optional restriction in the form of arguments for search (see search()) • many2one(obj, ondelete=’set null’,...) (→50) : Relationship towards a parent object (using a foreign key)

– obj: _name of destination object (required) – ondelete: deletion handling, e.g. ‘set null’, ‘cascade’, see PostgreSQL documentation • one2many(obj, field_id, ...) (→55) : Virtual relationship towards multiple objects (inverse of many2one)

– obj: _name of destination object (required) – field_id: field name of inverse many2one, i.e. corresponding foreign key (required) • many2many(obj, rel, field1, field2, ...) (→56) : Bidirectional multiple relationship between objects

– obj: _name of destination object (required) – rel: relationship table to use (required) – field1: name of field in rel table storing the id of the current object (required) – field2: name of field in rel table storing the id of the target object (required) Exercise 2 - Relations many2one, one2many Using ORM field types (one2many, many2one), modify the Course, Session and Attendee classes to reflect their relations with other objects, defined as follows:

10

Exercise 3 - Modify the views Modify the tree and form views for the Course object and create these views for the Session object. Data displayed should be, for the Course object: • In the tree view, the name of the course and the responsible for that course; • In the form view, the name and the responsible on the top, as well as the description of the course in one tab and and the related sessions in a second tab. For the Session object: • In the tree view, the name of the session and the related course; • In the form view, all the fields of the Session object. Since the amount of data to display is quite large, try to arrange the form views in such a way that information looks clear.

5 Inheritance 5.1 Inheritance mechanisms

Exercise 4 - Add an inheritance mechanism Add a “Partner” class which inherits of the existing “Partner” class.

Predefined osv.osv attributes for business objects _inherit

_name of the parent business object (for prototype inheritance)

_inherits

for multiple / instance inheritance mechanism: dictionary mapping the _name of the parent business objects to the names of the corresponding foreign key fields to use

11

5.2 View inheritance Existing views should be modifying through inherited views, never directly. An inherited view references its parent view using the inherit_id field, and may add or modify existing elements in the view by referencing them through XPath expressions, specifying the appropriate position. position

• inside: placed inside match (default) • before: placed before match

• replace: replace match • after: placed after match

Tip: XPath reference can be found at www.w3.org/TR/xpath id.category.list2 ir.ui.view

Exercise 1 - Add an inheritance mechanism Using class inheritance, create a “Partner” class which modifies the existing “Partner” class. Using views inheritance, modify the existing partners form view to display the new fields.

Exercise 2 - domain Add a mechanism allowing the Session form view to allow the user to choose the instructor only among the partners the “Instructor” field of which is set to “True”.

Exercise 3 - domain We now decide to create new categories among the partners: Teacher/Teacher Level 1 and Teacher/Teacher Level 2. Modify the domain defined in the previous exercise to allow the user to choose the instructor among the partners the “Instructor” field of which is set to “True” or those who are in one of the categories we defined.

6 ORM Methods 6.1 Functional fields function(fnct, arg=None, fnct_inv=None, fnct_inv_arg=None, type=’float’, fnct_search=None, obj=None, method=False, store=False, multi=False, ...) : Functional field simulating a real field, computed rather than stored • fnct [function to compute the field value (required)] – def fnct(self, cr, uid, ids, field_name, arg, context) returns a dictionary { ids→values } with values of type type

12

• fnct_inv [function used to write a value in the field instead] – def fnct_inv(obj, cr, uid, id, name, value, fnct_inv_arg, context) • type : type of simulated field (any other type besides ‘function’) • fnct_search [function used to search on this field] – def fnct_search(obj, cr, uid, obj, name, args) returns a list of tuples arguments for search(), e.g. [(‘id’,’in’,[1,3,5])] • obj : model _name of simulated field if it is a relational field • store, multi : optimization mechanisms (see usage in Performance Section) related(f1, f2, ..., type=’float’, ...) [Shortcut field equivalent to browsing chained fields] • f1,f2,... : chained fields to reach target (f1 required) (→51) • type : type of target field property(obj, type=’float’, view_load=None, group_name=None, ...) [Dynamic attribute with specific access rights] • obj : object (required) • type : type of equivalent field Exercise 1 - Functional fields Add a functional field to the “Session” class, that contains the percentage of remaining seats in a session. Display that percentage in the session tree and form views. One it is done, try to display it under the form of a progressbar.

Exercise 2 - Onchange methods Modify the Session form view and the Session class in such a way that the percentage of remaining seats refreshes whenever the number of available seats or the number of attendees changes, without having to save the modifications.

6.2 Predefined osv.osv attributes for business objects _constraints

list of tuples defining the Python constraints, in the form (func_name, message, fields).

_sql_constraints

list of tuples defining the SQL constraints, in the form (name, sql_def, message).

Exercise 3 - Add constraints Add a constraint which checks that the course description and the course title are not the same.

Exercise 4 - Add an sql constraint Add an sql constraint to check that a Course has a unique name.

13

Exercise 5 - Add a duplicate option Since we added a constraint for the Course name uniqueness, it is not possible to use the “duplicate” function anymore (Form > Duplicate). Re-implement your own “copy” method which allows to duplicate the Course object, changing the original name into “Copy of [original name]”.

Exercise 6 - Active objects – Default values Define the start_date default value as today. Add an active field in the Session class and set the session as active by default.

7 Advanced Views 7.1 List & Tree Lists include field elements, are created with type tree, and have a parent element. Attributes

Allowed elements

• colors: list of colors mapped to Python conditions • editable: top or bottom to allow in-place edit • toolbar: set to True to display the top level of object hierarchies as a side toolbar (example: the menu) field, group, separator, tree, button, filter, newline



Exercise 1 - List coloring Modify the Session tree view in such a way that sessions lasting less than 5 days are colored blue, and the ones lasting more than 15 days are colored red. Note: “duration” field Beware! If the “duration” field is not declared in the view, the client will not be aware of its existence. That would result in an error.

7.2 Calendars Views used to display date fields as calendar events ( parent). Attributes

Allowed elements

14

• • • • •

color: name of field for color segmentation date_start: name of field containing event start date/time day_length: length of a calendar day in hours (default: 8) date_stop: name of field containing event stop date/time OR date_delay: name of field containing event duration

field (to define the label for each calendar event)



Exercise 2 - Calendar view Add a Calendar view to the “Session” object enabling the user to view the events associated to the Open Academy.

7.3 Search views Search views are used to customize the search panel on top of list views, and are declared with the search type, and a top-level element. After defining a search view with a unique id, add it to the action opening the list view using the search_view_id field in its declaration. Allowed elements

field, group, separator, label, search, filter, newline, properties • filter elements allow defining button for domain filters • adding a context attribute to fields makes widgets that alter the search context (useful for context-sensitive fields, e.g. pricelist-dependent prices)

Exercise 3 - Search views Add a search view containing: 1) a field to search the courses based on their title and 2) a button to filter the courses of which the current user is the responsible. Make the latter selected by default.

7.4 Gantt Charts Bar chart typically used to show project schedule ( parent element). Attributes Allowed elements

same as field, level • level elements are used to define the Gantt chart levels, with the enclosed field used as label for that drill-down level



Exercise 4 - Gantt charts Add a Gantt Chart enabling the user to view the sessions scheduling linked to the Open Academy module. The sessions should be grouped by instructor.

7.5 (Charts) Graphs Views used to display statistical charts ( parent element).

15

Attributes

Allowed elements

• type: type of chart: bar, pie (default) • orientation: horizontal, vertical field, with specific behavior: • first field in view is X axis, 2nd one is Y, 3rd one is Z • 2 fields required, 3rd one is optional • group attribute defines the GROUP BY field (set to 1) • operator attribute sets the aggregation operator to use for other fields when one field is grouped (+,*,**,min,max)



Exercise 5 - Graph view Add a Graph view for the session object, that displays, for each course, the number of attendees under the fom of a bar chart.

8 Workflows Workflows are models associated to business objects describing the dynamics of the company. Workflows are also used to track processes that evolve over time. Exercise 1 - Static Workflow Create a state attribute which will be used for defining a workflow for the “Session” object. A session can have three states: Draft (default), Confirmed and Done. Add a (read-only) field to visualize the state, and buttons to change the state in the Session form. The valid transitions are: • Draft -> Confirmed • Confirmed -> Draft • Confirmed -> Done • Done -> Draft A sales order generates an invoice and a shipping order is an example of workflow used in Open ERP.

Workflows may be associated with any object in OpenERP, and are entirely customizable. Workflows are used to structure and manage the lifecycles of business objects and documents, and define transitions, triggers, etc. with

16

graphical tools. Workflows, activities (nodes or actions) and transitions (conditions) are declared as XML records, as usual. The tokens that navigate in workflows are called workitems. Exercise 2 - Dynamic workflow editor Using the workflow editor, create the same workflow as the one defined earlier for the Session object. Transform the Session form view such that the buttons change the state in the workflow. Note: Workflow “on create” A workflow associated to a session is created during the creation of that session. There is therefore no workflow instance associated to session instances created before the definition of the workflow.

Exercise 3 - Server actions Create server actions and modify the previous workflow in order to re-create the same behaviour as previously, but without using the Python methods of the Session class.

Exercise 4 - XML workflows Install the base_module_record module. Use it to export the workflow created in the workflow editor into an XML file, that you can incorporate in your module.

9 Security Access control mechanisms must be combined to achieve a coherent security policy.

9.1 Group-based access control mechanisms Groups are created as normal records on the res.groups model, and granted menu access via menu definitions. However even without a menu, objects may still be accessible indirectly, so actual object-level permissions (create,read,write,unlink) must be defined for groups. They are usually inserted via CSV files inside modules. It is also possible to restrict access to specific fields on a view or object using the field’s groups attribute. ir.model.access.csv "id","name","model_id:id","group_id:id","perm_read","perm_write","perm_create", "perm_unlink" "access_idea_idea","idea.idea","model_idea_idea","base.group_user",1,1,1,0 "access_idea_vote","idea.vote","model_idea_vote","base.group_user",1,1,1,0

Exercise 1 - Add access control through OpenERP interface Create a new user “John Smith”. Then create a group “OpenAcademy / SessionRead” with read access to the Session and Attendee objects.

Exercise 2 - Add access control through data files in your module Using a xml data file, create a “OpenAcademy / Manager” group, with no access rights defined yet (just create the empty group).

17

Exercise 3 - Add access control through data files in your module Use a CSV file to add read, write, creation and deletion rights on the Course, Session and Attendees objects to the OpenAcademy / Manager group. You can also create rights associated to no group, such as a read only access on Course and a read only access on Session.

10 Wizards 10.1 Wizard objects (osv_memory) Wizards describe stateful interactive sessions with the user through dynamic forms. Wizards make use of the osv_memory in-memory persistence to allow constructing wizards from regular business objects and views, without storing them in the database. In-memory objects are created by extending osv.osv_memory. Exercise 1 - Define the wizard class Define the create_attendee_wizard class and implement its structure.

10.2 Views Wizards use regular views and their buttons may use a special=”cancel” attribute to close the wizard window when clicked.

10.3 Wizard execution Such wizards are launched via regular action records, with a special target field used to open the wizard view in a new window. Exercise 2 - Make the wizard available through a menuitem Create a menuitem and the necessary action to use the wizard.

Exercise 3 - Customise the form view Customise the form view in order to show all the fields of the class.

Exercise 4 - Create methods Create the action_add_attendee method in the create_attendee_wizard class, and add a button in the form view to call it. Also add a “Cancel” button that closes the wizard window.

Exercise 5 - Add an onchange method Add an onchange method in order to display the list of existing attendees for a given session, once the session is selected.

18

Exercise 6 - Bind the wizard to the context bar Bind the wizard to the context bar of the session model.

Extra Exercise - Wizard on multiple records Make the wizard able to add attendees to several sessions at once.

11 Internationalization Each module can provide its own translations within the i18n directory, by having files named LANG.po where LANG is the locale code for the language, or the language and country combination when they differ (e.g. pt.po or pt_BR.po). Translations will be loaded automatically by OpenERP for all enabled languages. Developers always use English when creating a module, then export the module terms using OpenERP’s gettext POT export feature (Administration>Translations>Export a Translation File without specifying a language), to create the module template POT file, and then derive the translated PO files. Many IDE’s have plugins or modes for editing and merging PO/POT files. Tip: The GNU gettext format (Portable Object) used by OpenERP is integrated into LaunchPad, making it an online collaborative translation platform. |- idea/ |- i18n/ | - idea.pot | - fr.po | - pt_BR.po | (...)

# # # # #

The module directory Translation files Translation Template (exported from OpenERP) French translation Brazilian Portuguese translation

Tip: By default OpenERP’s POT export only extracts labels inside XML files or inside field definitions in Python code, but any Python string can be translated this way by surrounding it with the tools.translate._ method (e.g. _(‘Label’) )

Exercise 1 - Translate a module Choose a second language for your OpenERP installation. Translate your module using the facilities provided by OpenERP.

12 Reports Reports in OpenERP can be rendered in different ways: • Custom reports: those reports can be directly created via the client interface, no programming required. Those reports are represented by business objects (ir.report.custom) • High quality personalized reports using openreport: no programming required but you have to write 2 small XML files: – a template which indicates the data you plan to report – an XSL : RML stylesheet • Hard coded reports • OpenOffice Writer templates

19

There are several report engines in OpenERP, to produce reports from different sources and in many formats.

12.1 Expressions used in OpenERP report templates [[ ]]

double brackets content is evaluated as a Python expression based on the following expressions

Predefined expressions : • objects contains the list of records to print • data comes from the wizard launching the report • user contains the current user (as per browse()) • time gives access to Python time module • repeatIn(list,’var’,’tag’) repeats the current parent element named tag for each object in list, making the object available as var during each loop • setTag(‘tag1’,’tag2’) replaces the parent RML tag1 with tag2 • removeParentNode(‘tag’) removes parent RML element tag • formatLang(value, digits=2, date=False, date_time=False, grouping=True, monetary=False) can be used to format a date, time or amount according to the locale • setLang(‘lang_code’) sets the current language and locale for translations Exercise 1 - Install the OpenOffice plugin Install the report designer module and add the OpenOffice OpenERP plugin.

Exercise 2 - Create a new report Create a report for the Session object, displaying for each session its name, date, duration, percentage of completion, responsible name and list of attendees.

Exercise 3 - i18n Create a report for the Session object, displaying its name, date, duration, percentage of completion, responsible name and list of attendees.

Exercise 4 - RML Export the OpenOffice report to a RML file, add it to your module and add an action to the session object for printing the report.

20

13 WebServices The web-service module offer a common interface for all web-services : • SOAP • XML-RPC • NET-RPC Business objects can also be accessed via the distributed object mechanism. They can all be modified via the client interface with contextual views. OpenERP is accessible through XML-RPC interfaces, for which libraries exist in many languages.

13.1 Python example import xmlrpclib # ... define HOST, PORT, DB, USER, PASS url = ’http://%s:%d/xmlrpc/common’ % (HOST,PORT) sock = xmlrpclib.ServerProxy(url) uid = sock.login(DB,USER,PASS) print "Logged in as %s (uid:%d)" % (USER,uid) # Create a new idea url = ’http://%s:%d/xmlrpc/object’ % (HOST,PORT) sock = xmlrpclib.ServerProxy(url) args = { ’name’ : ’Another idea’, ’description’ : ’This is another idea of mine’, ’inventor_id’: uid, } idea_id = sock.execute(DB,uid,PASS,’idea.idea’,’create’,args)

Exercise 1 - Add a new service to the client Write a Python program able to send XML-RPC requests to a PC running OpenERP (yours, or your instructor’s). This program should be display all the existing sessions and the corresponding number of seats, and to create a new session for one of the courses. In this case, ask the server to create “Session” objects.

21