Oracle Universal Content Management Digging into Rules and Profiles

1
Oracle Universal Content Management Digging into
Rules and Profiles

• Vijay Ramanathan
• Principal Product Manager

2
The following is intended to outline our general
product direction. It is intended for information
purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver
any material, code, or functionality, and should
not be relied upon in making purchasing
decisions.The development, release, and timing
of any features or functionality described for
Oracles products remains at the sole discretion
of Oracle.
3
Metadata Model
Simplify User Experience
Organize
Minimize
Contextualize
4
Metadata Model
Capture Useful Information
Significant
Relevant
Accurate
5
Metadata Structures
Custom
Custom
Application Data
Default Info
6
An approach to grouping metadata fields
Context-specific state information
Required and/or optional depending on
context E.g. - Approval State, Dates, etc.
Context-specific custom information
Required and/or optional depending on
context E.g. - Department, Customer Name, etc.
Context-specific Application Information
Fields that are helpful to the application E.g. -
Folder, Rendition Set, etc.
Essential Information
Important regardless of application or
context E.g. - Title, Security, Type, etc.
7
An approach to grouping metadata fields
Context-specific state information
Mix and match groups based on user application
context
Context-specific custom information
Examples Require Essentials, Folders, Watermarks
and Dates for Press Releases Hide WCM fields when
not checking in web content Show Approval
Status for users with appropriate privileges
Context-specific Application Information
Essential Information
8
Points to consider while creating metadata fields

• Metadata Dependencies
• Field Reuse
• Lists
• Fields
• Restricting Lists
• Example If person in UK is checking in case
  study, restrict list of countries to European
  countries but if person in Asia is checking in a
  case study, show Asian countries only.

9
Points to consider while grouping metadata fields

• Context-based display
• Example Show Contract Start and Expiration Date
  fields only when person from Legal is checking in
  Contract.
• Context-based default values
• Example Person from Legal is checking in a
  contract, therefore set Type to Contract and
  Folder to Content Server Folders/Legal/Contracts
  
• Context-based required fields
• Example Comments required on update of document
  for non-admin users

10
Demonstration

• Rules
• Grouping Metadata Fields
• Activation Conditions
• Side Effects
• Profiles
• Restricting Profile Links
• Excluding Non-Rule Fields

11
Q

A
vijay.ramanathan_at_oracle.com