Archives
Contributors
Re: New set of module "Requests".
Thanks all for the suggestion. I think we will go with "request_document", for its straight meaning.May be I will land it to,
- server-tools --> request_document, request_document_exception, request_document_tier_validation, etc....
and specific repo, i.e.,,
- hr-expense --> request_document_hr_expense
- purchase-workflow --> request_document_purchase_request
- etc...
Is this ok?On Thu, Jul 29, 2021 at 3:07 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:Hi,"request" also sounds misleading to me and overlaps with the modules Pedro pointed out, one more proposal: "solicitude".My 2 cents,El jue, 29 jul 2021 a las 9:56, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:What about `request_document`?_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lois Rilo AnteloOdoo consultant at ForgeFlow S.L._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Syed Kamran Ali - 02:21 - 30 Jul 2021
Reference
-
New set of module "Requests".
Dear community,Currently I am working on a set of modules which we call "Requests" for a project. And want to check whether there is interest in these modules.At the surface it is quite similar to the "Approvals" of Odoo Enterprise. But in more detail it is like Approvals + Goodies of OCA. So I would say, it is a much better version of the Approvals.The current list of modules are,- requests --> the base module. You can think of it as the envelope where the user will put in their one or many requests and pass through the approval process in one go.
- requests_tier_validation -> extend request for base_tier_validation
- requests_exception -> extend request for base_exception
- requests_custom_info -> extend request for base_custom_info
- requests_operating_unit -> extend for operating_unit
- requests_???
And more documents that can be in the request envelope.- requests_hr_expense -> allow adding expense inside the request envelope
- requests_hr_advance --> allow adding employee advance inside the request envelope
- requests_purchase_request -> allow adding PR inside the request envelope
- requests_???
Small organizations may not need this, but I think bigger organizations that need more control might find it useful, whether it is Expense Request, Purchase Request, Vacation Request, or even Request to create master data, etc...- As a central place for all requests, and approval progress (instead of going through many documents).
- Streamline the way users go through approval process (by using tier validation, or any other extension in the future)
- Approval can be done for the combined amounts of all their requests for the same, ie.., Trip. (instead of fragmented by document)
- The request (as a template) controls how data in documents are filled. For example, a "Taxi Expense Request", helps create an Expense Sheet with all data filled, except amount.
My question is, which Repo should these modules go to? Or should it has a new repo. (I think it is more employee self service like).ThanksKitti U.
by Kitti Upariphutthiphong - 09:01 - 29 Jul 2021
