| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Bank statement lines need to be matched with entries; We have to automate this operation as much as possible.
At the same time, create an algorithm that fit everyone needs is quite impossible.
For that reason we will let users choose the rules they want with the improvement of reconciliation models.
Note that we did it only for bank statement reconliation, not for manual reconciliations.
Was task: 1877375
Was PR #26669
|
|
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
|
|
This allows to set up a mail alias per purchase journal. Then share that email address to your supplier, or use it internally to forward the vendor bills received by mail, to automatically create an empty vendor bill with the mail attachments linked, and the partner might be filled if the source email matches a supplier.
Thanks to the document preview on the side, it's now super easy and super fast to copy the vendor bill info from the received PDF into the account.invoice object. This would eventually be improved later on (IAP).
Was task: 37703
Was PR #22158
|
|
|
|
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.
|
|
Otherwise a constraint is raised because new line are added to the
payment term instead of recreating them from scratch. This constraint
blocks people from reinitializing the module, which is quite boring
when developing.
|
|
|
|
|
|
|
|
|
|
Otherwise, only the main company can make a full reconciliation
|
|
Sale Order --> Sales Order
Sale Report --> Sales Report
Sale Team -> Sales Team
Payment Term --> Payment Terms
|
|
|
|
|
|
71d16a369e01515aac988c62371d70549d3b5294
|
|
The payment sequence should depend on the company, which is not possible
with the harcoded reference to the sequence ids.
opw-670491
|
|
|
|
This is an oversight during the foward-port
57168a9e90066ed6b3d274d5032a20bef342a00f
of the revision
57168a9e90066ed6b3d274d5032a20bef342a00f
opw-652410
|
|
Major changes:
- No use of UoS anymore
- No analytic journal (journal_id) on account move lines
Reason: complete rewrite of the Sale module.
Responsible: fp, dbo, nim
|
|
|
|
tax_group retention for l10n_co
|
|
simple renaming, it also includes the following field removals:
- [REM] account_budget: removal of field 'validating _user_id' on account.crossovered.budget, which is now replaced by inheritance with mail.thread
- [REM] account_budget: removal of field 'code' of account.crossovered.budget, which was not used and redondant with its name
- [REM] account_asset: removal of field 'note' of account.asset.category, which was not used and redondant with its name
- [REM] account: removal of field 'to_check' of account.move, which was redondant with state == 'draft'
- [REM] account_voucher: removal of field 'audit' of account.voucher, which was a fields.related on move_id.to_check
|
|
|
|
invoices on the sales team.
|
|
ir.sequence.date_range, refactored ir.sequence and ir.sequence.date_range implementation
|
|
bzr revid: qdp-launchpad@openerp.com-20131230102802-y1ux8470wxnj4yfr
|
|
bzr revid: dle@openerp.com-20131210152957-hn0c3zvli62vhi0a
|
|
wrong fields in <record> creation
bzr revid: chs@openerp.com-20131031184321-2nqqpxowhg03wt4t
|
|
bzr revid: fp@tinyerp.com-20130630142927-juf7c4pa70lw7l6q
|
|
fields in account.payment.term.line model
bzr revid: qdp-launchpad@openerp.com-20130314145337-vriuhu2sozdeyu5a
|
|
avoid spamming contact partners.
bzr revid: tde@openerp.com-20130130090942-duiwfvtcj2d0ad6c
|
|
bzr revid: tde@openerp.com-20121219212330-xfx3lykstl1nsa8m
|
|
unnecessary chatter message.
bzr revid: tde@openerp.com-20121219130024-bmf584gyw5p8khrc
|
|
field. Modified tracked (old name) to track_visibility. Added description on subtypes of account.
bzr revid: tde@openerp.com-20121219121520-riwt9w52ntsa9dhm
|
|
bzr revid: fka@tinyerp.com-20121210045724-sk2hk8mmi8iahfwn
|
|
bzr revid: fp@tinyerp.com-20121208135723-ori198g559b1sxsu
|
|
bzr revid: atp@tinyerp.com-20121204130150-ng08xtg1mipt5590
|
|
bzr revid: atp@tinyerp.com-20121204062326-l0pexulus41zut59
|
|
Days end of Month,30% Advance, End 30 Days) and keep in demo
bzr revid: shp@tinyerp.com-20121203121900-fb52ryi5d2acolj8
|
|
about subtypes.
bzr revid: tde@openerp.com-20121203114009-obtca9gf3t7b909y
|
|
bzr revid: tde@openerp.com-20121203093454-lf21qlsuse1ve8ro
|
|
bzr revid: dle@openerp.com-20121122104504-ezgj2666zkhgybpj
|
|
bzr revid: apa@tinyerp.com-20121121093200-hx4pi4vvk54vgn1x
|
|
bzr revid: fka@tinyerp.com-20121120090657-2dhw9kew0425bjjj
|
|
bzr revid: tpa@tinyerp.com-20121019051438-gg0zk0wordvvi215
|
|
account.move.line which doesn't provide useful information most of the time)
bzr revid: qdp-launchpad@openerp.com-20121017094142-uxi6obk1byojzjm1
|
|
bzr revid: fp@openerp.com-20121002204023-8v3jf2n84xe2jol9
|
|
bzr revid: tde@openerp.com-20120919133540-e0d8huak2g3v915o
|
|
bzr revid: sgo@tinyerp.com-20120913062928-hvqnp116y49yrl4d
|
