TEAM Component Library Introduction

Workflow Reports

Released: June 2008

Compatibility: 10gR3, 11g

This component will put a link to the document history and workflow history on the content info page for each piece of content. Clicking on 'history' takes users to the Content History report that displays the entire history of actions the piece of content may have gone through. Clicking on 'workflow' takes users to the Workflow History report that displays the entire workflow history the piece of content may have gone through.

TEAM Expired Content Delete

Released: July 31, 2012

Compatibility: 11gR1 (11.1.1.1.0+)

When content items are expired in the content server, they are removed from the search index, but remain on the file system. In time, these items can occupy valuable disk space. The TEAM Expired Content Delete component will systematically delete expired content items and their revisions after a specified time period.

This component has two configuration variables that can be set within the component to alter the time period that the content server will retain expired content, as well as the time it will initiate the removal of those content items:

• TXEExpireDuration - the amount of time the system will retain the content before deletion. The default is 90 days.

• TXEScheduledEventTime - the time on the server that the system will initiate the deletion. The default is 12:00 AM.

Notes

• This component removes all revisions of an expired content item.

• This component assumes that you are using the default expiration configuration of ExpireRevisionOnly=false, which, when set to FALSE, all revisions expire when the current revision expires.

• If you are using ExpireRevisionOnly=true, which would assume that you want keep the previous revisions when the latest version expires, then this component is not recommended, as it will remove all revisions, including those that aren't marked expired.

Folders Secure 11g

Released: April 2012

This component works in conjunction with the Folders_g component. It provides a role security check for activities related to adding/editing/moving/removing collections. Only users with the proper role permissions will be allowed to perform these activities. A list of roles that are allowed to administer collections is maintained in /config/config.cfg.

ADSync

Released: May, 2012

This component will sync users from an AD/LDAP source into UCM. Following are the specific attributes:

• Relies on a properly configured LDAP provider with user attributes mapped (see installation section)

• Contains an administration page under the Administration menu to allow the admin user to set up the following

- The name of the UCM defined LDAP provider

- The AD/LDAP attribute name that denotes if the user is active or inactive. This will be resolved as a boolean

- Hour of the day to run the scheduled sync. 00 = midnight, 23 - 11:00 PM

- Button, when clicked, will execute the sync real time

- A list of all the past run logs - these are stored as non-managed files within the UCM directory - weblayout/groups/public/adusersync

• Adds any active AD users not in UCM

• Deletes any UCM external users not in AD

• Deletes any inactive AD users existing in UCM

• Updates any user metadata information in UCM for existing/active AD users

AdditionalSortFields

Released: June, 2012

This component is a sample used to describe how to specify additional fields as sortable during searches. As an example, this component specifies several additional standard fields such as dDocName and dDocAuthor as sortable fields. To do this, we need to merge some data into two tables which are both located in <home_dir>\ucm\idc\resources\core\tables\searchindexerrules.htm. If you are using Oracle 11g Database and are using the OracleTextSearch component, you'll need to specify your sort fields as Optimized Fields. In UCM, go to Administration > Text Search Admin and add the fields to the Optimized Fields list. You'll then need to perform a fast rebuild. Feel free to modify this component to specify any additional sort fields for your particular Content Server instance. This component is provided for sample use and is provided "as-is"; TEAM disclaims all express and implied warranties, including, the implied warranties of merchantability or fitness for a particular use. TEAM shall not be liable for any damages, including, direct, indirect, incidental, special or consequential damages for loss of profits, revenue, data or data use, incurred by you or any third party in connection with the use of these materials.