Rights/Access Permission Based (Prescription) Tabs

Support Developer
1

I have attached a snap. I want to make these Tabs/Pages rights-based for Prescription.

The requirement is that only those Tabs/Pages should be visible in Prescription which are related to the doctor’s specialty.

For example:

  • If a doctor is a Dentist, then only Dentistry-related tabs should be shown.

  • If the doctor is a Gynecologist, then only Gynecology-related tabs/pages should be visible.

I want to implement this specialty-based access control on the tabs.

I have already successfully handled rights-based access for the data inside the tabs (record-level access is working fine).

However, now I want the tabs themselves (UI pages) to be hidden or shown based on the doctor’s specialty, so that the doctor only sees tabs relevant to their own specialty and all other tabs do not appear at all.

I have tried many approaches, but I have not been successful so far.

image
image1332×896 120 KB

Below, In Dentistry Tab (Its not visible for Medical Offices but to Dentist only).
But I want to Hide this Dentistry Tab using Rights, Your Help is Required Plz…

image
image1600×945 111 KB

2

You could define method view_attributes to make tabs visible depending on function field which is doctor’s speciality.

Example here: Blame · modules/sale/product.py · branch/default · Tryton / Tryton · GitLab

Something like this:

   speciality = fields.Function(fields.Char("speciality"), 'get_speciality')
   ...

    def get_speciality(self, name):
        if self.doctor:
            return self.doctor.speciality

   ...

    @classmethod
    def view_attributes(cls):
        return super().view_attributes() + [
            ('//page[@id="dentist"]', 'states', {
                    'invisible': Eval('speciality') != 'dentist',
                    })]
3

This is implemented in new 7.8 series. Exactly what you are requesting is implemented in the following issue:

You may upgrade your server to newer series or backport the changeset to your custom models (it’s easly doable by including the code in some custom module).