Positioning metadata groups in Profiles

I was recently asked how to control the order of metadata groups that get created with Rules and Profiles in UCM.

In the Configuration Manager applet, you can create Rules which include multiple metadata fields and designate that rule as a Group. This means these fields will be displayed together in the order in which they are defined in the rule. You can also define a header display for the group and default them as hidden or displayed.

But if you have multiple metadata groups on a page, what determines the order of the groups?

metadata_groups.jpg

It's all determined by the first field in the group. That field will have a Field Order that was set on the Information Fields tab. UCM will look at the field order for the first metadata field in each group and order them according to that value. So to get group B to appear above group A, the first field defined in B needs to have a lower Field Order then the first field in group A.

Comments:

Hi Kyle, That is applicable in case of custom metadata fields but then how to control the display order of the system defined fields like content ID, security group, title, type etc? Thanks in Advance Sam

Posted by sam on February 27, 2011 at 11:50 AM CST #

Hey Sam, The same holds true for system fields as well. The main difference is the "default" order of the system fields is already defined in the system. So if I create a metadata group of both system and custom metadata fields, if I have a system field as the first field, it will display as one of the top groups on the page. That's because the system fields are generally defaulted as being above custom fields. But if I was to take that same group of fields and make one of the custom fields the first one in the group, then that group will be placed wherever that custom field would be placed...including those system fields. And if you want the system fields as a group, but you don't want a custom field displayed at the top of the group to control it's position, you can place a "dummy" field at the top and make it hidden. That way it controls the position of the group, but allows only the system fields to be displayed. Thanks, -Kyle

Posted by kyle.hatlestad on March 22, 2011 at 10:58 PM CDT #

Is there really no way to put a custom metadata above the system fields? I badly needed to do this. Thanks.

Posted by dory on April 03, 2011 at 10:43 PM CDT #

Hey Dory, Yes, it is possible. You need to create a rule that will group all of the system fields together. Then you you would need another rule with a group of the custom fields. Then in your profile, you would place the rule of custom fields above your rule of system fields. Just make sure you get all of the system fields placed within groups. Thanks, -Kyle

Posted by kyle.hatlestad on April 11, 2011 at 01:12 AM CDT #

Hi Kyle! How may I group system fields like dStatus which doesn't appear on the metadata's list? Thanks.

Posted by guest on January 25, 2012 at 01:48 PM CST #

The dStatus field is not considered a metadata field, so it is not available to be used for positioning with other fields with Rules and Profiles. You would need a custom component in order to position this differently on the Content Information page.

Thanks,
-Kyle

Posted by Kyle Hatlestad on February 07, 2012 at 04:59 AM CST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Kyle Hatlestad is a Solution Architect in the WebCenter Architecture group (A-Team) who works with WebCenter Content and other products in the WebCenter & Fusion Middleware portfolios. The WebCenter A-Team blog can be found at: https://blogs.oracle.com/ ateam_webcenter/

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today