Simon Read
My feedback
32 results found
-
91 votesSimon Read supported this idea ·
-
88 votesSimon Read supported this idea ·
-
55 votesSimon Read supported this idea ·
-
42 votesSimon Read supported this idea ·
-
20 votesSimon Read shared this idea ·
-
58 votes
An error occurred while saving the comment Simon Read supported this idea · -
19 votesSimon Read shared this idea ·
-
93 votesSimon Read supported this idea ·
-
14 votesSimon Read shared this idea ·
-
67 votesSimon Read supported this idea ·
-
44 votesSimon Read supported this idea ·
-
145 votesSimon Read supported this idea ·
-
3 votesSimon Read shared this idea ·
-
39 votesSimon Read supported this idea ·
-
315 votesSimon Read supported this idea ·
-
79 votesSimon Read supported this idea ·
-
164 votes
Hi,
This is to update that this issue is still not planned to be developed in the current road map. We will continue to evaluate it for a future release.
Therefore we are keeping this under "Under review" status.
Best regards,
Yael.
Simon Read supported this idea · -
99 votesSimon Read supported this idea ·
-
63 votesSimon Read supported this idea ·
-
20 votesSimon Read supported this idea ·
I support the addition of view specific configuration. It is particularly important that titles that appear on the person entity card are actually accessible via that view. At the moment we can see electronic titles on the person entity card that users can't access because those titles aren't activated for that view (in our case we're using available for groups to control view level access). We can't realistically use the person entity functionality until this has been resolved