[RFC] Enhancement to base_tier_validation about server-ux HOT 10 CLOSED

Hi Kitti,

other improvement list :

1. Customised validation error messages - Business Messages rather than the system ones
2. Also, can this be worked along side with base_exception OCA module..? Some of the functionality seems to be an overlap.

-Naran

from server-ux.

Sure. But can you explain more. Especially on point 2.

from server-ux.

@nmoturi I added the improvements in the list.

from server-ux.

Among the above enhancement, I think the "Replace notification system tray, with Odoo's Activity infrastructure" is quite harsh and need more opinions.
Functionally, I think it make sense, as the tray came before activity, and once we have activity, it is more unified.

@LoisRForgeFlow do you have comment on this?

from server-ux.

@kittiu why do you want to use activities? activities are not persistent and serve for many things, can't the tier validation get very diluted in activities systray?

Regarding the other items in the list and also continuing my answer in this other PR, I think you can propose everything that are fixes or soft improvements (not important changes in data model) to base_tier_validation and start new submodules (base_tier_validation_*) for bigger improvements. Then we add a section in the settings wizard on base_tier_validation to highlight and give visibility to those improvements.

I think this is the best way to go as I am not able to follow you up on all your proposed changes as much as I would like and I apologize for that. Yet, being realistic it is the best way for you to get job done and code merged quicker.

from server-ux.

@LoisRForgeFlow thank you for your comments. Please no apologize, it is me to apologize. I saw you were super busy with other projects.
I am comfortable with the splitting module and the settings wizard. 👍

from server-ux.

@LoisRForgeFlow - The idea of using the activity groups is to avoid a single person dependent. As an example for a large volume of approvals not everything can be done by a single person, anyone with in the activity group can be approved..

Thanks,
Naran

from server-ux.

@nmoturi Thank you for comment. The point that activity is not persistent is valid. The way systray works now is, it lively query on what todo for the login user, while the activity is just a created record, and so it can get diluted per say.

For your point of single person dependent. If you could explain here too in more detail.

from server-ux.

@kittiu
On a document with many states with branch flow such as a Sale Order, it is a good idea if tier_validation can provide minimal 2 steps. (step 1 _from_state _to_state and then step 2 __from_state.. _to_state...) For example on a quotation or sales order document. Sometimes there is a need to review the quotation before it can be sent or printed for a customer. Once step 1 is ok the quotation can be sent to the customer and may have some changes due to negotiation etc, but once it is sent the second step then become active to prevent the modified quotation data confirmed without review.

from server-ux.

@kittiu
On a document with many states with branch flow such as a Sale Order, it is a good idea if tier_validation can provide minimal 2 steps. (step 1 _from_state _to_state and then step 2 __from_state.. _to_state...) For example on a quotation or sales order document. Sometimes there is a need to review the quotation before it can be sent or printed for a customer. Once step 1 is ok the quotation can be sent to the customer and may have some changes due to negotiation etc, but once it is sent the second step then become active to prevent the modified quotation data confirmed without review.

Just in case it may help, let me mention this state machine implementation for Odoo by Acsone https://github.com/acsone/scobidoo

from server-ux.