-
12 |
${object.ics_url_field}
16 | ]]> 17 |
10 |
23 | Import (currently only one) ICS into schedule and calendar
11 |
12 |
22 |
13 |
14 |
21 |
15 | ICS URL
16 |
20 |
17 |
19 | "), 33 | 'partner_id': customer_id, 34 | 'access_token': event.access_token, 35 | 'start': event.start, 36 | 'stop': event.stop, 37 | } 38 | 39 | request.env['project.task'].sudo().create(data) 40 | 41 | -------------------------------------------------------------------------------- /website_calendar_waitlist/models/calendar_booking.py: -------------------------------------------------------------------------------- 1 | import logging 2 | 3 | from odoo import api, fields, models, _ 4 | 5 | 6 | _logger = logging.getLogger(__name__) 7 | 8 | 9 | class Waitlist(models.Model): 10 | _name = "calendar.booking.type.waitlist" 11 | _description = "Waitlist for calendar types" 12 | 13 | related_user_id = fields.Many2one( 14 | "res.users", 15 | string="User", 16 | required=True, 17 | ) 18 | 19 | related_booking_type_id = fields.Many2one( 20 | "calendar.booking.type", 21 | required=True, 22 | ) 23 | 24 | current_position = fields.Integer( 25 | compute="_compute_position", 26 | store=True, 27 | default=-10, 28 | ) 29 | 30 | employee_id = fields.Many2one( 31 | "hr.employee", 32 | string="Employee", 33 | ) 34 | 35 | @api.depends("related_booking_type_id", "related_booking_type_id.related_wait_list_ids") 36 | def _compute_position(self): 37 | for record in self: 38 | for i, row in enumerate(record.related_booking_type_id.related_wait_list_ids, 1): 39 | if row.id == record.id: 40 | record.current_position = i 41 | break 42 | else: 43 | record.current_position = -10 44 | 45 | class CalendarBookingType(models.Model): 46 | _inherit = "calendar.booking.type" 47 | 48 | related_wait_list_ids = fields.One2many( 49 | "calendar.booking.type.waitlist", 50 | "related_booking_type_id", 51 | string="Waitlist", 52 | ) 53 | -------------------------------------------------------------------------------- /website_calendar_ce/static/src/js/website_calendar.editor.js: -------------------------------------------------------------------------------- 1 | odoo.define('website_calendar_ce.editor', function (require) { 2 | 'use strict'; 3 | 4 | var core = require('web.core'); 5 | var wUtils = require('website.utils'); 6 | var WebsiteNewMenu = require('website.newMenu'); 7 | 8 | var _t = core._t; 9 | 10 | WebsiteNewMenu.include({ 11 | actions: _.extend({}, WebsiteNewMenu.prototype.actions || {}, { 12 | new_booking: '_createNewBooking', 13 | }), 14 | 15 | //-------------------------------------------------------------------------- 16 | // Actions 17 | //-------------------------------------------------------------------------- 18 | 19 | /** 20 | * Asks the user information about a new booking type to create, 21 | * then creates it and redirects the user to this new booking type. 22 | * 23 | * @private 24 | * @returns {Promise} Unresolved if there is a redirection 25 | */ 26 | _createNewBooking: function () { 27 | var self = this; 28 | return wUtils.prompt({ 29 | window_title: _t("New Booking Type"), 30 | input: _t("Name"), 31 | }).then(function (result) { 32 | var name = result.val; 33 | if (!name) { 34 | return; 35 | } 36 | return self._rpc({ 37 | model: 'calendar.booking.type', 38 | method: 'create_and_get_website_url', 39 | args: [[]], 40 | kwargs: { 41 | name: name, 42 | }, 43 | }).then(function (url) { 44 | window.location.href = url; 45 | return new Promise(function () {}); 46 | }); 47 | }); 48 | }, 49 | }); 50 | 51 | }); 52 | -------------------------------------------------------------------------------- /calendar_resource_booking/models/calendar_event.py: -------------------------------------------------------------------------------- 1 | # -*- coding: utf-8 -*- 2 | from odoo import models, fields, api 3 | import logging 4 | from datetime import date, datetime 5 | 6 | _logger = logging.getLogger(__name__) 7 | 8 | class CalendarEventModify(models.Model): 9 | _inherit = "calendar.event" 10 | 11 | resource_ids = fields.Many2many(comodel_name='resource.resource',string='Resource',domain="[('resource_type','=','material')]") # relation|column1|column2 12 | resource_status = fields.Char(readonly=True) 13 | resource_status = fields.Char(readonly=True,compute='onchange_resource') 14 | 15 | 16 | @api.depends("resource_ids") 17 | def onchange_resource(self): 18 | 19 | def overlap(self, other): 20 | if other.start < self.start < other.stop: 21 | return False 22 | elif other.start < self.stop < other.stop: 23 | return False 24 | elif self.start < other.start < self.stop: 25 | return False 26 | elif self.start < other.stop < self.stop: 27 | return False 28 | return True 29 | 30 | calendars = self.env['calendar.event'].search( 31 | [ 32 | ('stop_date','<=',self.start_date), 33 | ('start_date','>=',self.start_date), 34 | 35 | ] 36 | ) 37 | _logger.warning(calendars) 38 | self.resource_status='' 39 | for c in calendars: 40 | if overlap(self,c): 41 | for r in self.resource_ids: 42 | if c.create_date < self.create_date: 43 | self.resource_status = _('%s are already booked by %s') % (r.name,c.name) 44 | else: 45 | self.resource_status = _('%s tries to book %s') % (c.name,r.name) 46 | 47 | -------------------------------------------------------------------------------- /website_calendar_waitlist/views/project_portal_templates.xml: -------------------------------------------------------------------------------- 1 |
21 | There are no waitlists.
22 |
23 |
21 | There are no bookings.
22 |
23 |
6 |
27 |
28 |
34 |
35 |
46 |
36 |
37 |
44 |
45 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 | 
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
3 |
19 | Calendar for Odoo
4 |Keep track of time
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
18 | 12 | Schedule bookings with clients. 13 |
14 |15 | Record-keeping 16 |
17 |
23 |
59 | Odoo Calendar -- keep track of time!
24 |
25 |
57 |
58 |
26 | Glabels uses a template for the label design and are using a special
27 | notation, ${name}, for including fields from the database. When you
28 | design your labels use a dummy csv-file for your model you want
29 | to tie the report to and the format
"Text: coma separated Values
30 | (CSV) with keys on line 1".
When the template is ready you can
31 | upload it to the report-record (or include it in the xml-record if
32 | you are building a module). There is a test report action that
33 | also lists all fields for the choosen model.
34 |
Example of code for a module:
36 |37 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 38 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 39 | 40 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 41 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 42 | </record> 43 | 44 |45 | 46 |
47 | This module needs Glabel to be installed on the server (for Ubuntu:
48 | sudo apt install glabels)
49 |
50 | You can test your template (and installation) using glabels-batch-command:
51 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
52 | This command are alike both on workstation and server.
53 |
54 |
5 |
16 |
6 |
7 |
9 |
10 |
12 | Current place is
13 |
14 |
15 | Registered to waitlist
8 |Already in waitlist
11 |
22 |
26 |
23 |
25 | Can't use this service without logging in.
24 |
13 |
45 |
46 |
47 | Thank you, 48 | % if object.user_id.signature: 49 |
50 | ${object.user_id.signature | safe} 51 | % endif 52 |
53 |
14 | Hello ${ctx.get('partner_id').name},
15 |
16 | You have a new booking.
17 |
|
20 | Details of the event 21 |
26 | % endif 27 | % if object.description : 28 | 29 | % endif 30 | % if not object.allday and object.duration 31 | 32 | % endif 33 | |
44 |
47 | Thank you, 48 | % if object.user_id.signature: 49 |
50 | ${object.user_id.signature | safe} 51 | % endif 52 |
8 |
9 |
15 |
47 |
16 |
30 |
46 | 31 | Boka ett Tillfälle 32 |
33 | 34 |
35 |
45 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
3 |
22 | Record-keeping for Odoo
4 |Keep all documents in one place
5 |
6 |
10 |
7 |
8 |
9 |
8 |
11 |
21 | 12 | A diary is a register of an organization, where incoming, outgoing and prepared documents are 13 | registered. The purpose of diaries in the public sector is to create transparency according to the 14 | principle of openness. Record keeping in Sweden is regulated, among other things, by the Public Access 15 | to Information and Secrecy Act (SFS 2009: 400), which entered into force on 30 June 2009. 16 |
17 |18 | Record-keeping 19 |
20 |
26 |
62 | Design labels using notation
27 |
28 |
60 |
61 |
29 | Glabels uses a template for the label design and are using a special
30 | notation, ${name}, for including fields from the database. When you
31 | design your labels use a dummy csv-file for your model you want
32 | to tie the report to and the format
"Text: coma separated Values
33 | (CSV) with keys on line 1".
When the template is ready you can
34 | upload it to the report-record (or include it in the xml-record if
35 | you are building a module). There is a test report action that
36 | also lists all fields for the choosen model.
37 |
Example of code for a module:
39 |40 | <report string="Sample Glabels" id="action_glabels_sample_report" model="res.partner" 41 | report_type="glabels" name="report_glabels.glabels_sample_report" /> 42 | 43 | <record id="action_glabels_sample_report" model="ir.actions.report.xml"> 44 | <field name="glabels_template" type="base64" file="report_glabels/sample.glabels" /> 45 | </record> 46 | 47 |48 | 49 |
50 | This module needs Glabel to be installed on the server (for Ubuntu:
51 | sudo apt install glabels)
52 |
53 | You can test your template (and installation) using glabels-batch-command:
54 | glabels-3-batch -o <out-file> -l -C -i <csv-file> <your template.glabels>
55 | This command are alike both on workstation and server.
56 |
57 |
10 |
11 |
12 |
13 |
14 |
19 |
32 |
33 |
40 |
34 |
35 |
37 |
38 |
39 | 47 | on to 48 |
49 |