Search 1.9 billion lines of Odoo code on GitHub
partner_changeset
<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg">
</a>
<a name="partner-changesets"></a>
<h2>Partner Changesets</h2>
<p>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.</p>
<a name="configuration"></a>
<h3>Configuration</h3>
<a name="access-rights"></a>
<h4>Access Rights</h4>
<p>The changesets rules must be edited by users with the group <code>Changesets
Configuration</code>. The changesets can be applied or canceled only by users
with the group <code>Changesets Validations</code></p>
<a name="changesets-rules"></a>
<h4>Changesets Rules</h4>
<p>The changesets rules can be configured in <code>Sales > Configuration >
Partner Changesets > Fields Rules</code>. For each partner field, an
action can be defined:</p>
<ul class="simple">
<li>Auto: the changes made on this field are always applied</li>
<li>Validate: the changes made on this field must be manually confirmed by
a 'Changesets User' user</li>
<li>Never: the changes made on this field are always refused</li>
</ul>
<p>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.</p>
<p>The supported fields are:</p>
<ul class="simple">
<li>Char</li>
<li>Text</li>
<li>Date</li>
<li>Datetime</li>
<li>Integer</li>
<li>Float</li>
<li>Boolean</li>
<li>Many2one</li>
</ul>
<p>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).</p>
<p>If a field has no rule, it is written to the partner without changeset.</p>
<a name="usage"></a>
<h3>Usage</h3>
<a name="general-case"></a>
<h4>General case</h4>
<p>The first step is to create the changeset rules, once that done, writes on
partners will be created as changesets.</p>
<a name="finding-changesets"></a>
<h4>Finding changesets</h4>
<p>A menu lists all the changesets in <code>Sales > Configuration > Partner
Changesets > Changesets</code>.</p>
<p>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.</p>
<a name="handling-changesets"></a>
<h4>Handling changesets</h4>
<p>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.</p>
<p>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.</p>
<p>A button on a changeset allows to apply or reject all the changes at
once.</p>
<a name="custom-source-rules-in-your-addon"></a>
<h4>Custom source rules in your addon</h4>
<p>Addons wanting to create changeset with their own rules should pass the
following keys in the context when they write on the partner:</p>
<ul class="simple">
<li><code>__changeset_rules_source_model</code>: name of the model which asks for
the change</li>
<li><code>__changeset_rules_source_id</code>: id of the record which asks for the
change</li>
</ul>
<p>Also, they should extend the selection in
<code>ChangesetFieldRule._domain_source_models</code> to add their model (the
same that is passed in <code>__changeset_rules_source_model</code>).</p>
<p>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.</p>
<a name="screenshot"></a>
<h4>Screenshot:</h4>
<ul>
<li><p class="first">Configuration of rules</p>
<img alt="partner_changeset/static/src/img/rules.png" src="partner_changeset/static/src/img/rules.png" />
</li>
<li><p class="first">Changeset waiting for validation</p>
<img alt="partner_changeset/static/src/img/changeset.png" src="partner_changeset/static/src/img/changeset.png" />
</li>
</ul>
<a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/134/10.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a>
<a name="known-issues-roadmap"></a>
<h3>Known issues / Roadmap</h3>
<ul class="simple">
<li>Only a subset of the type of fields is actually supported</li>
</ul>
<a name="bug-tracker"></a>
<h3>Bug Tracker</h3>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/partner-contact/issues">GitHub Issues</a>. 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</p>
<a name="credits"></a>
<h3>Credits</h3>
<a name="images"></a>
<h4>Images</h4>
<ul class="simple">
<li>Odoo Community Association: <a class="reference external" href="https://github.com/OCA/maintainer-tools/blob/master/template/module/static/description/icon.svg">Icon</a>.</li>
</ul>
<a name="contributors"></a>
<h4>Contributors</h4>
<ul class="simple">
<li>Guewen Baconnier <<a class="reference external" href="mailto:guewen.baconnier@camptocamp.com">guewen.baconnier@camptocamp.com</a>></li>
<li>Denis Leemann <<a class="reference external" href="mailto:denis.leemann@camptocamp.com">denis.leemann@camptocamp.com</a>></li>
<li>Yannick Vaucher <<a class="reference external" href="mailto:yannick.vaucher@camptocamp.com">yannick.vaucher@camptocamp.com</a>></li>
</ul>
<a name="maintainer"></a>
<h4>Maintainer</h4>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>This module is maintained by the OCA.</p>
<p>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.</p>
<p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>