Author: |
ACSONE SA/NV |
License: |
AGPL-3 |
Branch: |
14.0-65136-mozaik_membership_request_email_matching-mle |
Repository: |
acsone/mozaik |
Dependencies: |
mozaik_address,
mozaik_membership_request,
and
mozaik_membership_request_autovalidate |
Languages: |
Python (339, 92.6%),
and
XML (27, 7.4%) |
Other branches: |
14.0-64203-mozaik_mandate_notes-mle,
14.0-64306-mozaik_event_website-mle,
14.0-65224-mozaik_partner_global_opt_out_no_email-mle,
14.0-mozaik_account_payment_analytic_account-qgr,
14.0-mozaik_graphql-mle,
14.0-mozaik_membership_payment_transaction_state-mle,
14.0-mozaik_membership_request_amount_fix-mle,
14.0-mozaik_membership_request_pre_process_address_fix-mle,
14.0-mozaik_membership_sepa_payment_returns-mle,
14.0-mozaik_partner_banking_mandate_merge_partners-mle,
docs-wip,
mozaik_add_oca_modules_survey-mle,
mozaik_mandate_legislature_fix-mle,
and
update-dotfiles-sbi |
Other repositories: |
mozaik-association/mozaik,
and
skygunner/mozaik |
If partner is recognized on the membership request, sensitive data
(such as name, firstname, email, ...) are not always erasing data
on the partner: if a value was already set on the partner, only
an authenticated user can change these data
(not a force autovalidate). Hence we prevent from changing these
values, and we schedule an activity to an Odoo user.
A system parameter defines which field has to be considered as 'sensitive'.