The document outlines a training course on Odoo Studio, focusing on its functionalities and features for creating custom applications without coding. It includes a comprehensive overview of database structures, use cases, and methods to implement and manage business needs through Odoo Studio. Key components also cover automation, access rights, and practical exercises for participants to enhance their understanding of the platform.

1. Odoo Studio
A functional approach
Ander Tur • Consultant
Luc Nailis • Consultant
EXPERIENCE
2018

2. First of all, we would like to
start with a minute of silence…

3. 0. Welcome
Getting to know us.
● Luc
● Ander

4. 0. Welcome
Getting to know you.
Who’s familiar with :
● Odoo ?
● Odoo Studio ?
● The technical structure behind Odoo ?

5. 0. Welcome
Getting to know you.
● Who are you ? http://pad.odoo.com/p/Studio-smart
● What do you expect from this course ?

6. 0. Welcome
About this training - WIIFY
● Goal :
○ Show the potential
○ Give a general comprehension >< Being exhaustive (and
exhausting !)
… To make sure you have the tools you’ll need

7. 0. Welcome
About this training - WIIFY
● Methodology
○ Brief explanation of the core functionalities
○ Learning by doing : Concrete use case(s) with your own Odoo
12 database

8. DAY #1 DAY #2
0. Welcome 6. Technical Concepts : Advanced
1. Introduction 7. Use Case : Advanced needs
2. Technical Concepts 8. Implementing with the
Standard : Expenses
3. Use Case : Context 9. Odoo Studio:
A prototyping tool
4. Studio Features : Basics 10. Q/A open session
5. Studio Features :
Intermediate 11. Conclusion

9. Introduction1

10. Elevator Pitch : Studio
● With vs Without Studio
● Test, Phase & Send to Production with only a few clicks

11. Warning !

12. A few words on PM
Introduction
● The “Quickstart” Methodology
● The “80/20” rule

13. Odoo Studio :
3 Pitfalls to avoid to make your project a success
● Reinventing the wheel
● Customization vs Development
● Not focusing on the added value & the Business Need

14. 1 - Reinventing the wheel
Take a loot at what exists…
… More than 45 apps & 400 modules...
… and no need to reinvent them !
Ex : Events & Expenses

15. The ‘Big Bang’
The ‘Creative’
1 - Two approaches,
Same problem

16. 2 - Customization vs Development
“If a picture is worth a thousand words, sometimes a
development is worth a thousand customizations !”

17. 3 - Not focusing on added-value
● Is the technical cost worth it ?
○ Cost : time, money, complexity
● Does it impact a lot of users ?
○ Role distribution

18. 3 - Not focusing on added-value
● Does it ease the onboarding ?
○ Replicating
● Does it impact your business ?
○ Think business not Odoo

19. Let’s get started !
Enter the below URL in your browser and create your own database.
https://www.odoo.com/start12
Install the apps Expenses, Inventory, Studio, Contacts.
NB : All databases will die after the OXP. Don’t forget to download your
module !

20. Technical Concepts :
Basic2

21. What is a database ?
See it as a dynamic Excel file
● Sheets are models
● Columns are fields
● Rows are records

22. Models
Each Odoo document is a model.
eg : invoice, a sale order, a customer.
But they can work together and have relationships through their fields

23. Fields
Fields are where the data is stored
Eg : Name, Address, Price, Weight, …
They have different types & features (ex : char, integer, html)

24. Relational fields
● M2O -> Many records pointing towards another
● O2M -> Does not exist “per se”, reverse search
Many2One & One2Many

25. Relational fields
● M2M : Many records pointing
towards many records… And vice
versa !
● O2O : Does not exist in Odoo, use
M2O instead
Many2Many & One2One

26. Views
● Views are the interface that allow us to see the data in different
ways
● Different views exist and are grouped in ‘families’ (screenshot from
Studio)
● A view is usually based on a single model (relation fields)

27. Views
Why do we have so many ?
● Different usages
○ Form views are used to create / edit complex records
○ List views usually to provide overviews / look for records
○ Kanban is to manage flows
○ Gantt is for forecasting
○ Pivot, grids, … are for reporting purposes.

28. Menus
● Menus allow to navigate through the differents views

29. Use case :
Animal rescue NGO3

30. Context
Animal Rescue - NGO
● Collect, Treat & Release wild animals
● Interact with Sponsors
● Multiple users with different roles & responsibilities

31. Functional needs
The President decided to use Odoo to :
● Get a clearer overview of the animals at the center (>< spreadsheet)
● Assign & Manage Staff
● Centralize the information in a database accessible worldwide

32. Functional needs
After some analysis, you find out that no App or module exist to
manage those flows…

33. Or is it...?

34. Studio Features &
usage : Basics4

35. Create your own app
Create a custom application
● Choose a name
● Upload/Choose a logo

36. More on that topic ?
Odoo Studio: Build an App from
Scratch with Zero Coding
Experience
William Nolis, Business Analyst

37. Create your own app
2. Create a custom model
● Create your first object : Animal
● A few fields are automatically generated
● You’re brought to a basic form view
● The name field as been created for you (=/= ID)

38. The users needs to be able to :
● Add a nickname
● Add a medium image
● Add the birth-date
● Take notes describing the animal character in a few lines
Note: remember to modify the name of the field straight away so that
you have a nice back-end name.
Create your own app
2. Let’s create fields on that model. (Basic fields)

39. Create your own app
2. Let’s create fields on that model. (Basic fields)
The users needs to be able to :
● Add a gender
● Add its weight
● Add the exact moment (Time & Date) the animal arrived *
* Fields can have widgets which display information in different ways

40. Create your own app
2. Let’s create fields on that model. (Intermediate)
The users need to be able to :
● Upload a PDF copy of the animal passport (check available widgets)
● Say whether or not it has been vaccinated
● Allow users to say whether the animal is carnivore/herbivore
NB : Other options could come later !

41. Create your own app
2. Let’s create fields on that model. (Intermediate)
The users needs to be able to :
● Add countries where the animal could be released
● Allow users to write the feeding time (hour not day !)
● Add a location for the animal (link to inventory locations)
● Add the notion of a “flow” (Not received/At the center/Released).

42. Create your own app
2. Let’s create fields on that model. (Advanced)
Add the Employee app and create a few employees
There are three kinds of employees :
● Veterinarians
● Trucker Drivers
● Administratives

43. Create your own app
2. Let’s create fields on that model. (Advanced)
Go back to the animal form view
● Add a field that allows to note who is the vet in charge of that
animal (hint : you’ve just created employees).
● Have Odoo display the phone number of that employee on the
animal form view.

44. Create your own app
2. Let’s create fields on another model. (Final)
Add the Contact module and create a few “Partners”
A Partner can sponsor an animal. Whether or not a contact is a sponsor
should be displayed on his page (True or False)

45. Create your own app
2. Let’s create fields on another model. (Final)
Go back to the animal form view.
Add a new field to display the animal sponsor. This list should ONLY
show sponsors, not all contacts !
NB : Users should not be able to create new partners from there !

46. GOOD JOB, you already have created a
database tailored on the first explained
needs.
… Let’s keep going !

47. Studio Features &
usage : Intermediate5

48. Let’s communicate !
With a click, add the chatter widget
Messages are external Notes are internal Followers are both

49. Attributes
Let’s make the form view dynamic ! (1/2)
Invisibility :
● Display the “Phone N°” only if there is a Vet assigned
● If the animal is on the Stage “Released” display a “Where” field
(M2O Country)
Mandatory :
● Users shouldn’t be able to create/save if the field “Gender” is not
defined

50. Attributes
Let’s make the form view dynamic ! (2/2)
Domains :
● Animals can never be released in Belgium (Way too cold!)
Default values :
● By default when creating an animal, it should not be set as
“Vaccinated”

51. Adding other views
Kanban - first displayed when clicking on the icon
Here are the informations we need to get at a glance :
● Name & Nickname
● Picture
● Race
● Vet’ in charge
● Stage

52. Adding other views
Tree (List)
The list should provide a clear overview of the :
● Name
● Race
● Gender
● Birthdate
● Sponsor
And allow to sort on all those values !

53. Adding other views
Search view (1/2) - The Bar
Add on “Auto-Completion“ the below fields
● Name
● Nickname
● Race
● Countries

54. Adding other views
Search view (2/2) - Group-by
Allow users to easily regroup animals based on those fields :
● Stage
● Race
● Gender
● Sponsor

55. Creating Menus
Making navigation in the App easy
● One for the Animals
● One for the Employees inside the App (add their functions in the
list view)
● One for the Sponsors (not contacts !) inside the App

56. The icing on the cake
Impress your manager !
● Add a custom background
● Populate the database
-> Download & Import the CSV file
● Add a dashboard view

57. Wrap up of DAY 1
As promised, not a single line of code !

58. Welcome to DAY 2
Thank you for coming back !

59. Recap of Day #1

60. Feedback from day 1:
Filters
Context on view through Studio
Computed fields

61. Technical Concepts :
Advanced6

62. Technical Concepts : Advanced
concepts
● Automations (Server actions, Automated actions)
● Reports
● Access Rights & Record rules

63. Automation
● Is the possibility to trigger actions automatically
Odoo needs 5 main elements :
1. A model
2. A trigger
3. A domain
4. An action
5. A last element, depending on the action (email, …)

64. Reports
● ‘Report’ is a generic term we use in Odoo for all Qweb documents
● An HTML page is generated and then printed into a PDF
● They can be customized with Studio to better fit your needs

65. Access rights VS Record rules
● Access rights : what can the user do with this object ?
● Record rules : which records of that object can the user access ?
➔ Both can work in parallel

66. Access rights
As a user of the group “Own Documents”, I can read but nothing else.
The manager however, can do all 4 operations.
➔ Can be done with Studio through the dedicated menu

67. Record rules
Record rules give more flexibility as they can be based on values stored on
the data tables
Ex : [('user_id', '=', user.id)] (Expense)
➔ Need some technical knowledge and is not done through Studio
(Domains)

68. Use Case : Advanced
needs7

69. New advanced fields
Animal Hierarchy
● Add a check-box : Is an ‘Alpha’ ? (False by default)
● If FALSE, display a field in which we can choose its ‘Alpha’ (Only
the ones that are alphas can be chosen)
● If TRUE, display all animals of the group that have this animal as
the ‘Alpha’ BUT do not let users add animals to that list, it should
not be editable

70. New advanced fields
● Form view : Add a clickable URL linking to a website
● Form view : Allow users to copy/paste the description with a click
● Form view : Show who created the Animal (field should be filled on
creation)
● Kanban view : Find a way to let users easily prioritize animals

71. Automation
A smoothless flow through Odoo Studio
● When an animal is sent to the stage “Released”, automatically
create an activity assigned to an employee of your choice so that
he will write a Tweet about it
● When a new animal is created, assign an activity “Medical
Inspection” to the user “Chief Vet” (you’ll have to create him)

72. Automation
Combining conditions & updates
● When an animal is vaccinated, if there is a Vet’s assigned to it,
send him an email to keep him informed

73. Report Editor
Potential sponsors like to visit the center and to keep a summary of
each animal they are interested in
➔ Let’s create a printable “Identity card” for the animal

74. Want to know more ?
What's New in Odoo Studio: Report
Editor, Moving Fields, etc.
Vincent Schippefilt, Developer

75. Access rights & groups
● Let’s define two levels of operations
-> Employees can read / create / write
-> The Admin can read / create / write / delete

76. Access rights & groups
Create a new group called “Sponsor manager”
-> This group should be the only one to see the ‘Sponsor’ button

77. Perfect the list view
To avoid displaying too much information at once, only display animals
per batch of 25 in the list view

78. Your turn !
Based on the flows and fields we’ve created, what kind of other field or
automation can you think about ?

79. Implementing with the
Standard : Expenses8

80. Expense part 1
Animal Rescue - NGO has limited resources and needs to have a way to
control expenses. To do so we must adapt the expense app to their
specific needs:
● Hide irrelevant fields (for example, sales is not used in this DB)
● Link each expense with an animal and bring its location,
veterinary, id and any other relevant information
● Link the expense with the potential related contact/s
● Adapt the search view

81. Expense part 2
● By default kanban view grouped by status
● Adapt search view
● Adapt access right, everyone can see every expense but only edit
their own

82. Expense reports
● Adapt expense report lines with the additional relevant fields
● Add a field so that the report can be linked to a location
● Update the respective pdf report (expense location, and expense
lines)
● Be creative!

83. Odoo Studio:
A prototyping tool9

84. Pm’s & Salesman best friend
● Create a POC / MVP
● Prepare demos on the go
● Brainstorm with a concrete support
● Test, Phase & Send to Production with only a few clicks

85. Want to know more ?
Studio as a Prototyping Tool
Antoine Mathot - Business Analyst

86. Q/A open session10

87. Your turn !

88. Conclusion11

89. Thank you.
#odooexperience
EXPERIENCE
2018