-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
[14.0][ADD] purchase_order_sending_warning #2269
[14.0][ADD] purchase_order_sending_warning #2269
Conversation
6c5a978
to
6496aa4
Compare
b4e8016
to
c0d2309
Compare
c0d2309
to
00f7459
Compare
sending_warning = fields.Selection(selection=[("email_not_sent", "Email not sent")]) | ||
|
||
error_in_sending = fields.Boolean( | ||
store=True, | ||
compute="_compute_error_in_sending", | ||
string="Error in sending", | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we need 2 fields here. Maybe the Selection field is enough.
For the name of the field, I would prefer transmission_error
or sending_error
since it is more important than a warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@florentx 2 fields are there because selection is going to be extended (for example by edi) and user would like to know POs which failed (whatever they failed - edi or email), so computed field will be set whenever mail/edi sending fails. I'll rename.
35e3b6a
to
4fb6ee4
Compare
4fb6ee4
to
1ddcfff
Compare
No description provided.