-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
[16.0][FIX] sign_oca Fix sign button visibility #55
[16.0][FIX] sign_oca Fix sign button visibility #55
Conversation
Hi @etobella, |
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.
Makes sense to me.
Thanks for the fix
Before this commit ------------------ Internal user cannot sign a document if this user's partner is a child of some other partner. Example: User "Pepe Frog" has a partner "Meme Inc, Pepe Frog" set as `user.partner_id`. This is because partner "Meme Inc" is set as a company for the partner "Pepe Frog". So when user Pepe Frog is assigned to a sign request he cannot see the "Sign" button. After this commit ----------------- User can see the "Sign" button and sign documents even if related partner has a parent partner set.
4b2b405
to
8b470aa
Compare
Meanwhile another question non related to this PR: |
Sure, be my guest |
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.
/ocabot merge patch
Hey, thanks for contributing! Proceeding to merge this for you. |
Congratulations, your PR was merged at 13ddd1d. Thanks a lot for contributing to OCA. ❤️ |
Before this commit
Internal user cannot sign a document if this user's partner is a child of some other partner.
Example:
User "Pepe Frog" has a partner "Meme Inc, Pepe Frog" set as
user.partner_id
. This is because partner "Meme Inc" is set as a company for the partner "Pepe Frog". So when user Pepe Frog is assigned to a sign request he cannot see the "Sign" button.After this commit
User can see the "Sign" button and sign documents even if related partner has a parent partner set.
This highly likely should close #54