IBM logo  

Glossary for IBM FileNet P8 Platform

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z


A

Access Control Entry (ACE)

An entry in an access control list (ACL). An ACE contains a set of access rights for a particular grantee, which could be a machine, a user, or a group, and whether the right is allowed or denied. FileNet P8 ACEs also contain information about their source, whether directly applied, inherited, or from a security template.

Access Control List (ACL)

A list of access control entries (ACEs) applied to an object (class, document, folder, event, or any other securable object). ACLs are displayed on the Security tab of an object's property sheet.

access level

See level.

access rights

The security settings that control access to the objects in an object store or workflow.

ACE

See Access Control Entry.

ACL

See Access Control List.

Action

See disposition action.

adaptor

An interface that communicates events from Process Engine to external entities such as Java™ objects or Java™ Message Service (JMS) messaging systems. Adaptors are part of the Component Integrator.

ADC

Authorized Derivative Classifiers.

aggregation

Part of an internal event trigger that determines which type of RM entity will be affected by the disposition action. For example, you can dispose of an individual record or a container that includes several records, depending on the aggregation. When you set the aggregation level, the action affects all of the entities at that level or below. For instance, if the aggregation level is set to record category, then the action affects all of the subcategories, folders, and records within that category with which that disposition schedule is associated.

alias ID

Identification that enables users to perform queries across object stores. Content Engine uses alias IDs to identify classes and properties that are semantically the same.

alias name

A different name that can be configured for a default attachment command. Available if FileNet P8 eForms integration has been configured.

alternate retention

An alternate retention period applied to entities that meet specified conditions. In Records Manager, multiple alternate retentions can be defined in the same disposition phase. For example, if you keep records in multiple countries or regions, each location might have different laws regarding retention. You would be able to retain records in each location using a retention interval based on a location property. See also disposition schedule and disposition phase.

AND-join

A step in the workflow that acts as a collector for an AND-split step. An AND-split step results in the workflow simultaneously following multiple routes; the AND-join step subsequently brings the workflow back into a single path. An AND-join is also referred to (and designated in Process Designer) as a collector step.

AND-split

A step in the workflow where there are multiple outgoing routes that the workflow can take simultaneously. In Process Designer, the outgoing routing for an AND-split step is set to "all true conditions." An AND-split step must have a corresponding AND-join step (collector step).

annotation

Unstructured information (such as notes, comments, or messages) about a folder or document.

Application Engine

One of the FileNet P8 components. Application Engine hosts the Web sites that interact with object stores and Process Engine.

application integration

Working with libraries and object stores from desktop applications such as Microsoft Word or PowerPoint.

application security template

A type of security template that can be applied by custom applications.

association property

A property in a class that describes an association to another class.

asynchronous

An event that does not occur at predetermined or regular intervals. When using asynchronous event actions in subscriptions, the subscription processor continues processing events without waiting for the results of an action. The action cannot be in the same transaction as the originating activity. See also synchronous.

attachment

A link to information (such as a document in an object store or library) a participant uses to complete a step in a workflow.

attachment command

An action that appears in a toolbar (e.g., Add New, Assign) when an attachment is configured with a workflow policy. Available if FileNet P8 eForms integration has been configured.

attribute

A characteristic of a property. For example, data type is an attribute of a property template.

authentication

The process of verifying a user name and password at login time.

authentication provider

Any of the FileNet-supported LDAP-compliant directory services that provide authentication for the FileNet P8 domain. The authentication provider is identified during FileNet P8 installation.

authorization

The process of determining and enforcing the access rights for an authenticated user.

auto destroy

The process of permanently deleting or destroying records without the use of a workflow. The record removal is immediate when it has reached the end of the retention schedule.

Return to Top

B

bootstrap properties

Initialization values for the Application Engine software.

box

Derives from the PhysicalContainer class. A box provides a mechanism to model physical entities that contain other physical entities.

branch

A set of parallel steps in a workflow. You can add branches to an existing branch and merge branches. A workflow step is a node in a branch.

Business Activity Monitor (BAM)

An extension of the FileNet P8 Platform that works with Process Analyzer to allow you to monitor your business activities.

Return to Top

C

catalog

When declaring a record, the step in which the record class and file plan location are specified.

category

A category (record category) is a container that categorizes a set of related records within a file plan. You typically use record categories to classify records based on functional categories. A record category can contain subcategories and record folders. In the Base and DoD data models, you can declare records directly into categories. The PRO data model does not allow this.

CBR

See Content-Based Retrieval.

charge in

The process of returning a physical record to its home location.

charge out

The process of checking out a physical record and tracking it in Records Manager.

check in

An action taken on a checked-out document. Checking in a document completes the creation of a new version and concludes the checkout.

check out

An action taken on a versionable object (such as a document) that creates a reservation and makes the content available to the user for editing. No other user can modify a checked-out document. See also Reservation version status.

child work item

A work item created for each participant in a multi-participant step and for each route taken simultaneously from an AND-split step.

choice list

A list of predefined property values. A choice list presents a list of valid choices, such as a list of states or zip codes.

class

A definition of the properties and actions for a particular kind of object. All objects in a class are identical in form and behavior, but can contain different property values and content.

class inheritance

Feature that allows a subclass to derive (inherit) all of the properties of a superclass (its parent in a class hierarchy).

classification

A process for automatically acquiring document properties from the document content (or another source).

classification guide

Security classification guides (SCG) are available only in DoD Chapter 4 data models. Persons with Original Classification Authority can delegate the authority to classify information by creating guidelines to be used by authorized derivative classifiers. Only users assigned to the Classification Guide Administrator security role can create or modify security classification guides.

classification scheme

See file plan.

classified

RM 3.7 and later: If you are using the DoD Chapter 4 data model you can indicate that a record is to be a classified record upon declaration. Classified records have special access restrictions in addition to normal record security.

RM 3.5.1 and before: When declaring a record, you specify the record class and where the record object should be located within the file plan. See catalog.

clear text

A string of characters sent over a network in readable form. They can be encoded for the sake of compression, for instance using Base64 encoding, but can easily be decoded.

clone

An identical copy of the latest approved version of a component, with a new unique component ID (GUID).

collector step

See AND-join.

COM

See Component Object Model.

compliance

Acting in accordance with certain accepted standards, laws, and guidelines.

component

An external entity to Process Engine.

Component Integrator

Native FileNet functionality that makes it possible to interact with an external entity, such as a Java object or JMS messaging system, from a workflow step.

Component Object Model (COM)

A Microsoft specification for how developers create components and build applications from these components. A component is a binary package of code that is compiled, linked, and ready-to-use. At runtime, the component connects with other components to form an application.

component queue

A queue holding work items that can be completed by an external entity that interacts with the workflow via the Component Integrator.

compound document

A collection of files that are used together to create a group of linked documents.

conditional hold

See dynamic hold.

conditional route

A route between two steps in a workflow that is followed only when certain conditions are met.

connection point

A setting that identifies a specific Process Engine server and isolated region number of the workflow database. In Workplace general site preferences, you specify the name of the connection point which sets the isolated region for all Workplace applications, such as Process Designer and Process Administrator. In a farmed environment of Process Engine servers, the connection point specifies the load balancer and the isolated region number. You manage connection points within Enterprise Manager.

container

An IBM FileNet P8 folder. In Records Manager, a container can be a folder, category, box, volume, or hybrid folder. All of these containers are subclasses of the RM Folder class, which is a subclass of FileNet P8 Folder. See folder.

content

The data portion of a document, as opposed to the properties that identify and describe the document.

content cache area

Storage area that holds temporary copies of files retrieved from remote file storage areas, as well as content retrieved from local or remote database storage areas.

Content Engine

The FileNet P8 component that provides an object-oriented repository for managing content and other business-related data, collectively referred to as objects.

Content Engine operations

Programmatic step processors that act on objects stored in an object store as part of a workflow. For example, an operation can publish a document or change the document's security.

content storage area

A physical storage area (either a file storage area, database storage area, or content cache area) for content. While file and database storage areas provide permanent storage, a content cache area provides disk space for temporary copies of content retrieved from file and database storage areas. See also file storage area, database storage area, and content cache area.

Content-Based Retrieval (CBR)

The process of searching for documents based on their content in addition to or instead of searching on properties.

content-less document

A document with properties but no content that is typically used to track a physical item such as a video tape.

CS

See FileNet Content Services.

current version

The latest checked-in version in a document's version series. Only the current version, determined by the IsCurrentVersion property, can be checked out or promoted.

custom object

A generic business object that can be stored in a folder. Unlike document objects, a custom object cannot have versions, lifecycles, or content. Custom objects are not available in Workplace XT.

custom property

A user-defined property, as opposed to a system-defined property. You can assign custom properties to a class.

cut off

The point at which a record is closed and starts its disposition phases.

cut off workflow

A workflow that is launched by the cut off event. The purpose of the cut off workflow is to ensure that the records manager reviews the entity after the cut off trigger and approves the cut off date. The different phases of the disposition schedule start only after approval of the cut off date.

Return to Top

D

data model

A template for a file plan object store to be compliant with certain records management standards. The data model can include metadata and security features. When you create a new file plan object store, you must choose a data model. There are currently four data models: Base: Satisfies the requirements of most corporations; DoD: Satisfies basic Department of Defense requirements per DoD Chapter 2; DoDCH4: Satisfies Department of Defense Chapter 4 requirements, including classified records management; PRO: Satisfies Public Record Office (per UK standard) requirements.

data field

A user-defined workflow field.

data type

A property attribute that defines the kind of data the property represents. Supported data types are string, integer, object, float, date/time, Boolean, binary, and ID.

database schema

The definition of an object store. Content Engine sets up the database schema in tables, columns, and indexes within the object store's database. You can view the schema using the software that supports your database engine. For example, if you're using MS SQL Server, you can view the database schema using SQL Server Enterprise Manager.

database server

The computer that hosts the database engine and the database tables populated with an object store's metadata.

database storage area

A content storage area that retains document content in a database engine. The database storage area also retains all objects contained in the object store, like class definition, property definition, containment, storage policy, and queue events.

deadline

An optional, time-based scheduling constraint that requires a step or workflow to be completed within a certain amount of time. For a step, the deadline is relative to the time the step was routed to the participant. For a workflow, the deadline is relative to the time the workflow was launched. A value of 0 indicates the absence of a deadline.

declare

The act of creating a record object. Declaration and cataloging happen simultaneously. Declaration can be manual or automatic.

default ACE

An editable ACE whose source type is Default. Permissions placed on an instance by the Default Instance Security ACL of its class, as well as permissions placed on a subclass by its parent class are labeled Default by Enterprise Manager's security editor. If you edit a default ACE, it becomes a direct ACE.

default retention

The phase retention period that applies if either no alternate retentions are specified or if the entity does not meet any alternate retention conditions.

default security

The security assigned to an object by pre-defined settings.

demote lifecycle state

An action taken on a document that moves the object back to its previous lifecycle state. See also lifecycle policy.

demote version

An action that changes a major version with the status Released into a minor version with the status In Process. This action also changes the status of the previous major version from Superseded to Released.

designer

One of several components that authorized users can run to create reusable, generally available searches, workflow definitions, workflow subscriptions, and templates for searching, publishing, and document entry. Site preferences control access to the designers.

desktop form template document class

Used when adding a desktop form template (with the legacy .itp file extension) to an object store. This document class is available if FileNet P8 eForms integration has been configured.

See also document class and form template.

destruction

The removal of the record and the object of the record from the system. For electronic documents, both the record object and the document object are deleted. For physical objects, the record object is deleted. Optionally, the metadata of destroyed records can be retained after the record itself is destroyed, providing a record of the destruction of the record.

detailed view

Format for document lists in Workplace in which document properties are listed in columns.

DFS

See Distributed File System.

direct ACE

An editable ACE whose source type is Direct. Permissions placed directly on an object are labeled Direct by Enterprise Manager's security editor. If you edit a default ACE, it becomes a direct ACE.

directly applied ACEs

The access rights acquired from a document class and subsequent edits made by a user or application. Directly applied access rights have precedence over those indirectly applied.

directly applied property

A property that is assigned to a subclass, but not to its superclass.

discovery

In law, the pretrial phase in a lawsuit in which each party can request documents and other evidence from other parties or compel the production of documents and other evidence using the legal system.

disposal phase

A part of a disposition schedule that controls the retention of entities in a particular state for a specified time period. Also called a phase or a disposition phase. Each phase has a phase retention period and a phase action.

disposition

What happens to a record after cut off. Disposition is applied through disposition schedules that are created in Records Manager and associated with containers. Disposition includes one or more disposal phases. Each phase has a phase retention period and a disposition action that occurs at the end of that retention period.

disposition action

Also called phase action. An action performed on entities after the cut off is reached or when their retention period in a disposal phase is over. Fro vital records, it is a periodic review. You create actions on Records Manager. Each action is associated with a workflow. Some examples of actions include: Destroy, Review, Export, Transfer, and Vital Review. Actions need to be initiated manually when the retention period of the phase is over. Each phase has an associated disposition action. Each disposition action is associated with a disposition workflow.

disposition hold

A temporary suspension of disposition processing. You can create a hold and then apply it to an entity. Each hold is for a specific use and can be applied to several entities at one time.

disposition phase

See disposal phase.

disposition schedule

Disposition instructions which specify how long to keep the entity and how to dispose of it. In Records Manager, a disposition schedule has one or more disposition phases. Disposition schedules are created in Records Manager and associated with containers. The disposition schedule applies to the entity type specified by the aggregation.

disposition sweep

A program that processes the file plan object store (usually on a scheduled basis) and computes disposition-related properties, launches the vital review workflow, and launches the cut off workflow where applicable. It marks entities that are ready for disposition. In Records Manager 3.5.0 and before, it was sometimes called Sweep.

disposition workflow

A workflow that is associated with a disposition action that automates that part of the disposition process. Records Manager comes with several workflows. There are several types of disposition workflows. Examples of disposition workflows are: Destroy, Export, and Interim Transfer.

Distributed File System (DFS)

A file system used to store content across multiple servers. Distributed File System gives Content Engine users access to shared directories across a network.

document

An object saved in an object store or library. Documents have properties and security, and can additionally have content, versions, lifecycles, and subscriptions.

Searches, publishing templates, workflow definitions, preferences files, and most documents added by Workplace users are stored as versionable documents. Documents and searches saved in Content Services libraries can have versions; Image Services documents do not have versions. Documents are instances of the Document class or one of its subclasses.

document class

A category for documents in an object store or library. Every document belongs to a document class such as Purchase Orders. The document class determines the document's versioning (where applicable), properties, storage location, security, and lifecycle.

document classification action

A root class that allows developers to create classifiers to examine and automatically map the contents of documents of a specific MIME type to a target document class.

document map

In a workflow policy, allows property mapping between form template cells and document class properties for workflow and document policies. Available if FileNet P8 eForms integration has been configured.

document policy

A specification that indicates which form template and form data entry template are used for the policy, how mapping is configured between form template fields and document class properties, and any special property settings or security features. Document policies are available if FileNet P8 eForms integration has been configured.

See also form policy.

DoD

Department of Defense.

DoD transfer

Capability to transfer records from one Records Manager system to another. The records are exported to a standard DOD defined schema. On import, the schema is used to map the fields to the existing records fields.

domain

See FileNet P8 domain.

domain controller

In a Windows network, the machine that manages user access to machines and shared resources in the domain.

dynamic hold

Refers to the ability to specify conditions for entities to be placed on hold. For example, you might want to put all records that include the name BrightTours on hold. A scheduled Hold Sweep process determines if any entities meet the conditions of the holds. If so, the hold is applied automatically. Also called Conditional hold.

Return to Top

E

EAI

See Enterprise Application Integration.

eBusiness Framework

Infrastructure and platform software for building eBusiness B2B (Business to Business), B2C (Business to Customer), and B2E (Business to Employee) applications.

eForms (FileNet P8 eForms)

Allows you to add intelligent form documents to your FileNet P8 system. FileNet P8 eForms includes eForms Designer, a browser fill environment, and form-based Launch Step and General Step processors. FileNet P8 eForms is available if FileNet P8 eForms integration has been configured.

Enterprise Application Integration (EAI)

A FileNet P8 optional component, EAI technologies (called connectors) serve as the common interface between dissimilar applications using the same data and processes.

Enterprise Manager

A Microsoft Management Console (MMC)-based tool that provides access to most of Content Engine's administrative functionality.

entity

A generic term that can apply to a record object or an RM container.

entry template

A wizard that steps a user through adding a document, folder, or custom object. An entry template, which is created using the Entry Template Designer, can provide default values for the destination folder, properties, and security. The entry template can hide some pages in the add wizard, and the template can launch a workflow when the new item is added.

event

In FileNet P8, an event is a change in the metadata that, when specified in an event subscription, initiates an event action. For example, an event could be the addition of a document to a folder. The event action might be to declare that document as a record. In Records Manager, an event is used to trigger the start of the disposition process or, in the case of vital record review, to trigger the vital review action. It is a system-level action that has occurred during the processing of a workflow. For example, an event occurs when a workflow is created or when a step processor begins processing a work item. See event trigger, event action, and event subscription.

event action

A script, object, or workflow that Content Engine runs, as defined in a subscription or event subscription. Event actions can be used to launch workflows and to declare records.

event log

A database table that contains information about certain system-level events related to work item processing.

event logging

An optional feature used to log the occurrence of certain system-level events related to work item processing. For example, log a message when a work item is created or when a step processor begins processing a work item.

event subscription

In FileNet P8, a definition of conditions required to initiate an event action. An event subscription specifies the class, to which the subscription applies, the event that must occur (such as adding a document or changing a property value) and the event action that is triggered. See event action.

event trigger

Also called a trigger or a Records Manager event. An event that triggers the start of the disposition process. You create event triggers in Records Manager. Each event trigger has a condition. When an event occurs that meets the condition, Disposition Sweep marks the entity as being ready for disposition. There are several types of event triggers you can configure in Records Manager: internal events, external events, recurring events, and predefined date events. In addition, you can define a calendar date in the disposition schedule to be the cut off trigger.

exception state

A lifecycle property that determines whether a document can be promoted or demoted from one lifecycle state to another. See also reset and lifecycle policy.

export manifest

A temporary container for references to all the objects to export. It is represented as the Export Manifest node in an object store in the Enterprise Manager tree view.

exposed fields

System and data fields in a roster, queue, or event log that have been made available for searches and sorting. Use exposed fields in a search filter, when defining an index, and when logging information to the event log.

expression

A set of symbols combined to represent a single value. For example, a + b = c.

external document

See content-less document, custom object.

external event

An event that occurs outside the system, but can directly impact the cut off and disposition of entities. For example, there might be a change in administration that could delay disposing of unnecessary or old records. External event triggers are similar to predefined date events, except that the date field is not a required property, which means you can create the trigger without knowing the future date of the event.

external reference

A document with content consisting of a URL or a UNC path (a link to another location).

Return to Top

F

file storage area

A permanent storage area managed by the Content Engine server. A file storage area retains document content in a Distributed File System (DFS) or a Windows NTFS file system. You can manage a file storage area through Enterprise Manager.

FileNet Content Services

Server software and utilities for document management and version control. Also referred to as Content Services or CS.

FileNet Image Services

Server software and utilities for imaging, document storage and retrieval. Also referred to as Image Services or IS.

FileNet Open Client

A FileNet application that provides Web browser-based access to Content Services and Image Services libraries. Open Client uses Microsoft's .NET technology.

FileNet P8 domain

A logical grouping of physical resources (object store databases, full text index areas, file storage areas, and content cache areas) and Content Engine servers that provide access to those resources. Each resource, and each Content Engine server, belongs to one and only one domain. A Content Engine server can access any resource in its domain, but cannot access any resource that lies outside of its domain.

FileNet Web Services

A FileNet application that provides Web browser-based access to Content Services and Image Services libraries. FileNet Web Services runs on Microsoft Internet Information Services (IIS)-based Web servers.

file plan

In Records Manager, a file plan is a container hierarchy that defines the organization of records. The file plan also determines the security and disposition of contained entities. Entities can inherit security and disposition from the parent container in the file plan. Also called classification scheme.

file plan object store

An object store that hosts a file plan. The administrator must create an FPOS by importing the appropriate data models and performing other configurations. Once the FPOS is configured, the records manager can create the file plan on it.

filter conditions

Restrictions placed on a search, for example to identify specific workflows.

fixed storage area

A file storage area that has a connection to a third-party fixed content system providing additional storage capacity and security. This connection is provided by a Content Engine object called a fixed content device.

folder

A container for documents and subfolders.

folder class

A template for folders.

form data

Data that exists in a filled-out form derived from an ITX form template. Form data can be manually or automatically saved to an object store. Form data is available if FileNet P8 eForms integration has been configured.

See also content and form template.

form data document class

Used when specifying how form data is to be saved. This document class is available if FileNet P8 eForms integration has been configured.

See also document class and form data.

form data entry template

An entry template that specifies how form data will be added to an object store. A form data entry template can be associated with document and workflow policies. This template is available if FileNet P8 eForms integration has been configured.

See also entry template and form data.

form policy specification document class

A document class used with document and workflow policies. This document class is available if FileNet P8 eForms integration has been configured.

See also document class, document policy and workflow policy.

form proxy custom object class

A custom object class used to link form data to form template policies. This object class is available if FileNet P8 eForms integration has been configured.

See also form policy, form data, and document class.

form template

An xml-based document that contains the framework, intelligence, and graphic and text elements of a form created by the form author in eForms Designer. Form templates are available if FileNet P8 eForms integration has been configured.

See also document class, document policy, and workflow policy.

form template document class

A document class used when defining form templates for document policies and workflow policies. This document class is available if FileNet P8 eForms integration has been configured.

See also document class, document policy, and workflow policy.

form policy

A file or specification that determines how the form is presented. There are two types of policies: document policy and workflow policy. Form policies are available if FileNet P8 eForms integration has been configured.

FPOS

See file plan object store.

frozen version

A document version whose custom properties cannot be edited.

FRC

Fleet Readiness Command.

full-text indexing

Method used to create and maintain an index catalog of text-based content and string properties stored in an object store's database.

Return to Top

G

generic class

A class with no special behavior built in. The administrator can customize, save, and query a generic class.

Global Configuration Database (GCD)

The Content Engine component that stores global data that defines the FileNet P8 domain. Data stored in a GCD includes information about: object stores, file storage areas, content cache areas, index areas, and other domain resources. The GCD also stores and manages the security descriptors for all accounts provided by the authentication provider.

global property

A property template that has not been assigned to a class.

Global Unique IDentifier (GUID)

A Microsoft identifier that is compatible with DCE Unique Universal Identifiers (UUIDs). Content Engine assigns a unique GUID to every object in the system. Usually, no other object in the world can have the same GUID.

group

A set of accounts that can represent individual users, computers, and, depending on the authentication provider, other groups.

guest

An optional account for anonymous logins.

GUID

See Global Unique IDentifier.

Return to Top

H

hierarchical choice list

A grouping of choice list values usually presented as cascading menu options.

hold

A method of stopping the normal disposition of a record, usually because of court cases or investigations. See disposition hold.

hold sweep

A daemon process that finds records meeting the conditions needed to place them on hold.

Return to Top

I

index area

A storage area that contains one or more indexes, which are used to perform full-text searches against documents in an object store.

in process version status

The status of the most recently checked-in minor version. Older minor versions have the status Superseded.

Inbox

A folder that contains work (tasks) assigned to a specific user. The Web application determines user access to the Inbox:

  • Workplace users access the Inbox from the Tasks page.
  • FileNet Web Services users access the Inbox as a folder in Personal Work Manager.
  • FileNet Open Client users access the Inbox from the Process page.

index content

To store the text-based content of documents in a database for content-based retrievals (CBR), when enabled by the file storage area property Indexed.

inheritable depth

The maximum number of levels through which a permission can be inherited. There are three possible settings: "This object only," "This object and immediate children," and "This object and all children."

inherited ACE

A non-editable ACE whose source type is Inherited. Permissions placed on the object by a security parent are labeled Inherited by Enterprise Manager's security editor.

initiating attachment

An attachment used to launch a workflow.

instance

A particular occurrence of an object. For example, a document is an instance of the document class.

interim transfer

Temporarily transfers records to some other location. The original record remains in the RM system until some final disposition occurs, See interim transfer workflow.

interim transfer workflow

This ensures that the home location of a physical entity and location of an electronic entity is changed to the specified location at the end of the retention period of a phase. The Records Manager must approve the interim transfer of each entity. Before approving the interim transfer of a physical entity, the Records Manager must ensure that the physical entity has been manually transferred to the new location. The interim transfer workflow launches when you initiate disposition.

internal event

An event trigger that refers to a change in an entity’s metadata. These events are triggered automatically when the specified condition is fulfilled. For example, the system could track when a volume closes and trigger cut off and disposition at that time. An internal event acts on the type of entity you specify in the aggregation field. See event trigger.

IS

See FileNet Image Services.

isolated region

A logical subdivision of the workflow database that contains both transferred workflows and the data for all active workflows. Work cannot be shared across or moved between isolated regions. Use isolated regions to separate groups of users as appropriate for the organization.

Return to Top

J

J2EE platform

A standards-compliant application server environment that enables products to run on any system that supports Java™ 2 Enterprise Edition (J2EE), and facilitates development of multitiered, scalable, and reliable applications. J2EE enables Content Engine to support a variety of operating system, directory service providers, application servers and database servers.

Return to Top

L

launch

To begin the process specified in a workflow definition.

launch processor

A step processor designed specifically to complete the launch step of a workflow.

launch step

The first step in a workflow. In Process Designer, the launch step is automatically placed on the main workflow map and cannot be deleted or copied.

LDAP

See Lightweight Directory Access Protocol.

legal discovery

In law, discovery is the pre-trial phase in a lawsuit in which each party can request documents and other evidence from other parties or compel the production of documents and other evidence using the legal system.

level

A predefined collection of rights which simplify applying and administering individual rights. For example, the Major Versioning level for documents includes those rights required to allow the user to perform the various tasks required to create a major version of a document.

lifecycle

Stages a document passes through in its lifetime (such as draft and review). Lifecycle and current stage are document properties.

lifecycle action

A script or object executed when a document changes state as defined in a lifecycle policy.

lifecycle policy

Definition of the document's states. The policy also identifies the lifecycle action that executes in response to the state changes.

Lightweight Directory Access Protocol (LDAP)

A client-server protocol used to connect to a repository of information. Both Content Engine and Process Engine use LDAP in certain authentication scenarios.

link

As a verb, to establish a relationship between a workflow definition and a document or document class. Linking a document class to a workflow definition enables a user to launch the workflow from any document belonging to that class. Linking a document to a workflow definition enables a user to launch the workflow from that document.

As a noun, a relationship between a workflow definition and a document or document class.

Return to Top

M

magazine view

Format for document lists in Workplace in which properties appear in a phrase (such as, " Created by <property> on <date>").

major version

A document that has been released. Typically, a major version's security makes the document available to a wide range of users.

map

See workflow map.

marker record

The name of a class used for physical records in Records Manager.

maximum instructions per transaction

The number of system instructions per transaction that the InstructionSheetInterpreter (ISI) process will execute before temporarily storing the work item in the InstructionSheetInterpreter queue.

maximum operations per transaction

The number of database operations per transaction that the InstructionSheetInterpreter (ISI) process will execute before temporarily storing the work item in the InstructionSheetInterpreter queue.

metadata

Data that describes other data. Content Engine stores metadata, which describes classes and properties, in the object store's database.

Metadata Explorer

A design tool you can load from the Properties tab of most Enterprise Manager property sheets. The Metadata Explorer presents a hierarchy of classes and properties that lets you view the entire architecture of Content Engine.

Microsoft Management Console (MMC)

A general-purpose management display framework for hosting snap-in administration tools including Enterprise Manager.

milestone

A designated point in a workflow, used to track the progress of the workflow. Each milestone is defined to occur before or after a specified step. When the running workflow reaches a milestone, the message defined for that milestone is written to a log file. Milestone history can be viewed in the step processor or Process Tracker application.

MIME

See Multipurpose Internet Mail Extension.

minor version

A document version that has not been released. Typically, a minor version's security makes the document available only to the authors and reviewers.

MMC

See Microsoft Management Console.

Multipurpose Internet Mail Extension (MIME)

An industry standard format for content, especially Internet mail. Content Engine provides a document property called "MIME type." The value for MIME type identifies a document type (such as text, XML, or application).

Return to Top

N

naming pattern

Specifies rules used to automatically generate names when new containers are added to a file plan. For example, a container naming pattern can be used to automatically ensure that each new container has a unique category ID. Naming patterns consist of one or more pattern levels that apply to an entire level in the file plan hierarchy (think of a tree diagram of the file plan). See record pattern.

NARA

National Archives and Records Administration.

node

An object in the tree view that serves as a container to hold related objects. A node appears with an icon and name that identifies the type of objects the node contains.

non-exposed fields

System and data fields that are part of a work item but are not available for searches and sorting.

Return to Top

O

object

The programmatic definition of an entity such as a folder or document. An object has properties, methods, and events (which trigger actions).

Object Instance Identifier (OIID)

A globally unique identifier used to identify and locate an object saved in an object store.

object store

A set of services provided by Content Engine to access and manage documents and other objects. An object store resides in a FileNet P8 domain, which can contain many object stores.

OCA

Original Classifying Authority.

OIID

See Object Instance Identifier.

operation

A function in an application (step processor or automated process) that processes work items in a queue. The operation is defined as a property of the queue and includes as parameters any data required for input from or output to a work item.

owner

A user designated in the "Owner" property of an object. Certain extended security access rights are granted to the owner, even beyond full control.

offset

An optional time gap between the event trigger and cut off.

Return to Top

P

parent class

See superclass.

participant

A user or group assigned to process work at one or more steps in a workflow.

permanent record

A record that has been identified as having sufficient historical or other value to warrant continued preservation by the organization beyond the time it is normally required for administrative, legal, or fiscal purposes.

persistence

A property attribute. Persistent values are saved to a relational database and can be retrieved during queries. User-defined properties are usually persistent.

Personal Work Manager

(FileNet Image Manager only)

A FileNet Web Services or Open Client application used to locate and open items in active workflows.

phase

See disposal phase.

physical record

Metadata describing a physical object like paper, tapes, CDs, and so forth.

PJAC

See Process Java Applets and Connectivity.

policies

See security policy and lifecycle policy.

Predefined date event trigger

In Records Manager, an external event trigger with a required date field. An example of a predefined date is New Years Day January 1st.

PRO data model

A data model that fulfills the Public Record Office requirements for electronic record management.

Process Administrator

A program used to locate, edit, and manage running workflows.

Process Analyzer

A FileNet expansion product (optional component) that supports monitoring and analyzing business processes.

Process Configuration Console

A program used to configure the workflow database and environment.

Process Designer

A program used to create or modify workflow definitions.

Process Engine

The FileNet P8 component that is responsible for workflow execution and management.

Process Java Applets and Connectivity (PJAC)

(FileNet Image Manager only)

The FileNet Image Manager component that enables FileNet Web Services, FileNet Open Client, and custom applications to interface with Process Engine.

Process Service

Back-end Process Engine software and utilities that provide workflow functionality.

Process Simulator

A FileNet expansion product (optional component) that simulates workflows by performing "what-if" scenarios, providing business analysts with important information that helps streamline business processes.

Process Task Manager

A program used to manage workflow-related processes on various FileNet P8 Platform servers.

processor

A Java function that accepts arguments as input and operates on the value of the component to which it is connected when it is rendered or to subcomponents being assembled into the component for rendering.

prog ID

Program identifier. A property that specifies the COM object whose code executes when the event occurs.

promote lifecycle

An action taken on a document that moves it forward to its next lifecycle state. See also lifecycle policy.

promote version

An action that changes a minor version into a major version and sets its status to Released. Promotion sets the previous major version's status to Superseded.

property

Descriptive information associated with an object. All objects have properties you can view or modify using a property sheet. Properties have values; for example, a Customer Name property might have the value "John Smith." See also property template, custom property, or property tag.

property map

A property available through the Workflow tab on the properties sheet for an event subscription. This identifies the workflow data fields designated as launch step parameters in the workflow definition.

property sheet

An Enterprise Manager dialog box made up of tabbed pages, also called property pages, that make available such things as the object's descriptive information, properties, and security settings.

property tag

A shorthand way to call the getProperty function for a component identified by a keyword.

property template

A template for creating one or more custom properties that can be assigned to one or more classes.

publish

To create a read-only copy of a document in an object store. Publishing makes the publication document available to a different audience and can translate the content to a different format.

publish template

A publish template determines the properties, format (such as HTML), and storage location of the publication document. The template determines whether the publication document is replaced or versioned when it is republished.

Publishing Designer

An application used to define publish templates.

publishing handler

A component of Enterprise Manager and uses the publishing framework to produce HTML and PDF files. It replaces the former Publishing HTML plug-in and PDF plug-in.

publishing style template

A set of translation and formatting rules applied when a document is published.

Publishing Style Template Manager

The application used to define publishing style templates.

Return to Top

Q

queue

A workflow database table that holds work items. There are four types of queues: user queues, work queues, component queues, and system queues.

Return to Top

R

RDOS

See record-enabled-document-object-store.

realm

The collection of all user accounts and group memberships available to the FileNet P8 domain. Realms are created, maintained, and authenticated by the authentication provider and are thereafter read and utilized by a FileNet P8 domain.

record

A file that references and contains information about another electronic file (document) or a physical object. A record is created to place the document or physical object under corporate or governmental control. The record specifies how the document or object is to be stored, accessed, and, optionally, disposed of. A record is metadata.

record-enabled document object store (RDOS)

An object store that has been configured to allow record declaration. Electronic documents on an object store that is not configured as an RDOS cannot be declared as records. In ecm_help and in the Records Manager Installation and Upgrade guide, RDOS is called ROS. For the Records Manager courseware, the word document was added to emphasize the distinction between the RDOS, in which documents are stored, and the FPOS, in which record objects are stored. Do not confuse the RDOS and the FPOS.

record category

The top level record container in a records management file plan.

record folder

A container below the category level for records in a file plan.

record pattern

Used to constrain the names of new records to a pattern that is associated with the container. It is similar to a naming pattern except that it does not generate names, only constrains them. Users must be careful when adding records to a container with a record pattern because the pattern does not allow declaration if the record name is not compliant with the pattern. Care must be exercised when using record patterns with automated declaration.

record types

A categorization of records that has a unique disposition schedule. Record types are used when a group of records existing in a record category or folder needs to have a disposition schedule that is different from the one currently associated with the container. Usually, record types are used when some records must be destroyed before the rest of the records in the container. If a record type has a longer retention than other records in the container, the container is placed on hold until all the records are ready for disposition.

records administrator

The records administrator is a Records Manager security role, the duties of which include setting up security, object stores, document and record classes, and metadata.

records management professional

A person responsible for managing records.

records management system

Any system for managing records. In the Records Manager courses, a records manager system includes the file plan, disposition schedules, naming patterns, record classes and properties, locations, workflows, and anything else that can be created for records management.

Records Manager

IBM FileNet Records Manager. An add-on product to the FileNet P8 system that has special record management capabilities. A records manager (lowercase) is a Records Manager security role, the duties of which include managing records, holds, and disposition actions.

records reviewer

A Records Manager security role (in the PRO data model), the duties of which include reviewing entities that are ready for disposition, declaring records, and performing basic record-related operations, such as filing or copying records. In the DoD and Base data models, this person is called a Privileged User.

records user

A Records Manager security role, the duties of which include declaring and viewing records.

recurring event

Events Events that recur automatically after a specified time interval. They are used to trigger periodic reviews of vital records. For example, a recurring event called Monthly review with a specified frequency of one month can be created to cause a monthly review of the associated entity.

See also vital records.

region layout

The customizable areas or frames (e.g., notice and banner sections) that surround the eForm in a form policy. Available if FileNet P8 eForms integration has been configured.

released version status

The most recently checked-in major version. A major version is typically an approved document of record. Only a major version can have the status Released, and a version series can have only one released version. Older major versions have the status Superseded.

request forwarding

Enables data requests to be serviced by a site that is geographically closest to the object store database.

reservation version status

The status that indicates a checked out, but not yet checked in, version of a document.

reset

An action taken on a document that returns the document to its original lifecycle state. See also lifecycle policy.

response

A choice that a user selects from a predetermined list when processing a work item. A response can determine the route that work will subsequently follow.

result set

A visible subset of items, such as workflows or documents, returned by a search. The user can set the size of the result set.

retention period

At a high level, how long to keep a record. In Records Manager, a part of a disposition phase that specifies the length of time between cut off and the phase action. A disposition schedule can have several phases of retention, each with its own retention period. Total retention time is equal to the retention period of the final phase of disposition. The retention period is always relative to cut off, not to the end of a prior phase. For example, if a review phase is set for one year after cut off and the second phase is set for a year after the review, then the phase retention period for the second phase is two years (after cut off).

retention schedule

See disposition schedule.

rights

Rights are security permissions at the lowest, most granular level. Objects include the rights appropriate to them. For example, document classes include the "create instance" right, whereas folder classes include a "file in folder" right. Rights can be either allowed or denied. Individual rights are grouped together, or "mapped," into levels for easier and more meaningful application while using Enterprise Manager's security editor. For example, the View Content level on a document includes both the View Content and View Properties rights.

root class

A class whose parent class is identified as "None" on its property sheet. Enterprise Manager's root classes are the document class and those left-most classes exposed under the Other Classes node (such as the Annotation, Choice List, and Folder nodes). You can subclass and modify most root classes when you configure an object store.

root folder

The top-most node in a tree view. In Enterprise Manager, an object store's Root Folder holds content, which consists of folders, documents, and custom objects.

ROS

Record-enabled object store. See record-enabled document object store (RDOS).

roster

See workflow roster.

route

A path between two steps in a workflow definition.

Return to Top

S

scenario

A distinct, plausible projection of how a business process described in a workflow definition might occur. The purpose of scenario planning is not to predict the future, but rather to show how different forces can impact the process and produce various outcomes.

SCG

See classification guide.

schema

See database schema.

screening

A workflow that enables the reviewer to screen an entity before executing workflows associated with its disposition phases. Screening is optional and can be specified when a disposition phase is created.

script

A set of commands in a scripting language (such as VBScript or Jscript). Content Engine users add scripts to common functions to customize and enhance their applications.

Search Designer

Java applet used to create stored searches and search templates.

search template

A file created in Search Designer that is run from either the Workplace Search or Browse page. Using the search template usually prompts the Workplace user to enter or change values and then displays a list of the documents that meet the search criteria.

security

The rules that allow and limit access to computers and data.

security categories

Additional hierarchical security markings used by Records Manager.

security editor

Enterprise Manager's security interface that allows viewing and editing of an object's security. The security editor is embedded into property pages titled Security, Default Instance Security, and Template Security.

security parent

A folder configured to propagate permissions to documents contained in the folder.

security policy

A set of security templates, which provide a way to apply default security settings as you add objects.

security template

A set of security settings that can be applied to a document, folder, or custom object. Security templates are components of security policies. For documents, the versioning security templates supply permissions for each version status. Applications can apply application security templates.

server instance

An individual J2EE application server instance. Multiple server instances (each running in their own JVM) can be hosted on a single physical server (this is common when large multi-CPU servers are used).

shared folder

A directory or folder to which network users can connect. File storage and content cache areas must be located in a shared folder.

simple search

An ad hoc search created by a Workplace user for one-time execution and a list of the documents that meet the user's search criteria are displayed.

simulation

The execution of a scenario. A mimicking of the operation of a real system, such as a claims processing application, in a computer.

Simulation Animator

A program used to view a workflow simulation graphically.

Simulation Console

A program used to manage scenarios and simulations.

Simulation Designer

A program used to create or modify scenarios that simulate running workflows.

single value

A property attribute that restricts the property to only one value.

single-level versioning

A document version series containing only major versions.

site

Represents a geographical location where resources are well connected via a fast, reliable LAN. Object stores, storage areas, content cache areas, index areas, and virtual servers are all associated with an individual site.

site preferences

Configuration settings that affect Workplace appearance, behavior, and connectivity. Administrators set site preferences using the Site Preferences application. Non-administrative users can set personal preferences, which override some site preferences.

snapshot interval

Defines how often statistical samples or "snapshots" are taken of the work in progress.

source permission type

Used in Enterprise Manager's security editor. A value specifying the source of a permission, with four possible values: Direct, Default, Template, and Inherited. Client-created permissions are always set to Direct. Template and Inherited permissions are read-only and cannot be removed. Default permissions are editable and removable.

spoilation

The willful or accidental destruction of a record prior to its scheduled destruction.

step

A stage in a workflow where a distinct, well-defined action is performed. Each step on a workflow map represents a specific activity or task in the business process described by the map. For example, in insurance claims processing, "verify account number" and "calculate deductible" could be individual steps. A workflow consists of two or more steps.

step map

In a workflow policy, allows property mapping between form template cells and workflow data fields for workflow policies. Step maps are available if FileNet P8 eForms integration has been configured.

step processor

An application that provides the information and resources a participant needs to complete a step in a workflow. When a participant opens a work item at runtime, the step processor displays the necessary instructions, attachments, current field values, response options, or other resources. In a workflow definition, the workflow author specifies the step processor to use for a particular step.

storage policy

Provides mapping to specific physical storage areas and is used to specify where content is stored for a given class or object with content (for example, a document).

stored search

A file created in Search Designer that is run from the Workplace Browse page. Using the stored search displays a list of the documents that meet the search criteria.

subclass

A class that inherits properties and security from a parent class, also called a superclass.

submap

A workflow map that is called from another map in the same workflow definition.

subscription

A method that sets up the conditions required for an event action to take place and the class, object, instance or workflow the event acts upon.

superclass

A class whose properties are inherited by its subclasses. For example, custom document classes inherit properties from their superclass (the supplied document class).

superseded version status

A major or minor version that is not the most recent.

supplemental marking

Additional non-hierarchical security markings used by Records Manager.

symmetric encryption

An encryption algorithm that requires the same key for encrypting and decrypting.

synchronous

An event that occurs at regular intervals. When using synchronous event actions in subscriptions, the subscription processor blocks further processing until the action completes and returns. The action runs in the same transaction as the originating activity on the target object. If the action fails, the transaction rolls back. See also asynchronous.

system field

A system-defined workflow field. You can make a system field visible at a step, use it to determine conditional routing, and expose it (that is, make it available for searches and sorting). A system field value cannot be edited.

system function

The FileNet-provided functions that perform general flow- and logic-control instructions commonly used in workflow processing. Examples are Begin Timer and Invoke (a Web service). Process Engine software executes all system functions.

system queue

A queue holding work items that are undergoing or waiting for processing by Process Engine. There are two system queues: Delay and InstructionSheetInterpreter (ISI).

System State

A set of data specific to the Windows 2000/2003 operating systems. For all Windows 2000/2003 systems, the System State includes the registry, the boot files, and the COM+ class registration database. The System State for a Windows 2000 server includes the Certificate Services database if the server offers Certificate Services. A Domain Controller adds the SYSVOL directory and the Active Directory services to the basic System State components.

Return to Top

T

taskpad

A view in Enterprise Manager's details pane that provides a set of icons that represent tasks. Clicking a taskpad icon initiates an action or starts a wizard that walks you through an administrative function.

template

A pattern or mold used to create objects or processes. For example, a property template defines a property that can be associated with one or more document classes. See also: application security template, entry template, property template, publish template, publishing style template, search template, security template, versioning security template.

template ACE

A non-editable ACE whose source type is Template. Permissions placed on the object by a security policy are labeled Template by Enterprise Manager's security editor.

tracker

A participant who is designated to monitor the progress of a workflow. If necessary, the tracker can modify various step and workflow properties.

Tracker (application)

A FileNet-provided application used to monitor, manage, and modify the workflows to which you have been assigned as a tracker.

transfer

The act or process of moving records from one location to another, especially from the location the record is used to Agency storage facilities or FRCs or NARA.

transfer mapping file

A file that maps Content Engine property names to XML property names that the Records Manager Transfer tool includes in an XML file when importing or exporting Records Manager entities. When you transfer records and record folders while they are still active, the transfer mapping capability tracks the entities by the organizations receiving and originating the entities.

transformation plug-in

The Content Engine software that translates a source document to a format such as HTML as specified by a style template.

tree view

A hierarchical list of objects typically shown in the left pane with a list view in the right pane. Selecting a node in the tree view displays content related to the selected node in the right pane.

trigger

See event trigger.

Return to Top

U

unassigned work

Work that does not require completion by a specific participant but can instead be completed by any one of a number of users or by an automated program. The concept is similar to a stack of typing projects to be completed by the workers in a typing pool. At runtime, unassigned work is routed to a specified work queue; a user or program with access to that work queue can open and complete the work contained within.

UNC

See Universal Naming Convention.

unfiled document

A document that is not contained in any folder. Users can search for unfiled documents and file them in folders.

Universal Naming Convention (UNC)

A convention for specifying directories, servers, and other resources on a network, using two slashes // or backslashes \\ to indicate the name of the computer, and one slash to indicate the path or directory levels within the computer, in this format: //computer/directory.

user queue

A queue that holds work items waiting to be completed by a user rather than by an automated process. Each user's queue displays as his or her Inbox.

Return to Top

V

Verity collection

Contains full-text indexing information. Each Verity collection is a member of only one index area.

version

The properties and content associated with an instance of a document in an object store or a Content Services library. A version is created each time a document is checked out, edited, and checked in. A document version can be designated as a major version or a minor version.

version series

All versions of a document. A version series from which one or more versions have been deleted is said to be a sparse version series.

version status

The state of a version. Minor versions have the status In Process, Reservation, or Superseded. Major versions have the status Released, Reservation, or Superseded.

versioning security template

An ACL associated with a particular document version state. Versioning security templates can define ACLs for the four possible version states: Reservation, Released, In Process, or Superseded. A versioning security template is applied through a security policy. See also application security template.

view

A configurable data display. For example, an administrator can select which properties to display in Workplace document lists.

virtual server

The logical service point that Content Engine clients interact with. A virtual server can map to a single independent server instance or to a set of server instances.

vital records

Essential business records needed to meet operational responsibilities for an organization. Vital records are subject to periodic review. Whenever a recurring review event occurs, the vital records review workflow associated with the event is launched.

volume

A volume serves as a logical subdivision of a record folder into smaller and more easily-managed units. A volume has no existence independent of the folder. A record folder (with the exception of a box) will always contain at least one volume, which is automatically created by the system when a record folder is created. A volume will be of the same type as its parent record folder (electronic, physical, or hybrid) and can contain the same type of records as its parent. However, a volume cannot contain a subfolder or another volume. A record cannot be filed directly into a folder. Instead, it goes into the currently open volume. Volume names are based on the folder name with an automatically generated volume suffix (for example <folder name>-00001). When you create a new volume, the latest current volume is automatically closed. When records are added to folders, they are automatically filed in the currently open volume. You can reopen a volume after it is closed.

vwlog

A Process Engine-based administration utility used to perform maintenance tasks related to the logging and statistics subsystem. You can use vwlog to delete log records within a specified interval, transfer log records from the database to a comma-separated (.CSV) file, or coalesce statistics records within a specified interval.

vwtool

A Process Engine system support and administration program used to gather system information and analyze and modify various Process Engine components. It is intended primarily for use by FileNet support staff.

Return to Top

W

WebDAV

Web-based Distributed Authoring and Versioning. A technology that allows users to create, change and move documents on a remote server, typically a Web server.

Web client

An application that accesses object stores and workflows through a Web connection. Web clients include Workplace, Microsoft Office integration, and WebDAV.

wizard

An interactive utility within an application that guides a user through each step of a particular task, such as creating a new object store.

work class

See workflow definition.

work item

A single unit of work, the smallest component of work to be done in a workflow. It is a collection of both data and references to the system information necessary for processing the data. A work item is transitory; once it has been processed as required, it ceases to exist.

work object

See work item.

work queue

A queue holding work items that can be completed by one of a number of users, rather than by a specific participant, or work items that can be completed by an automated process. The system administrator defines work queues using Process Configuration Console.

workflow

Work performed by two or more individuals or resources, serially or in parallel, to accomplish a business process or task. In FileNet P8, workflows are automated and defined by workflow definitions and managed by the Process Engine. FileNet Records Manager includes several workflows: screening, cut off, and the disposition workflows.

workflow author

A person who creates workflow definitions that specify the step-by-step process, participants, attachments, data fields, and routing logic for a business process.

workflow database

Contains the workflow rosters, work queues, and other database tables necessary for work item processing and related activities, such as event logging and statistics collection.

workflow definition

An electronic representation of the activities and resources required to accomplish a business process. A workflow definition acts as a processing template that Process Engine uses each time the workflow runs, routing the work to the specified participants, along with data, attachments, and other information they will need to complete the activities.

workflow fields

A collective term for the data fields and system fields associated with a single workflow.

A field is a workflow property, which means that it can be used in one or more steps of a workflow. When the workflow is running, a value set at one step will be available in (and can be changed in) subsequent steps that use the same field. The value of each field in a workflow is limited to the current instance of the workflow; each time the workflow runs, the values in each field can be different.

workflow group

A collection of users who perform a particular job function in a workflow; for example, claims adjustors or supervisors. A workflow group consists of one or more users or groups.

workflow map

A graphical representation of a workflow that shows the sequences of steps needed to complete the business process. A step represents a specific activity; routes between the steps indicate one or more possible processing paths.

workflow policy

Used to map form template fields to workflow step element parameters. Workflow policies are available if FileNet P8 eForms integration has been configured.

workflow roster

A database table that stores the current location of and other information about all workflows. Workflow rosters provide Process Engine with an efficient way to locate specific workflows.

workflow subscription

An association between a class or an object and a workflow definition. The subscription can specify which events trigger an automatic launch of the workflow or if a user must launch the workflow manually. For example, an expense approval workflow could launch automatically when a user adds a new expense report to an object store.

Workplace

Web application for users. This application allows users to add documents and other items to an object store, to browse and search for items, and to run workflows. If allowed by the preference setting, Workplace users can also start the designer applications.

Return to Top

X

XML classifier

Content Engine function that identifies a document type by examining the contents of XML documents. The XML classifier applies the script contained in the XML property mapping script to determine property mappings.

XML property mapping script

A script that maps XML values in an incoming document to a target document class.

XSL script

A script written in Extensible Style sheet Language. XML property mapping script objects contain XSL scripts to perform automatic document classification.

Return to Top

Z

zeroclick

This term describes the ability to automatically declare records without user involvement. Examples:  A record can be declared with an event action (for instance, when a document is added to a FileNet P8 folder, it is declared as a record). A record can be declared as part of a workflow. IBM FileNet Records Manager can also declare e-mail messages as records.

Return to Top