Partner list – system description

Tables and filters of the partner list, content scope, rights of the row buttons, status and how permanent deletion works.

The partner master list shows customers, suppliers and client companies. Finalised module; row actions link to the invoice list and the account statement.

Data model

Table names carry the installation's own prefix in the database.

TableRole
companypartner (name, tax numbers, status, company group)
company_address, addressaddresses
company_bankaccount, bankaccountbank accounts
company_group, company_group_descriptioncompany group
navtax authority API data (on delete)

Process

  1. List: without the right a warning HTML. Filters: filter_company_group_id, filter_company_id, filter_company_name, filter_company_tax, filter_taxhu, filter_address, filter_bankaccount, filter_valid, filter_companyaddress_true/false, filter_data.
  2. Scope: the company group/company filter follows the content right (getCompanyGroupFilter); per partnerScopeOpen() the company as customer-side master is not filtered, on the client side it is.
  3. Status: enable/disable on the selected companies or the one in GET.
  4. Delete: deleteCompany() – DELETE from company, company_address and nav.

Permissions

  • Function rights: list, edit (edit button), taxpayer (tax authority icon), status, delete, debug. Row links: finance/invoice list (filter_supplier_id / filter_customer_id), finance/settlement list.
  • statusdelete is classified BASE, but the controller does not check it and has no endpoint for it.

Known limitations

  • Status change and deletion do not check the content scope.
  • Deletion does not check references (invoice, contract etc.).
Related topics: partner permissions