Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: New set of module "Requests".

Archives

Contributors

Re: New set of module "Requests".

Re: New set of module "Requests".

Re: New set of module "Requests".

I am also thinking about "hr_request", "hr_request_???". Because I think it towards end users / employee use.

But says, we have hr_request_purchase_request, hr_request_stock_request, it might sound weird.

On Thu, Jul 29, 2021 at 2:42 PM Simone Orsi <simahawk@gmail.com> wrote:
Hello there :)

Can we avoid using  "request" as name? As we are on a web app this clashes w/ the base concept of `request`.

Any better specific name?

Cheers

On Thu, Jul 29, 2021 at 9:37 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
OK, thanks for the explanation. I think we already have some of this as a specific thing (purchase_request, stock_request), and this can be a generalization, and they can maybe be derived from this one in the future.

Please don't use plurals in module names though. Call it `request`.

Regards.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Kitti Upariphutthiphong - 09:46 - 29 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.

    image.png

    image.png

    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).

    Thanks
    Kitti U.
    by Kitti Upariphutthiphong - 09:01 - 29 Jul 2021

    2 attachments 2 attachments

    image.png
    image.png