Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFQ] sale_order_version - sale_order_revision #2844

Open
leemannd opened this issue Dec 12, 2023 · 0 comments
Open

[RFQ] sale_order_version - sale_order_revision #2844

leemannd opened this issue Dec 12, 2023 · 0 comments

Comments

@leemannd
Copy link
Contributor

Is your feature request related to a problem?
The current implementation of sale_order_revision. Allows to create versions of an SO, on which only one is active. This makes revision of the same SO.
Into the module sale_order_revision_multi. We want to have several active versions of an SO. When we confirm one of them. The other ones are canceled.
base_revision and sale_order_revision are adding a the field active on SO, which is not necessary for the creation of several versions.

Describe the solution you'd like
The current proposition, would be to create/update the modules as following:

  • base_version: it would add the base mechanism of version generation of the same model
  • base_revision: inherit from base_version and it adds the field active
  • sale_order_version: implementation of the versions on SO
  • sale_order_revision: depends on sale_order_version and base_revision to have only one active version => a revision

Describe alternatives you've considered
A first work was done in -> https://github.com/OCA/sale-workflow/pull/2671/files#diff-90445d6bc34b420c3b7a067848c74af4c47313994f1342028c4ed4351a707dda
And I'm currently not happy about it (architecture and field active on SO).

Thanks @grindtildeath for your inputs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant