Jahres Archiv: 2012

Documentum Records Management

Documentum Records Management

Federated Search Services

Optional componet allows external sources of information (DB, website, third-party search environment) to be searched along with the Documentum repositories. If FSS (formerly named Enterprise Content Integration Services (ECIS)) is not installed the external sources are not available for searching.
Federated Search Services function trough a two-step process. First, the query broker maps a query into a format supported by an external information source and then submits the query to the source.Then the query processor receiver the requested information from the external source, extracts the metadata, filters the response, and returns the result.

Extended Search option is a part of FSS, which adds the following features:

  • Smart navigation: Search results are grouped into clusters of related results in the navigation pane.
  • Real-time monitoring: Status of results from various sources is displayed in real time in graphical and tabular formats.
  • Search Templates: A search template is like a saved search with part of the search criteria unspecified. The unspecified portion of the criteria is provided by the user while performing the search based on a template. Search templates are available under the Saved Searches node.

Federated Records Services

Federated Records Services (FRS) based an the Virtual Content Management (VCM). VCM is designated to managed one master repository and many source repositories. Objects are not replicated or dublicated, because in the master repository proxy objects were created for every necessary object from the source. Only relevant metadata is trasferred to the master repository.
FRS allows you to connect remote repositories (Documentum, external whird-party repositories) to manage their content from the master Documentum repository without necessarily importing content into the master Documentum environment. FRS provides the ability to configure which sources are to be imported, processed, and managed by the master environment.
FRS proviedes the ability to create a proxy object within a Documentum repositorx that links to the main object stored in the external repository.

 

2012-03-28Permalink

Composer – Step 4 create the Lifecycle

Composer – Step 4 create the Lifecycle

You can now create the lifecycle to which objects of type hpe_doctype can be attached.

File–> New–> Other–> Documentum Artifact–> select Lifecycyle

Enter a lifecycle name as artifact name and click Finish.

A new properties tap displayed on the bottom frame. This Porperties tab include a General tab on the left side (screenshot).

  1. Generla tab select the custom type as your Primary type
  2. click in the white area and draw a new rectangle
  3. addtional tabs under general appears
  4. enter in the Overview tab the name of the rectangle = lifecycle state

select both check boxes: Allow attachments directly to this state and Allow scheduled transitions from this state

go to Actions tab
select Set attribute and enter the first attribute of the custom type called: status
the value of the attribute status is draft

click on the Set permission set and select the doc_processor permission set

 

Add four more states: review, approved, effective and obsolete
set the status attribute to the corresponding values of the lifecycle state
Connect the lifecycle states. Draw an arrow between the states and they are connected automatically.

full lifecycle created with Composer

 

2012-03-27Permalink

Composer – Step 3 create Alias Set

Composer – Step 3 create Alias Set
  1. This alias represents a person who is  authorized to review submitted documents and check them for completed informationadjudication_user: This alias represents a person who is authorized to approve or deny processed claims.
    File–>New–>Other–>select Alias Set in the wizard

    Click Finish.
    The Alias Set pane appears in Composer.
  2. You can enter a description to understand the alias set.
    Create a new Aliases to click on Add
    Specify the following information for the fields and click OK.Artifact Name:  processing_user
    Type:  User

    Ensure that the alias that you just created is highlighted and click on the Parameter radio button in the  Value section.

  3. Click on the Select button for the Parameter field and select the processing_parameter installation parameter from the list.

  4. Add another alias to the alias set with the following information:
    Name: adjudication_user
    Type: User
    Parameter: select the radio button and choose adjudication_parameter

Two aliases are created.

2012-03-27Permalink

Composer – Step 2 Installation Parameters

Composer – Step 2 Installation Parameters

Create two installation parameters for two alias sets.
With installation parameters, you can specify the values for the aliases during the installation of the application.
File–>new–>other–> select Installation Parameter in the wizard and click next.

Installation Parameter Artifact:

select User Intallation Parameter as Parameter Type.

click Finish.

Save the project and check the Problems and Error log tab. No problems or errors should be displayed.

Create another installation parameter with the following settings:

Artifact name: Adjudication_parameter

Parameter type: User Installation Parameter

Description: This parameter represents the user that specifies the adjudicator

2012-03-27Permalink