Allow configuring the absence of certain steps/precisions

[milstan]

Description

In PRCI, currently, you can configure categories you want to include (or if none, all categories possible are offered). However, it is not possible to dissallow the choice of categories all toghether.

Same as with other configuration options.

Intended outcome

Support the following configuration options: allow/dissalow :

• slecting particular data-categories
• advanced settings (maybe do it per subsection of advanced settings)
• additional message

Also, in TRANSPARENCY requests, allow to limit the list of transparency demands to only certain transparency.* actions (in certain locations not all of this information is neeed, like in USA, only a subset is required)

For revoke-consent, ideally make the choice all/one optional, and make it visually consistent with all/one choices in categories, transparency actions (check-box rather than radio-button).

If they want, a client should be able to configure PRCI to only accept very rudimentary, non-detailed requests assuming all default options (regarding data-categories, targets, provenances, etc.)

[milstan]

Maybe consider allowing setting-up this behavior per demand type (like I want to ask for categories within DELETE request, but not in ACCESS request) if it makes sens.

[jboileau99]

Maybe consider allowing setting-up this behavior per demand type (like I want to ask for categories within DELETE request, but not in ACCESS request) if it makes sens.

@milstan A way we could support this is to have the data-categories attribute take either a list as it does now, or a object that defines the behaviour per action. So you could pass either of these:

Have any request type involving data categories limit the options to contact and uid:

<bldn-priv-request
    data-categories="['contact', 'uid']"
></bldn-priv-request>

Specify the allowed categories per request action:

<bldn-priv-request
    data-categories="{
        access: "['contact', 'uid']",
        delete: "['biometric', 'affiliation']"
    }"
></bldn-priv-request>

In the above case, object and restrict demands would still offer all data categories, while access and delete demands would be limited to those categories listed.

We could do something similar for the other options dropdown (used to be advanced settings), where you can define which sub-sections should be available across all the dropdowns or specify them per demand type.

[milstan]

Sounds good. I would maybe try and make the top-level parameters be the actions, and than under them, set other parameters