Within the fixlist of the new released CR3 of IBM Connections 5 there are several new configuration options mentioned. One of the interesting ones for me is the mobile update parameter AllowRemoveAccount. The default value is “false” and your Connections environment still works before, but what’s changed when you set this to true?
The official documentation is already uptodate and shows us:
When you set this option to true, accounts can be removed from a mobile device without requiring the user to login and without any authorization check. The user is asked to confirm the deletion of an account before it is removed.
So this helps me with my long list of Connections environments on my mobile clients. Until you set this to true you can only remove a profile, when you still can login to this system. I have several environments configured on my mobile which i can’t access anymore, because my user is disabled, or the system is only available within special wifi or network environments. So i’m not able to remove these accounts.
I will set this to true in all environments i have access to, to prevent this behavior.
Please beware of the additional infos in the online help:
If a user has existing accounts that they cannot access and that were created before this feature was available, those accounts cannot be deleted using the AllowRemoveAccount property.
Validation error
After checking out the mobile-config.xml (yes you should always use wsadmin to change config parameters), the parameter was not set in the file. So i added it and saved my change.
After checkIn i got a validation error, first i thought the order of
parameters was wrong and so i checked the mobile-config.xsd. Even in the
xsd the parameter wasn’t mentioned. So i checked
<connections-root>/mobile/mobile/mobile/mobile-config/mobile-config.xsd|xml
and there the parameter (and the other new ones) is available. I’m sure
that the update was finished successfully without errors, so i checked
two other systems (Windows and Linux) with CR3 and there was the same
behavior, the new parameters were not copied to LotusConnections-config.
After manually copying the xml and xsd i could set the values and after
restarting of mobile the new feature was available.
When i enabled the feature the first time and i like the xml validation feature of checkIn and checkOut, so i used wsadmin to checkOut the mobile-config.xml
I haven’t checked if the new parameter
useLeadingWildcardForGroupTypeahed with LotusConnections-config.xml
works, but it isn’t available in the xsd too and i can’t found it in the
complete connections-root directory. Will try the next days.
