.. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg
:target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
:alt: License: AGPL-3
==================
Partner Changesets
==================
This module extends the functionality of partners. It allows to create
changesets that must be validated when a partner is modified instead of direct
modifications. Rules allow to configure which field must be validated.
Configuration
=============
Access Rights
-------------
The changesets rules must be edited by users with the group ``Changesets
Configuration``. The changesets can be applied or canceled only by users
with the group ``Changesets Validations``
Changesets Rules
----------------
The changesets rules can be configured in ``Sales > Configuration >
Partner Changesets > Fields Rules``. For each partner field, an
action can be defined:
* Auto: the changes made on this field are always applied
* Validate: the changes made on this field must be manually confirmed by
a 'Changesets User' user
* Never: the changes made on this field are always refused
In any case, all the changes made by the users are always applied
directly on the users, but a 'validated' changeset is created for the
history.
The supported fields are:
* Char
* Text
* Date
* Datetime
* Integer
* Float
* Boolean
* Many2one
Rules can be global (no source model) or configured by source model.
Rules by source model have the priority. If a field is not configured
for the source model, it will use the global rule (if existing).
If a field has no rule, it is written to the partner without changeset.
Usage
=====
General case
------------
The first step is to create the changeset rules, once that done, writes on
partners will be created as changesets.
Finding changesets
------------------
A menu lists all the changesets in ``Sales > Configuration > Partner
Changesets > Changesets``.
However, it is more convenient to access them directly from the
partners. Pending changesets can be accessed directly from the top right
of the partners' view. A new filter on the partners shows the partners
having at least one pending changeset.
Handling changesets
-------------------
A changeset shows the list of the changes made on a partner. Some of the
changes may be 'Pending', some 'Accepted' or 'Rejected' according to the
changeset rules. The only changes that need an action from the user are
'Pending' changes. When a change is accepted, the value is written on
the user.
The changes view shows the name of the partner's field, the Origin value
and the New value alongside the state of the change. By clicking on the
change in some cases a more detailed view is displayed, for instance,
links for relations can be clicked on.
A button on a changeset allows to apply or reject all the changes at
once.
Custom source rules in your addon
---------------------------------
Addons wanting to create changeset with their own rules should pass the
following keys in the context when they write on the partner:
* ``__changeset_rules_source_model``: name of the model which asks for
the change
* ``__changeset_rules_source_id``: id of the record which asks for the
change
Also, they should extend the selection in
``ChangesetFieldRule._domain_source_models`` to add their model (the
same that is passed in ``__changeset_rules_source_model``).
The source is used for the application of the rules, allowing to have a
different rule for a different source. It is also stored on the changeset for
information.
Screenshot:
-----------
* Configuration of rules
.. image:: partner_changeset/static/src/img/rules.png
* Changeset waiting for validation
.. image:: partner_changeset/static/src/img/changeset.png
.. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas
:alt: Try me on Runbot
:target: https://runbot.odoo-community.org/runbot/134/9.0
Known issues / Roadmap
======================
* Only a subset of the type of fields is actually supported
Bug Tracker
===========
Bugs are tracked on `GitHub Issues
<https://github.com/OCA/partner-contact/issues>`_. In case of trouble, please
check there if your issue has already been reported. If you spotted it first,
help us smashing it by providing a detailed and welcomed `feedback
Credits
=======
Images
------
* Odoo Community Association: `Icon <https://github.com/OCA/maintainer-tools/blob/master/template/module/static/description/icon.svg>`_.
Contributors
------------
* Guewen Baconnier <guewen.baconnier@camptocamp.com>
* Denis Leemann <denis.leemann@camptocamp.com>
Maintainer
----------
.. image:: https://odoo-community.org/logo.png
:alt: Odoo Community Association
:target: https://odoo-community.org
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 https://odoo-community.org.
Raw data
{
"_id": null,
"home_page": "http://www.camptocamp.com",
"name": "odoo9-addon-partner-changeset",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "",
"author": "Camptocamp, Odoo Community Association (OCA)",
"author_email": "support@odoo-community.org",
"download_url": "",
"platform": "UNKNOWN",
"description": ".. image:: https://img.shields.io/badge/licence-AGPL--3-blue.svg\n :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html\n :alt: License: AGPL-3\n\n==================\nPartner Changesets\n==================\n\nThis module extends the functionality of partners. It allows to create\nchangesets that must be validated when a partner is modified instead of direct\nmodifications. Rules allow to configure which field must be validated.\n\nConfiguration\n=============\n\nAccess Rights\n-------------\n\nThe changesets rules must be edited by users with the group ``Changesets\nConfiguration``. The changesets can be applied or canceled only by users\nwith the group ``Changesets Validations``\n\nChangesets Rules\n----------------\n\nThe changesets rules can be configured in ``Sales > Configuration >\nPartner Changesets > Fields Rules``. For each partner field, an\naction can be defined:\n\n* Auto: the changes made on this field are always applied\n* Validate: the changes made on this field must be manually confirmed by\n a 'Changesets User' user\n* Never: the changes made on this field are always refused\n\nIn any case, all the changes made by the users are always applied\ndirectly on the users, but a 'validated' changeset is created for the\nhistory.\n\nThe supported fields are:\n\n* Char\n* Text\n* Date\n* Datetime\n* Integer\n* Float\n* Boolean\n* Many2one\n\nRules can be global (no source model) or configured by source model.\nRules by source model have the priority. If a field is not configured\nfor the source model, it will use the global rule (if existing).\n\nIf a field has no rule, it is written to the partner without changeset.\n\nUsage\n=====\n\nGeneral case\n------------\n\nThe first step is to create the changeset rules, once that done, writes on\npartners will be created as changesets.\n\nFinding changesets\n------------------\n\nA menu lists all the changesets in ``Sales > Configuration > Partner\nChangesets > Changesets``.\n\nHowever, it is more convenient to access them directly from the\npartners. Pending changesets can be accessed directly from the top right\nof the partners' view. A new filter on the partners shows the partners\nhaving at least one pending changeset.\n\nHandling changesets\n-------------------\n\nA changeset shows the list of the changes made on a partner. Some of the\nchanges may be 'Pending', some 'Accepted' or 'Rejected' according to the\nchangeset rules. The only changes that need an action from the user are\n'Pending' changes. When a change is accepted, the value is written on\nthe user.\n\nThe changes view shows the name of the partner's field, the Origin value\nand the New value alongside the state of the change. By clicking on the\nchange in some cases a more detailed view is displayed, for instance,\nlinks for relations can be clicked on.\n\nA button on a changeset allows to apply or reject all the changes at\nonce.\n\nCustom source rules in your addon\n---------------------------------\n\nAddons wanting to create changeset with their own rules should pass the\nfollowing keys in the context when they write on the partner:\n\n* ``__changeset_rules_source_model``: name of the model which asks for\n the change\n* ``__changeset_rules_source_id``: id of the record which asks for the\n change\n\nAlso, they should extend the selection in\n``ChangesetFieldRule._domain_source_models`` to add their model (the\nsame that is passed in ``__changeset_rules_source_model``).\n\nThe source is used for the application of the rules, allowing to have a\ndifferent rule for a different source. It is also stored on the changeset for\ninformation.\n\nScreenshot:\n-----------\n\n* Configuration of rules\n\n .. image:: partner_changeset/static/src/img/rules.png\n\n* Changeset waiting for validation\n\n .. image:: partner_changeset/static/src/img/changeset.png\n\n\n.. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas\n :alt: Try me on Runbot\n :target: https://runbot.odoo-community.org/runbot/134/9.0\n\nKnown issues / Roadmap\n======================\n\n* Only a subset of the type of fields is actually supported\n\nBug Tracker\n===========\n\nBugs are tracked on `GitHub Issues\n<https://github.com/OCA/partner-contact/issues>`_. In case of trouble, please\ncheck there if your issue has already been reported. If you spotted it first,\nhelp us smashing it by providing a detailed and welcomed `feedback\n\nCredits\n=======\n\nImages\n------\n\n* Odoo Community Association: `Icon <https://github.com/OCA/maintainer-tools/blob/master/template/module/static/description/icon.svg>`_.\n\nContributors\n------------\n\n* Guewen Baconnier <guewen.baconnier@camptocamp.com>\n* Denis Leemann <denis.leemann@camptocamp.com>\n\nMaintainer\n----------\n\n.. image:: https://odoo-community.org/logo.png\n :alt: Odoo Community Association\n :target: https://odoo-community.org\n\nThis module is maintained by the OCA.\n\nOCA, or the Odoo Community Association, is a nonprofit organization whose\nmission is to support the collaborative development of Odoo features and\npromote its widespread use.\n\nTo contribute to this module, please visit https://odoo-community.org.",
"bugtrack_url": null,
"license": "AGPL-3",
"summary": "Partner Changesets",
"version": "9.0.1.0.0",
"project_urls": {
"Homepage": "http://www.camptocamp.com"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "f914a8cf281751e1d05d887ed7aac5fb709edf664fb09f80cf1a3ebfa73f9ff6",
"md5": "c990a8f8650477deab53f6542a4c9074",
"sha256": "2c60e2cba0079761684fbe3750aa41ea74ac1df1de8bef46e15a36bea055398e"
},
"downloads": -1,
"filename": "odoo9_addon_partner_changeset-9.0.1.0.0-py2-none-any.whl",
"has_sig": false,
"md5_digest": "c990a8f8650477deab53f6542a4c9074",
"packagetype": "bdist_wheel",
"python_version": "py2",
"requires_python": null,
"size": 192763,
"upload_time": "2017-04-11T19:46:46",
"upload_time_iso_8601": "2017-04-11T19:46:46.367542Z",
"url": "https://files.pythonhosted.org/packages/f9/14/a8cf281751e1d05d887ed7aac5fb709edf664fb09f80cf1a3ebfa73f9ff6/odoo9_addon_partner_changeset-9.0.1.0.0-py2-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2017-04-11 19:46:46",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "odoo9-addon-partner-changeset"
}
JSON