In certain scenarios it is useful to have an isolated Personalization Group, so you can test various configurations / setups without affecting the general user population.
This article will provide a step-by-step guide on how to configure this within Environment Manager 10.1 Feature Release 1. The steps are largely the same as on previous versions, although the layout of the console may have changed. Please consult the product guide corresponding to your version for further details.
NOTE: When a user logs on to an endpoint with Personalization enabled, they are compared to the list of Personalization Groups found in the console in a top-down fashion, and then assigned to the first group for which they match the Membership Rules:
In this example, the user is tested against the membership rules of Domain Users first, then Support Users. All other users will fall into the "Default Users" group, for which membership rules cannot be configured.
Below are the steps to create a test personalization group:
1. Create a new Personalization Group with any name you like by right-clicking 'Personalization Groups' and selecting "Add Personalization Group":
2. If the new group does not appear at the top of the list, right-click it and select "Move Up" repeatedly until it reaches the top of the list:
3. Next, you will need to add a membership rule to this new group to match the username of your test user.
As of Environment Manager v10.0, users no longer have a separate set of data for each Personalization Group, instead the data is shared between all groups.
As such, it is not recommended to have a test user with previous data in any other group, as changes made to their data in the Test group will affect their data in all other groups.
A 'User Name' membership rule is configured in the following location:
4. Now you can assign any Windows Personalization or Application Groups you require for testing.
Please note that all Windows Personalization and Application Groups are 'global' - i.e. they are not tied to a particular Personalization Group. If you are doing any testing which involves altering the configuration of any of these Windows Personalization / Application groups, you will need to create a duplicate group with the same configuration, and then make any changes to this duplicate.