Inside Activate
Development
Migration of SelectUserFromList
4 min
the selectuserfromlist aspx page was commonly used in earlier versions of activate web wizards and forms in later versions, this functionality is replaced and extended by the selectuserfromgrid page this document explains the recommended migration approach and highlights version specific behaviour to be aware of recommended replacement for web wizards and forms, selectuserfromgrid should be used instead of selectuserfromlist aspx selectuserfromgrid provides equivalent functionality while offering greater flexibility rather than applying filtering logic directly in the page definition, user selection is controlled by overriding the availableusers query behaviour differences and prerequisites when migrating from selectuserfromlist aspx to selectuserfromgrid, ensure the following properties are configured autoskiponempty displaycolumns these properties were not consistently available prior to version 8 1 4 465 and may need to be explicitly defined when upgrading existing wizards selecting disabled users support for selecting disabled users was introduced in activate build 8 1 4 481 from this version onwards, selectuserfromgrid can be configured to return disabled users when required, provided the correct parameters and query are supplied disabled users query configuration disabled user selection is controlled using a task string parameter that defines the ldap query used to retrieve users an example ldap filter is shown below (&(objectcategory=person)(anr=%=/data/firstname% %=/data/lastname%)(useraccountcontrol 1 2 840 113556 1 4 803 =2)) this query returns disabled users whose first name and last name match values provided in the job data migration considerations when migrating existing web wizards replace selectuserfromlist aspx with selectuserfromgrid move filtering logic into the availableusers query confirm required properties are defined for the target activate version validate behaviour for disabled users if applicable testing should be completed in a non production environment before deploying updated wizards