Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

License: AGPL-3

Calendar Resource

This module adds new features to facilitate resource management with meetings:

  • To attach resources to a meeting, go to Calendar => Click on a meeting => Edit => Edit => add any related resources.

  • To edit or add a resource, go to Calendar => Resources => Resources.

  • This module can also prevent resources from being double-booked. Go to a resource and disable or enable Allow Double Booking (this is disabled by default). As a note, the same resource in a meeting that ends at 5pm and in a meeting that starts at 5pm on the same day would not not be considered double-booked.

  • You can restrict resources to certain calendar types. In the Resources form view, edit the Event Types field. The resource can then be added to events only of those types.

  • Resources cannot be added to events when they’re not available, either because they’re on leave or because the event time is outside their working time.

  • If you have an event selected as allday, only if there are no working times available on 1 or more of the days in that event will an error be raised. For example, if you set an event to allday on a Saturday and there are no working times at all that Saturday for a particular resource, then an error will be raised. However, if there is at least 1 working time interval for that resource on the Saturday, regardless of how long or short that working time is, the day will be considered covered by that working time. If the event is not allday, any time the resource is not available during the event, regardless of the time of day, will cause an error to be raised.

  • To stop leaves and working time validations on a resource when adding to an event, set the resource’s Working Time field to blank in the resource form view.

Usage

Try me on Runbot

Roadmap

  • Abstract out logic from _check_resource_ids_working_times into separate methods in resource.calendar.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smash it by providing detailed and welcomed feedback.

Credits

Images

  • Odoo Community Association: Icon.

Contributors

Maintainer

Odoo Community Association

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit http://odoo-community.org.

Metadata

Release files for odoo10-addon-calendar-resource 10.0.1.1.0.99.dev13

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo10-addon-calendar-resource 10.0.1.1.0.99.dev13
File Interpreter ABI Platform Actions
odoo10_addon_calendar_resource-10.0.1.1.0.99.dev13-py2-none-any.whl Python 2 none any Details for odoo10_addon_calendar_resource-10.0.1.1.0.99.dev13-py2-none-any.whl

Release files / odoo10_addon_calendar_resource-10.0.1.1.0.99.dev13-py2-none-any.whl

Download URL odoo10_addon_calendar_resource-10.0.1.1.0.99.dev13-py2-none-any.whl
Size 110.3 kB
Tags Python 2
SHA-256 checksum
How to use checksums
49fc3bf8ea13508263f3f512c1dd0b50703e99dc330f1361ca69524ca6935691
BLAKE2b-256 checksum
How to use checksums
eb61658e79b536f9aecc674a5085b62d495319250f694ad80a1d786114f67469
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.1 CPython/3.8.10

Security for odoo10-addon-calendar-resource 10.0.1.1.0.99.dev13

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page