Global Setting: Alias#RequiredOnUser
Posted: Sun Jan 24, 2010 6:28 pm
Hi,
I came across this in the documentation:
E.g. when the “forced-filter” alias method is used across the dictionary, it is recommended to set the global settings ALIASxREQUIREDONUSER in order to enforce that accounts must be set with specific alias values to be valid.
No further explanation or examples did I find, but my interpretation is that I would create an system parameter like this:
I then tested removing the Alias1 value in an existing user and saving. I was able to do so without error or warning. I also tried logging out and back in, in case this global setting had to be refreshed to take effect. Alias1 is set to an enforced filter and, for some users, applies a bundle value prefix. (I also tested making the key type of the parameter "T/F" as I saw an example elsewhere in the docmentation for "SHOWDAIKEYS".)
How is this parameter supposed to be setup and what precisely should I expect it to do?
Thanks,
Bob
I came across this in the documentation:
E.g. when the “forced-filter” alias method is used across the dictionary, it is recommended to set the global settings ALIASxREQUIREDONUSER in order to enforce that accounts must be set with specific alias values to be valid.
No further explanation or examples did I find, but my interpretation is that I would create an system parameter like this:
I then tested removing the Alias1 value in an existing user and saving. I was able to do so without error or warning. I also tried logging out and back in, in case this global setting had to be refreshed to take effect. Alias1 is set to an enforced filter and, for some users, applies a bundle value prefix. (I also tested making the key type of the parameter "T/F" as I saw an example elsewhere in the docmentation for "SHOWDAIKEYS".)
How is this parameter supposed to be setup and what precisely should I expect it to do?
Thanks,
Bob