summaryrefslogtreecommitdiff
path: root/addons/purchase/data/purchase_data.xml
AgeCommit message (Collapse)Author
2020-06-09[IMP] purchase: Improve reminder mail usabilityFabien Pinckaers
Some change to imporve reminder mail usability: 1. Scheduled date on POL of the PO form now is always editable. 2. Improve tooltip for the reminder email 3. don't show number of days when reminder email not checked on both PO and partner form. 4. only show "confirm receipt date" button in debug model 5. In the mail, format date by partner.lang 6. Add button to send preview reminder mail 7. On default, receipt_reminder_email on res.partner is False 8. merge expected_date with date_planned (done by FP) Task 2265912 PR #52693
2020-05-27[IMP] purchase: send reminder mail to vendoryhu-odoo
1. automatically send a reminder mail to vendor to confirm the receipt date. If confirmed, (confirmed by vendor) will be added next to the receipt date. If not, vendor can update the date on the portal website. An warning activity will be set for the purchase representative for this update. 2. Vendor can also comfirm recieption of the PO when we 'send PO by mail'. If confirm, (confirmed by vendor) will be added next to the confirmation date. An filter is added in the PO search view to show all unconfirmed PO. Task 2230811 PR #49921 Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>
2019-08-06[IMP] purchase: improve usability (back2basics)Kevin Baptiste
TaskID: 2040826 closes odoo/odoo#35394 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
2019-07-10[IMP] purchase: set the action menu 'Share' only for form viewHiral Bhavsar
For the model 'purchase.order', set the action menu 'Share' only for the form view. Linked to task 1984526 Related to PR #33720
2018-08-03[IMP] Portal - Share link : Easily share the url of a documentMitali Patel
Purpose ======= - Quickly share the url to someone else (a client, a colleague,...) - Ensure that the recipient can access at least the portal view of the shared record. - Typically used when a client cannot retrieve the mail to access his order. The share link can be used in this case. Specifications ============== For any object inheriting form portal.mixin: - Add a button SHARE (not visible in edit mode) - When clicking on this button, a popup opens with : - A warning message for tasks and projects only (see below) - the link (like in gmail) that can be copied - Recipients - mail composer (with preselected template) ==> see below - button [Send Link] [Copy Link] Discard - After sharing document, put internal note like "Document shared to xyz,...." with template message - Anyone with the link, even anonymous user (not logged in) can have access to the document with the access token provided in the url. Impacted models: - account.invoice (Community) - project.project (Community) - project.task (Community) - purchase.order (Community) - sale.order (Community) - helpdesk.ticket (Enterprise) Warning messages and access rules: Allowed : - SO canceled or draft will be accessible with the link with access_token - If the customer account is B2B (signup not enabled), the recipient will anyway see the document as the user specifically wants the recipient to see the document. Restrictions : - For Project and Task, if the privacy is not public, then, there is a contradiction between the access_token mechanism and the privacy of the document. - A warning message will be displayed in the share wizard to inform the user if the document cannot be visible by the recipients and to ask him to set the privacy to 'Visible by following customer'. The send button will, in that case, be hidden. - To avoid to block the share for a new project, default privacy value is now set to 'Visible by followong customer' Technical implementation ======================== - Move the access_token mechanism (field + methods + mail controller) to the portal.mixin to be able to use it in a generic way for each object inheriting the portal.mixin - Generalise a part of the _*model*_get_page_view_values method into a single one in portal - Generalize the _*model*_check_access into the portal controller of the portal module - Remove the init_column + default value for the access_token > old records have an access_token, > new one won't but it will be generated on demand via the get_access_token Done for performance reasons - Add share button into action menu separately. + kanban view context menu (except for task and project where button not in action menu but 'simple' button for task and project because other modules already provide action to send documents by email, which is not the case for project and task.) - Add a sign_token used to authentify the recipient in the portal view chatter, if any. The message will be posted as if the user was logged in. - Set the _get_share_url as private for security reason - Add a redirect parameter to _get_share_url to get If false : The direct portal view url If True : The redirect url (mail/view/?) - Cleaning up unnecessary code - Bug fix : - Before, if user was not logged and record had partner_id, if partner id was null, post message was done as admin. Now, the post message is done as public user. - If the user had an uid but had no access_token, he could be able to gain the access token of the record. check_access_rights was missing in the get_access_action. Task ID : 30985 Closes #25629
2018-05-23[MOV] purchase_stock: move code from purchasejem-odoo
We want to break the dependency between stock and purchase for our furtur developpement. For more modularity, a new bridge module 'purchase_stock' is created. This commti move part of business code, views, data, ... related to stock management from purchase into purchase_stock without changing any feature. Task #47927
2017-11-16[IMP] purchase: Convert yml files to python and xmlPragnesh Mistry
2017-11-02[MERGE] forward port branch 11.0 up to ee2b9fae351Christophe Simonis
2017-10-30[FIX] stock, mrp, stock_dropshipping: location access rightamoyaux
Use case to reproduce the bug: - Enable multi company and create a second one. - Add both company to another user and give him stock manager rights - Login on the second user and select as active the created company - Go to product and create one -> access right error on stock.location.route message. It happens because the routes 'buy' is selected by default. However the route buy when created use the default company although it's generic for all companies. This commit change the data in order to remove the company on routes buy, mto, manufacture and drop_shipping. Since this commit was released after v11 release, it could happens that already created database still have the problem thus the solution is to remove manually the company on the routes quoted above. opw-777718
2017-10-19[REM] base, various: remove res.request.linkThibault Delavallée
Not used since a while, remaining of old res.request. Requests have been removed at 881a76dbcf47c877feb5efa14943010309d22eaf . Links have been kept because still used in some reference fields. It seems the last use was in OpenERP v9.0 in crm_claim module. As links are not used since a while let us get rid of it.
2017-01-07[IMP] *: remove #general messages at module installationFabien Pinckaers
2016-08-05[MIG] purchase: Migrate to new APIDenis Vermylen (dve)
2016-08-05[MOV] purchase/data: add purchase_sequence to dataDenis Vermylen (dve)
2016-08-05[MOV] purchase: move and rename files according to guidelinesDenis Vermylen (dve)