Task #378
open
Attribute mapping on system - feedback
0%
Description
On adding new attribute to mapping on system:
1) Its not obvious that select box with attributes on schema doesnt contains all attributes from schema. It should show them all.
2) While mapping entity atribute, its posible to chose it from select box. It should be the same for extended atributes, because to find its keys takes a lot of time.
3) Using non-existing extended atribute key creates new attribute for all entities in IdM. User should be notify, that he did not use existing key.
4) Option Send always should be incompatible with option Send if IdM value exists
5) There are settings by check-boxes, but its not clear which ones have help. Attrs with help must be marked with a question mark.
Updated by Marcel Poul almost 7 years ago
Petr Michal wrote:
3) Using non-existing extended atribute key creates new attribute for all entities in IdM. User should be notify, that he did not use existing key.
It would be nice if the user is acked about creating new extended attribute. It is common mistake, that the user misspell a word and in that case he does not want to create new extended attribute. He just wants to correct the name and save current form.
Updated by Radek Tomiška almost 7 years ago
- Category set to Frontend
- Assignee set to Vít Švanda
Updated by Vít Švanda almost 7 years ago
- Category changed from Frontend to Feedback
Updated by Petr Michal almost 7 years ago
Two new remarks:
6) We dont have agenda, for set constant from role to system. Now it must be put into transformation to system script like (return "my_constant"). This is widely used, but because its definitly not transformation of value, its really confusing. We should think about some new agenda for constants setted from roles.
7) When we are using role to set some values to system, in most cases not all attributes from given mapping are used. Would be nice to have a link to full mapping on system under attributes mapped in role.
Updated by Petr Michal almost 7 years ago
8) Mapping of password is confusing. Because password cannot be selected as entity attribute. When mapping password there must be some help with explanation and also fields which are not needed in password mapping must be hide.
9) When mapping attribute in role, Strategy and Identificatior check-box must be disabled for overloading. These attributes must be showed read-only from system setting. Doesent make sence to overload them in role.