From 714ff44fbc6afa48e2dbca7ccb210c1a372408f8 Mon Sep 17 00:00:00 2001 From: Kevin Papst Date: Tue, 18 Feb 2025 17:20:59 +0100 Subject: [PATCH] explain visibility limitations --- collections/_documentation/plugin-custom-fields.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/collections/_documentation/plugin-custom-fields.md b/collections/_documentation/plugin-custom-fields.md index 2db6dd110e..ef2d9fa9db 100644 --- a/collections/_documentation/plugin-custom-fields.md +++ b/collections/_documentation/plugin-custom-fields.md @@ -85,6 +85,17 @@ If you want to use custom roles, you have to follow the documented rules for rol So a role name like `Manager` does not work, it must be `ROLE_MANAGER`. +### Customer, Project and Activity + +You cannot limit the visibility of fields by `Customer`, `Project` or `Activity` when creating a new timesheet. +Because at the moment the form is opened, it is unknown which `Customer`, `Project` and `Activity` the user chooses. + +The same can applies to the custom fields: +- `Project`, if there is no pre-selection (e.g. creation with the `Customer` detail screen) +- `Activity`, if there is no pre-selection (e.g. creation with the `Project` detail screen) + +Once you open an existing record, you can now see the custom field, as its visibility can be detected. + ## Permissions | Permission Name | Description |