Goffin Simon
0fd773a486
Unify and refactor exception handling in framework and addons. The generic `except_osv` is now deprecated, and replaced by more specialized exception subtypes: - `UserError` (renamed from Warning, as it conflicts with the built-in `Warning`) raised when a non-technical error occurs during a business operation. It could be a missing information in the data provided by the user, or a misconfiguration. - `AccessError`: raised when any operation is denied because the user conducting it does not have the required access rights. - `AccessDenied`: raised when an operation that requires authenticated access is attempted via an unauthenticated request. - `MissingError`: raised when an operation is attempted on a record that does not exist. - `ValidationError`: raised when an operation violates a SQL or Python constraint. - All other exceptions are internal errors due to a system problem or bug, and raised untouched to the client-side, which should display a traceback. All exceptions take a single message argument. The `test_exceptions` module has been updated to showcase both new and old (deprecated) exceptions. A great many old `except_osv` had a useless title with "Error!" or "Warning", those have been removed, as this is handled by the client-side widget that displays the messages. This commit introduces a more consistent policy for logging errors and warnings: - All messages that do not require administrator attention should be logged at INFO level or lower. This includes all errors that are notified to the user in a friendly manner, even for access right problems or validation errors during business operations. - All messages that indicate a likely misconfiguration or malicious use by the users should be logged at WARNING level, as they typically require administrator attention. - All other unhandled internal errors cannot typically be handled by the user and should be logged at ERROR or higher level, as they require immediate administrator attention.
Google Calendar
Get your meetings, yours holidays, ... Get your calendar anywhere and never forget an event, fully synchronized with the Odoo Open Source CRM.
Keep an eye on your events
See easily the purpose of the meeting, the start time and also the attendee(s)... All that without click on anything...
Create so easily an event
In just one click you can create an event... You can drag and drop your event if you want moved it to another timing. You can shrink or extend the event if you need to change the start's hours or the duration of your meeting.
Create recurrent event
You can also create recurrent events with only one event. You need to create an event each monday of the week ? With only one it's possible, you could specify the recurrence and if one of this event is moved, or deleted, it's not a problem, you can untie your event from the others recurrences.
See all events you wants
See in your calendar, the event from others peoples where your are attendee, but also their events by simply adding your favorites coworkers. Every coworker will have their own color in your calendar, and every attendee will have their avatar in the event...
Get an email
You will receive an email at creation of an event where you are attendee, but also when this event is updated for some fields as date start, ...
Be notified
You can ask to have a alarm of type 'notification' in your Odoo. You will have a notification in you Odoo which ever the page you are.
Google Calendar
With the plugin Google_calendar, you can synchronize your Odoo calendar with Google Calendar.