[midPoint] Options / Dropdown for New User Properties

[Ivan Noris]

Hi Patrick,


On 09/12/2016 11:26 PM, pdbogen at cernu.us wrote:
> Thanks!
>
> This was extremely helpful. I do have a few comments, though:
>
> 1) I think this would have been easier to find if there was a link to it from 
> the 'see also' section of 
> https://wiki.evolveum.com/display/midPoint/Resource+Schema

I agree that we should make link to this from other documents, but
probably not from Resource Schema, as object Template is not related to it.

>
> 2) The syntax for the table itself as described on 
> https://wiki.evolveum.com/display/midPoint/Lookup+Tables seems to have two 
> errors:
>
>   1. The closing tag for the second entry in the table is missing the `/`; and 
>   2. The tags for each entry in the table should be 'row' rather than 'table'.
>
> These two changes allowed me to create and import a table properly; I was not 
> able to do so when each entry was in `<table></table>`.

I have just fixed the wiki page, thank you for noticing!

>
> 3) The rendering of a field that is restricted in this way is not perfect- it 
> still behaves a bit like a text field in that I can type arbitrary values into 
> it. It does indeed prohibit disallowed values, but I think that the user 
> experience would be a little nicer if it were rendered as a drop-down. This is 
> a very minor issue, thuogh.

This has two causes, as far as I know:
- you can type the arbitrary values because we would like to allow
typing the arbitrary values for the future
- but this is not implemented yet

Please see also: https://jira.evolveum.com/browse/MID-2633,
https://jira.evolveum.com/browse/MID-2299
>
> 4) No error is indicated when I _do_ try to provide a prohibited value. Since 
> the field is a text field, it seems to allow me to type an arbitrary value in 
> and submit it.

Which version are you using? I have just tried current master (almost
3.4.1) and typing a value which is not in the lookup table definition
will indeed show a warning just below the attribute in the form, saving
will not save it (but the form will be allowed to be saved, the value
will be ignored).

Many thanks,
Ivan

-- 
Ivan Noris
Senior Identity Engineer
evolveum.com