Skip to content

Commit

Permalink
test-requirements.txt
Browse files Browse the repository at this point in the history
  • Loading branch information
AungKoKoLin1997 committed Nov 17, 2023
1 parent 76344ab commit c3c07de
Show file tree
Hide file tree
Showing 4 changed files with 30 additions and 31 deletions.
19 changes: 10 additions & 9 deletions crm_exception/README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ CRM Exception
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:498512792cef75c7813a75027dc0c867fa7077e8924a866079014cc458dcf489
!! source digest: sha256:811943ad09fec50d0ac57f5124dd8a2d2c04327e1d49ecda72d2394891457a11
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
Expand Down Expand Up @@ -38,16 +38,17 @@ This module allows you to attach several customizable exceptions to your opportu
Usage
=====

To use this module, follow these steps:
Using this Module:

#. Create exception rules for the `crm.lead` model.
#. Navigate to CRM > Stages:
To configure exception handling for CRM stages, follow these steps:
a. Create a new stage or edit an existing one.
b. Check the `ignore_exception` checkbox if you want to disable exception checks for this stage.
c. Define specific exception rules in `exception_ids`. The defined exception rules will be checked for this stage. If this field is left empty, all exceptions will be checked.
When working with the crm.lead model, you can establish standard exception handling
by defining rules based on specific criteria. (Standard exception handling means
the module automatically checks all exception rules associated with the current record model, crm.lead.)

Note: Customizing exception rules allows you to tailor the exception handling behavior for each CRM stage to meet specific needs.
Additionally, the module offers advanced exception control for CRM stages. As you navigate to CRM > Stages,
you can create or edit a stage and use the ignore_exception option to bypass standard checks for that stage if needed.
Moreover, by defining specific exception rules in the exception_ids field for a stage, these rules will exclusively be checked
for that stage, providing a more tailored approach. If the exception_ids field is left empty, the stage will follow standard behavior
and check all exceptions.

Bug Tracker
===========
Expand Down
17 changes: 9 additions & 8 deletions crm_exception/readme/USAGE.rst
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
To use this module, follow these steps:
Using this Module:

#. Create exception rules for the `crm.lead` model.
#. Navigate to CRM > Stages:
To configure exception handling for CRM stages, follow these steps:
a. Create a new stage or edit an existing one.
b. Check the `ignore_exception` checkbox if you want to disable exception checks for this stage.
c. Define specific exception rules in `exception_ids`. The defined exception rules will be checked for this stage. If this field is left empty, all exceptions will be checked.
When working with the crm.lead model, you can establish standard exception handling
by defining rules based on specific criteria. (Standard exception handling means
the module automatically checks all exception rules associated with the current record model, crm.lead.)

Note: Customizing exception rules allows you to tailor the exception handling behavior for each CRM stage to meet specific needs.
Additionally, the module offers advanced exception control for CRM stages. As you navigate to CRM > Stages,
you can create or edit a stage and use the ignore_exception option to bypass standard checks for that stage if needed.
Moreover, by defining specific exception rules in the exception_ids field for a stage, these rules will exclusively be checked
for that stage, providing a more tailored approach. If the exception_ids field is left empty, the stage will follow standard behavior
and check all exceptions.
24 changes: 10 additions & 14 deletions crm_exception/static/description/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -367,7 +367,7 @@ <h1 class="title">CRM Exception</h1>
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! source digest: sha256:498512792cef75c7813a75027dc0c867fa7077e8924a866079014cc458dcf489
!! source digest: sha256:811943ad09fec50d0ac57f5124dd8a2d2c04327e1d49ecda72d2394891457a11
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<p><a class="reference external image-reference" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <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.png" /></a> <a class="reference external image-reference" href="https://github.com/OCA/crm/tree/16.0/crm_exception"><img alt="OCA/crm" src="https://img.shields.io/badge/github-OCA%2Fcrm-lightgray.png?logo=github" /></a> <a class="reference external image-reference" href="https://translation.odoo-community.org/projects/crm-16-0/crm-16-0-crm_exception"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external image-reference" href="https://runboat.odoo-community.org/builds?repo=OCA/crm&amp;target_branch=16.0"><img alt="Try me on Runboat" src="https://img.shields.io/badge/runboat-Try%20me-875A7B.png" /></a></p>
<p>This module allows you to attach several customizable exceptions to your opportunities.</p>
Expand All @@ -386,19 +386,15 @@ <h1 class="title">CRM Exception</h1>
</div>
<div class="section" id="usage">
<h1><a class="toc-backref" href="#toc-entry-1">Usage</a></h1>
<p>To use this module, follow these steps:</p>
<ol class="arabic simple">
<li>Create exception rules for the <cite>crm.lead</cite> model.</li>
<li><dl class="first docutils">
<dt>Navigate to CRM &gt; Stages:</dt>
<dd>To configure exception handling for CRM stages, follow these steps:
a. Create a new stage or edit an existing one.
b. Check the <cite>ignore_exception</cite> checkbox if you want to disable exception checks for this stage.
c. Define specific exception rules in <cite>exception_ids</cite>. The defined exception rules will be checked for this stage. If this field is left empty, all exceptions will be checked.</dd>
</dl>
</li>
</ol>
<p>Note: Customizing exception rules allows you to tailor the exception handling behavior for each CRM stage to meet specific needs.</p>
<p>Using this Module:</p>
<p>When working with the crm.lead model, you can establish standard exception handling
by defining rules based on specific criteria. (Standard exception handling means
the module automatically checks all exception rules associated with the current record model, crm.lead.)</p>
<p>Additionally, the module offers advanced exception control for CRM stages. As you navigate to CRM &gt; Stages,
you can create or edit a stage and use the ignore_exception option to bypass standard checks for that stage if needed.
Moreover, by defining specific exception rules in the exception_ids field for a stage, these rules will exclusively be checked
for that stage, providing a more tailored approach. If the exception_ids field is left empty, the stage will follow standard behavior
and check all exceptions.</p>
</div>
<div class="section" id="bug-tracker">
<h1><a class="toc-backref" href="#toc-entry-2">Bug Tracker</a></h1>
Expand Down
1 change: 1 addition & 0 deletions test-requirements.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
odoo-addon-base-exception @ git+https://github.com/OCA/server-tools@refs/pull/2757/head#subdirectory=setup/base_exception

0 comments on commit c3c07de

Please sign in to comment.