|
1 |
| -.. image:: https://img.shields.io/badge/licence-LGPL--3-blue.svg |
2 |
| - :target: https://www.gnu.org/licenses/lgpl-3.0-standalone.html |
3 |
| - :alt: License LGPL-3 |
4 |
| - |
5 | 1 | =============================
|
6 | 2 | Purchase Order Approval Block
|
7 | 3 | =============================
|
8 | 4 |
|
| 5 | +.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
| 6 | + !! This file is generated by oca-gen-addon-readme !! |
| 7 | + !! changes will be overwritten. !! |
| 8 | + !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
| 9 | +
|
| 10 | +.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png |
| 11 | + :target: https://odoo-community.org/page/development-status |
| 12 | + :alt: Beta |
| 13 | +.. |badge2| image:: https://img.shields.io/badge/licence-LGPL--3-blue.png |
| 14 | + :target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html |
| 15 | + :alt: License: LGPL-3 |
| 16 | +.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fpurchase--workflow-lightgray.png?logo=github |
| 17 | + :target: https://github.com/OCA/purchase-workflow/tree/13.0/purchase_order_approval_block |
| 18 | + :alt: OCA/purchase-workflow |
| 19 | +.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png |
| 20 | + :target: https://translation.odoo-community.org/projects/purchase-workflow-13-0/purchase-workflow-13-0-purchase_order_approval_block |
| 21 | + :alt: Translate me on Weblate |
| 22 | +.. |badge5| image:: https://img.shields.io/badge/runbot-Try%20me-875A7B.png |
| 23 | + :target: https://runbot.odoo-community.org/runbot/142/13.0 |
| 24 | + :alt: Try me on Runbot |
| 25 | + |
| 26 | +|badge1| |badge2| |badge3| |badge4| |badge5| |
| 27 | + |
9 | 28 | This module allows you to block the approval of an RFQ when an Approval
|
10 | 29 | Block Reason has been provided. Upon confirmation of an RFQ the orders will be
|
11 | 30 | waiting for approval by a Manager.
|
12 | 31 |
|
| 32 | +**Table of contents** |
| 33 | + |
| 34 | +.. contents:: |
| 35 | + :local: |
| 36 | + |
13 | 37 | Configuration
|
14 | 38 | =============
|
15 | 39 |
|
16 | 40 | * Go to ‘Purchases / Configuration / Purchase Approval Block Reasons’ and create
|
17 | 41 | the blocking reasons as needed, providing a name and a description. A field
|
18 | 42 | ‘Active’ allows you to deactivate the reason if you do not plan to use it
|
19 | 43 | any more.
|
20 |
| -* Assign the security group 'Release blocked RFQ' to users that should be able |
21 |
| - to release the block. Users in group 'Purchase / Managers' are by default |
22 |
| - assigned to this group. |
| 44 | +* Assign the security group 'Release RFQ with approval block' to users that |
| 45 | + should be able to release the block. Users in group 'Purchase / Managers' |
| 46 | + are by default assigned to this group. |
23 | 47 |
|
24 | 48 | Usage
|
25 | 49 | =====
|
26 | 50 |
|
27 | 51 | Set the Purchase Approval Block
|
28 |
| -------------------------------- |
| 52 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
29 | 53 |
|
30 | 54 | #. Go to ‘Purchases / Purchase / Requests for Quotation’
|
31 | 55 | #. Create a new RFQ and indicate the approval block reason (found in the
|
32 | 56 | right hand side of the screen, below the order date).
|
33 | 57 |
|
34 | 58 | Search existing RFQ
|
35 |
| -------------------- |
| 59 | +~~~~~~~~~~~~~~~~~~~ |
36 | 60 |
|
37 | 61 | There is a filter ‘Blocked’ to search for orders that are blocked for approval.
|
38 | 62 | It is also possible to search RFQ’s with a specific block reason.
|
39 | 63 |
|
40 | 64 | Confirm the RFQ
|
41 |
| ---------------- |
| 65 | +~~~~~~~~~~~~~~~ |
42 | 66 |
|
43 | 67 | #. Press the button ‘Confirm’. If there’s an approval block, the order will
|
44 | 68 | be set to status 'To Approve'. You will then need to request a Purchase
|
45 | 69 | Manager to approve it.
|
46 | 70 |
|
47 | 71 | Release the purchase approval block
|
48 |
| ------------------------------------ |
| 72 | +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
49 | 73 |
|
50 |
| -While the RFQ is in draft, members of security group ‘Release blocked RFQ’, |
| 74 | +While the RFQ is in draft, members of security group ‘Release RFQ with approval block’, |
51 | 75 | can see a button ‘Release Approval Block’. From this point and on, anyone
|
52 | 76 | seeing that RFQ will be able to validate it.
|
53 | 77 |
|
54 | 78 | Notifications to followers
|
55 |
| --------------------------- |
| 79 | +~~~~~~~~~~~~~~~~~~~~~~~~~~ |
56 | 80 |
|
57 | 81 | Followers of the RFQ receive notifications when an approval block has been
|
58 | 82 | set or released.
|
59 | 83 |
|
60 |
| -.. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas |
61 |
| - :alt: Try me on Runbot |
62 |
| - :target: https://runbot.odoo-community.org/runbot/142/11.0 |
63 |
| - |
64 | 84 | Bug Tracker
|
65 | 85 | ===========
|
66 | 86 |
|
67 |
| -Bugs are tracked on `GitHub Issues |
68 |
| -<https://github.com/OCA/purchase-workflow/issues>`_. In case of trouble, please |
69 |
| -check there if your issue has already been reported. If you spotted it first, |
70 |
| -help us smashing it by providing a detailed and welcomed feedback. |
| 87 | +Bugs are tracked on `GitHub Issues <https://github.com/OCA/purchase-workflow/issues>`_. |
| 88 | +In case of trouble, please check there if your issue has already been reported. |
| 89 | +If you spotted it first, help us smashing it by providing a detailed and welcomed |
| 90 | +`feedback <https://github.com/OCA/purchase-workflow/issues/new?body=module:%20purchase_order_approval_block%0Aversion:%2013.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_. |
| 91 | + |
| 92 | +Do not contact contributors directly about support or help with technical issues. |
71 | 93 |
|
72 | 94 | Credits
|
73 | 95 | =======
|
74 | 96 |
|
75 |
| -Images |
76 |
| ------- |
| 97 | +Authors |
| 98 | +~~~~~~~ |
77 | 99 |
|
78 |
| -* Odoo Community Association: `Icon <https://odoo-community.org/logo.png>`_. |
| 100 | +* ForgeFlow |
79 | 101 |
|
80 | 102 | Contributors
|
81 |
| ------------- |
| 103 | +~~~~~~~~~~~~ |
82 | 104 |
|
83 | 105 | * Jordi Ballester Alomar < [email protected]>
|
84 | 106 | * Roser Garcia < [email protected]>
|
85 | 107 | * Darshan Patel < [email protected]>
|
86 | 108 |
|
87 |
| -Maintainer |
88 |
| ----------- |
| 109 | +Maintainers |
| 110 | +~~~~~~~~~~~ |
| 111 | + |
| 112 | +This module is maintained by the OCA. |
89 | 113 |
|
90 | 114 | .. image:: https://odoo-community.org/logo.png
|
91 | 115 | :alt: Odoo Community Association
|
92 | 116 | :target: https://odoo-community.org
|
93 | 117 |
|
94 |
| -This module is maintained by the OCA. |
95 |
| - |
96 | 118 | OCA, or the Odoo Community Association, is a nonprofit organization whose
|
97 | 119 | mission is to support the collaborative development of Odoo features and
|
98 | 120 | promote its widespread use.
|
99 | 121 |
|
100 |
| -To contribute to this module, please visit https://odoo-community.org. |
| 122 | +This module is part of the `OCA/purchase-workflow <https://github.com/OCA/purchase-workflow/tree/13.0/purchase_order_approval_block>`_ project on GitHub. |
| 123 | + |
| 124 | +You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute. |
0 commit comments