Global Rules for Standard Check In and Search Only
By Kyle Hatlestad on Jul 23, 2009
Or another way to put it...Global Rules that don't take effect in Profiles.
I was recently setting up a UCM instance and was configuring my Profiles to show just the metadata I wanted. And more specifically, I was trying to change the Standard Check In and Standard Search pages to be as clean as possible. To do that, I used Rules in Configuration Manager set to 'Global' and used the 'Is group' selection with the group hidden by default. Here is a sample of what it looks like:
As you can see it makes the default check in screen much cleaner and easier to deal with for most folks. But still allows for access to all of the other fields by dynamically opening the field groups
But I hit a major snag when I tried creating specific profiles and tried to reuse fields from within the global groups. For instance, let's say I want to create an 'Images' profile that had the Standard Fields group from above, but added a new group called 'Image Fields'. And that group had fields that are currently defined in other groups such as the Web Content Management and Other Fields. Well, because those groups were defined as global, I'm not able to overwrite them with a rule in my profile. The global ones win out. So at this point, I can show/hide certain fields with rules in my profile, but I can't control the grouping.
And that's when the workaround struck me. You can use an activation condition on your global rules that force them to execute only on the standard Check In, Search, and Info pages. So basically, you're turning the standard pages into it's own profile. So the activation condition that you add to your global rule would look like:
In this case, xProfileTrigger is the field I use as my profile trigger. BEST PRACTICE TIP: Although it's easy to fall into the trap of using Type (dDocType) as your profile trigger field, for the most flexibility it's recommended to use a custom metadata field for that trigger.
The above example will exclude that that rule for every profile. But maybe you only want to exclude it for certain ones. Then you can simply construct your activation condition to not activate for those certain ones.
[Updated 9/16/09 - Added a space between the "not" and "(" in the activation condition code]