Glossary

This glossary includes terms and definitions for IBM Content Cortex.

The following cross-references are used in this glossary:

See refers you from a term to a preferred synonym, or from an acronym or abbreviation to the defined full form.
See also refers you to a related or contrasting term.

To view glossaries for other IBM products, go to www.ibm.com/software/globalization/terminology External link opens a new window or tab (opens in new window).

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

A

access control entry (ACE): An entry in an access control list (ACL) that contains a set of access rights, for a particular grantee, such as a machine, a user, or a group, and whether the right is allowed or denied. An ACE can also contain information about the source, whether directly applied, inherited, or from a security template.
access level: In computer security, the level of authority a user has while accessing a secured file or library.
access right: A security setting that controls access to the objects in an object store or workflow.
ACE: See access control entry.
adapter: An intermediary software component that allows two other software components to communicate with one another.
aggregation: A setting in an internal event trigger that determines which type of product entity is affected by the disposition action.
alias ID: Identification that enables users to perform queries across object stores. Content Platform Engine uses alias IDs to identify classes and properties that are semantically the same.
alias name: A name that is used to represent all or part of a command.
alternate retention: A variable retention period defined within one records management disposition schedule. The alternate retention is based on property values.
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.
AND-split: A step in the workflow where there are multiple outgoing routes that the workflow can take simultaneously. An AND-split step must have a corresponding AND-join step.
annotation: An added descriptive comment or explanatory note.
application security template: A type of security template that can be applied by custom applications. See also template, versioning security template.
association property: A property in a class that describes an association to another class.
asynchronous: Pertaining to events that are not synchronized in time or do not occur in regular or predictable time intervals. See also synchronous.
asynchronous event: 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.
attachment: A file that is attached to an email message or other electronic document.
attachment command: An action that appears in a toolbar, such as Add New, or Assign, when an attachment is configured with a workflow policy.
attribute: A property, quality, or characteristic whose value contributes to the specification of an element or program function. For example, "cost" or "location" are attributes that can be assigned to a resource.
authentication: A security service that provides proof that a user of a computer system is genuinely who that person claims to be. Common mechanisms for implementing this service are passwords and digital signatures.
authorization: The process of granting a user, system, or process either complete or restricted access to an object, resource, or function.
auto-destroy: To permanently delete or destroy records without the use of a workflow. The record removal is immediate when it has reached the end of the retention schedule.

B

bootstrap: A small program that starts a computer by loading the operating system and other basic software.
box: A software object that provides a mechanism to model physical entities that contain other physical entities.
branch: A set of parallel steps in a workflow. A workflow step is a node in a branch.

C

catalog: To specify the record class and file plan location when declaring a record.
category: A container that groups a set of related records within a file plan.
CBR: See content-based retrieval.
charge in: To return a physical record to its home location.
charge out: To check out and track a physical record.
check in: In certain software configuration management (SCM) systems, to copy files back into the repository after changing them.
check out: In certain software configuration management (SCM) systems, to copy the latest revision of a file from the repository so that it can be modified. 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: In object-oriented design or programming, a model or template that can be used to create objects with a common definition and common properties, operations, and behavior. An object is an instance of a class.
classification: A process for automatically acquiring document properties from the document content or another source.
classification scheme: See file plan.
classified: Pertaining to a record that has special access restrictions in addition to normal record security.
class inheritance: A feature that allows a subclass to inherit all of the properties of a superclass, which is its parent in a class hierarchy.
cleartext: A string of characters sent over a network in readable form. It might be encoded for the purposes of compression, but it can easily be decoded.
clone: An identical copy of the latest approved version of a component, with a new unique component ID.
component: A reusable object or program that performs a specific function and works with other components and applications.
component queue: A queue holding work items that can be completed by an external entity that interacts with the workflow. See also queue.
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: An object that identifies a specific workflow system and isolated region.
container: A software object that holds or organizes other software objects or entities.
content: The data portion of a document, as opposed to the properties that identify and describe the document. See also form data.
content-based retrieval (CBR): The process of searching for documents based on their content in addition to, or instead of, searching on properties.
content cache area: A 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. See also content storage area.
contentless document: A document with properties, but no content, that is typically used to track a physical item, such as a video tape.
content storage area: A physical storage area, such as a file storage area, database storage area, or content cache area, used for content. See also content cache area, database storage area, file storage area.
current version: The latest checked-in version in the version series of a document. Only the current version can be checked out or promoted.
custom object: A generic business object that can be stored in a folder. A custom object cannot have versions, lifecycles, or content.
custom property: A user-defined property, as opposed to a system-defined property. The user can assign custom properties to a class. See also property.
cutoff workflow: A workflow that is launched by the cutoff event. It ensures that the records manager reviews the entity after the cutoff trigger and approves the cutoff date.

D

database schema: See schema.
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, such as class definition, property definition, containment, storage policy, and queue events. See also content storage area.
data field: A user-defined workflow field.
data model: A template that is used to make a file plan object store compliant with certain records management standards. The data model can include metadata and security features.
data type: An attribute that is used for defining data as either numeric or character or both.
deadline: The time by which a job must be completed.
declare: To create a record object.
default ACE: An editable access control entry (ACE) whose source type is default.
default retention: The phase retention period that applies if either no alternate retention periods 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: To move an object to an earlier state or version, for example, to demote a major version with the status "released" into a minor version with the status "in process." In this case, the status of the previous major version is changed 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: A class that is used when adding a desktop form template (with the .itp file extension) to an object store. See also document class.
destruction: The removal of a record and the object of the record from the system.
detailed view: A format for document lists in which document properties are listed in columns.
DFS: See distributed file system.
direct ACE: An editable access control entry (ACE) whose source type is direct.
directly applied ACE: An access right acquired from a document class with 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 phase of a disposition schedule that controls the retention of entities in a particular state for a specified time period.
disposition: The state of a record after cutoff is applied through created disposition schedules and associated with containers.
disposition action: An action that is performed on entities after the cutoff is reached or when their retention period in a disposal phase is over. For vital records, the disposition action is a periodic review.
disposition hold: A temporary suspension of disposition processing. Each hold is for a specific use and can be applied to several entities at one time.
disposition schedule: The set of instructions for disposing of a record.
disposition sweep: A daemon process that finds records ready to move to the next phase of their disposition schedule.
disposition workflow: A workflow that is associated with a disposition action that automates that part of the disposition process.
distributed file system (DFS): A file system composed of files or directories that physically reside on more than one computer in a communications network.
document: An object saved in an object store or library. Documents have properties and security, and may additionally have content, versions, lifecycles, and subscriptions.
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 properties, storage location, security, lifecycle, and versioning of the document. See also desktop form template document class, form data document class, form policy specification document class, form proxy custom object class, form template document class, root class.
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, a map that allows property mapping between form template cells and document class properties for workflow and document policies.
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. See also form policy, form policy specification document class, form template document class.
domain: A logical grouping of resources in a network for the purpose of common management and administration.
domain controller: For a Windows NT Server or Windows 2000 Server domain, the server that authenticates domain logons and maintains the security policy and the security accounts master database for a domain. Domain controllers manage user access to a network, which includes logging on, authentication, and access to the directory and shared resources.
dynamic hold: A software component that provides the ability to specify conditions for entities to be placed on hold.

E

EAI: See enterprise application integration.
eBusiness Framework: The infrastructure and platform software for building eBusiness business-to-business, business-to-customer, and business-to-employee applications.
enterprise application integration (EAI): A technology that serves as the common interface between dissimilar applications using the same data and processes.
entity: In object-oriented design, an item that can be treated as a unit and, often, as a member of a particular category or type. An entity can be a concrete thing or an abstract idea.
entry template: A template that allows the user to create a document, folder, or custom object. The template provides default values for the destination folder, properties, and security. See also form data entry template, template.
event: A system-level action that occurs 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.
event action: A script, object, or workflow that is run as defined in a subscription.
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, the event logging feature logs a message when a work item is created or when a step processor begins processing a work item.
event subscription: A set of conditions required to initiate an event action. These include the target object, the event that must occur, and the action that is triggered.
event trigger: An event that triggers a cutoff in a disposition schedule. There are internal, external, recurring, and predefined date events.
exception state: A lifecycle property that determines whether a document can be promoted or demoted from one lifecycle state to another. See also lifecycle policy, reset.
export manifest: A temporary container for references to all the objects to export.
exposed field: A workflow-related system or data field in a roster, queue, or event log that has been made available for searches and sorting. Exposed fields can be used in a search filter, when defining an index, and when logging information to the event log.
expression: In programming languages, a combination of terms and operators that can be evaluated to a single value by using the rules of precedence for the given language.
Extensible Stylesheet Language (XSL): A language for specifying style sheets for XML documents. Extensible Stylesheet Language Transformation (XSLT) is used with XSL to describe how an XML document is transformed into another document.
Extensible Stylesheet Language Transformation (XSLT): An XML processing language that is used to convert an XML document into another document in XML, PDF, HTML, or other format.
external event: An event that occurs outside the system, but can directly impact the cutoff and disposition of entities.
external reference: A document with content consisting of a URL or a UNC path linking to another location.

F

Content Cortex domain: A domain that represents a logical grouping of physical resources and the Content Platform Engine servers that provide access to those resources. Each resource and server belong to only one domain. A server can access any resource in the domain but cannot access any resource that lies outside of the domain.
file plan: A container hierarchy that defines the organization of records and determines the security and disposition of contained entities.
file plan object store (FPOS): An object store that hosts a file plan.
file storage area: A permanent storage area managed by Content Platform Engine. A file storage area retains document content in a distributed file system (DFS) or a Windows NTFS file system. See also content storage area.
filter condition: A restriction placed on a search. For example, a filter condition could 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.
folder: A container used to organize objects.
folder class: A template for folders.
form data: The data from a filled-out form which can manually or automatically be saved to an object store. See also content, form data document class, form data entry template, form proxy custom object class.
form data document class: A document class used when specifying how form data is to be saved. See also document class, 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. See also entry template, form data.
form policy: A file or specification that determines how the form is presented. There are two types of policies: document policy and workflow policy. See also document policy, form proxy custom object class.
form policy specification document class: A document class used with document and workflow policies. See also document class, document policy, workflow policy.
form proxy custom object class: A custom object class used to link form data to form template policies. See also document class, form data, form policy.
form template document class: A document class used when defining form templates for document policies and workflow policies. See also document class, document policy, workflow policy.
FPOS: See file plan object store.
frozen version: A document version whose custom properties cannot be edited.
full text indexing: A method used to create and maintain an index catalog of text-based content and string properties stored in the database of an object store.

G

GCD: See global configuration database.
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 Platform Engine component that stores global data that defines the domain. Data includes information about object stores, file storage areas, content cache areas, index areas, and other domain resources. The global configuration database also stores and manages the security descriptors for all accounts provided by the authentication provider.
Globally Unique Identifier (GUID): An algorithmically determined number that uniquely identifies an entity within a system.
global property: A property template that has not been assigned to a class.
group: A logical organization of users whose membership allows them to perform the same activities or provide the same authority to access resources.
guest: An optional account for anonymous logons.
GUID: See Globally Unique Identifier.

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.
hold sweep: A daemon process that finds records meeting the conditions needed to place them on hold.

I

inbox: A folder that contains tasks assigned to a specific user.
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.
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 access control entry (ACE) whose source type is inherited.
initiating attachment: An attachment used to launch a workflow.
in-process version status: The status of the most recently checked-in minor version. Older minor versions have the status Superseded.
instance: A specific occurrence of an object that belongs to a class. See also object.
interim transfer: A software component that temporarily transfers records to a different location while the original record remains in the system until the final disposition occurs.
interim transfer workflow: A workflow that ensures that the home location of a physical entity or location of an electronic entity is changed to the specified location at the end of the retention period of a phase.
internal event: An event trigger that refers to a change in an entity’s metadata.
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. Isolated regions can be used to separate groups of users as appropriate for the organization.

J

Java EE: See Java Platform, Enterprise Edition.
Java Platform, Enterprise Edition (Java EE): An environment for developing and deploying enterprise applications, defined by Oracle. The Java EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multitiered, web-based applications. (Oracle)

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.

lifecycle

The set of stages a document passes through in its lifetime, such as draft and review.

lifecycle action

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

lifecycle policy

A policy that identifies the states of a document and the lifecycle action that executes in response to the state changes. See also exception state, reset.

Lightweight Directory Access Protocol (LDAP)

An open protocol that uses TCP/IP to provide access to directories that support an X.500 model and that does not incur the resource requirements of the more complex X.500 Directory Access Protocol (DAP). For example, LDAP can be used to locate people, organizations, and other resources in an Internet or intranet directory.

link

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.
A relationship between a workflow definition and a document or document class.

M

magazine view: A format for document lists in which properties appear in a phrase, such as created by [property] on [date].
major version: A document that has been released. The security of a major version makes the document available to a wide range of users. A major version is typically an approved document of record.
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 instruction sheet interpreter (ISI) process will execute before temporarily storing the work item in the ISI queue.
maximum operations per transaction: The number of database operations per transaction that the instruction sheet interpreter (ISI) process will execute before temporarily storing the work item in the queue.
metadata: Data that describes the characteristics of data; descriptive data.
migrate: To move data from one location to another.
milestone: A significant event in a project that is used to determine progress toward goals.
MIME: See Multipurpose Internet Mail Extensions.
minor version: A document version that has not been released. The security of a minor version makes the document available only to the authors and reviewers.
Multipurpose Internet Mail Extensions (MIME): An Internet standard that allows different forms of data, including video, audio, or binary data, to be attached to email without requiring translation into ASCII text.

N

naming pattern: A set of specific rules used to automatically generate names when new containers are added to a file plan.
node: An object in the tree view that serves as a container to hold related objects.
non-exposed field: A system or data field that is part of a work item but is not available for searches and sorting.

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 Platform Engine to access and manage documents and other objects. An object store resides in a domain, which can contain many object stores.
offset: An optional time gap between the event trigger and cutoff.
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: The user who has the highest level of access authority to a data object or action, as defined by the object or action; usually the creator of the object.

P

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 normally required for administrative, legal, or fiscal purposes.
persistent: Pertaining to data that is maintained across session boundaries, usually in nonvolatile storage such as a database system or a directory.
personal work manager: A web service or Open Client application used to locate and open items in active workflows.
physical record: Metadata describing a physical object, such as paper, tapes, or CDs.
predefined date event trigger: An external event trigger with a required date field.
processor: A Java function that accepts arguments as input. It 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.
PRO data model: See Public Record Office data model.
prog ID: See program identifier.
program identifier (prog ID): A property that specifies the COM whose code executes when the event occurs.
promote: To move an object forward to a later state or version, for example, to promote a minor version into a major version and set its status to "released." Promotion sets the previous status of the major version to "superseded."
property: A characteristic of an object that describes the object. A property can be changed or modified. Properties can describe an object name, type, value, or behavior, among other things. See also custom property, property tag, property template.
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 page: See tabbed page.
property tag: A shorthand way to identify a component by a keyword. See also property.
property template: A template for creating one or more custom properties that can be assigned to one or more classes. See also property, template.
Public Record Office data model (PRO data model): A data model that fulfills the Public Record Office requirements for electronic record management.
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 may translate the content to a different format.
publishing handler: A Content Platform Engine component that uses the publishing framework to produce HTML and PDF files.
publishing style template: A set of translation and formatting rules applied when a document is published. See also template.
publish template: A template that determines the properties, format (such as HTML), and storage location of the publication document. The template also determines whether the publication document is replaced or versioned when it is republished. See also template.

Q

queue: A workflow database table that holds work items. See also component queue, system queue, user queue, work queue.

R

realm: A collection of resource managers that honor a common set of user credentials and authorizations.
record: Any form of recorded information that is under records management control.
record category: The top level record container in a records management file plan.
record-enabled object store (ROS): An object store that has been configured to allow record declaration.
record folder: A container below the category level for records in a file plan.
records administrator: A specific security role, the duties of which include setting up security, object stores, document and record classes, and metadata.
records management system: Any system for managing records which 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: A specific security role, the duties of which include managing records, holds, and disposition actions.
records reviewer: A specific security role, 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.
records user: A specific security role, the duties of which include declaring and viewing records.
record type: A categorization of records that has a disposition schedule that is different from the one currently associated with the container.
recurring event: An event that recurs automatically after a specified time interval and is used to trigger periodic reviews of vital records.
released version status: The status of the most recently checked-in major version. Only a major version can have the status Released, and a version series can have only one released version.
request forwarding: The process of enabling 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. See also check out.
reset: To return a document to its original lifecycle state. See also exception state, 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: A period in a disposition phase that specifies the length of time between cutoff and the phase action. A disposition schedule can have several phases of retention, each with its own retention period.
retention schedule: See disposition schedule.
right: A security permission 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.
role: A job function that identifies the tasks that a user can perform and the resources to which a user has access. A user can be assigned one or more roles.
root class: A class that does not have a parent class. Most root classes can be subclassed or modified when configuring an object store. See also document class.
root folder: The folder on the system that contains all other folders. The system-recognized identifier is *ROOT.
ROS: See record-enabled object store.
route: A path between two steps in a workflow definition.

S

scenario: A specific sequence of actions that illustrates behaviors. A scenario may be used to illustrate an interaction or the execution of one or more use-case instances.
SCG: See security classification guide.
schema: A collection of database objects such as tables, views, indexes, or triggers that define a database. A schema provides a logical classification of database objects.
screening: A workflow that enables the reviewer to screen an entity before executing workflows associated with its disposition phases.
script: A series of commands, combined in a file, that carry out a particular function when the file is run. Scripts are interpreted as they are run.
Search Designer: A Java applet used to create stored searches and search templates.
search template: A file that, when opened, prompts the user to enter or change values and then displays a list of the documents that meet the search criteria. See also template.
security: The protection of data, system operations, and devices from accidental or intentional ruin, damage, or exposure.
security category: An additional hierarchical security marking.
security classification guide (SCG): A set of instructions used to classify information used by authorized derivative classifiers.
security parent: A folder configured to propagate permissions to documents contained in the folder.
security policy: A set of security templates that apply default security settings as the user adds 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. See also template.
server instance: A single operating system process that runs on a single machine and responds to requests from clients. See also virtual server.
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: The basic search type for the novice user which consists of a text box for terms and a drop-down list to select the field.
single-level versioning: A document version series containing only major versions.
single value: A property attribute that restricts the property to only one value.
site: A representation of a geographical location where resources are well connected through a fast, reliable LAN. Object stores, storage areas, content cache areas, index areas, and virtual servers are all associated with an individual site.
site preference: A configuration setting that determines the Content Cortex client appearance, behavior, and connectivity. Administrators can set site preferences for their site. Non-administrative users can set personal preferences, which override some site preferences.
snapshot: A statistical sample.
snapshot interval: An interval that defines how often snapshots are taken of the work in progress.
source permission: A value specifying the source of a permission, with four possible values: direct, default, template, and inherited.
spoliation: 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, a map which allows property mapping between form template cells and workflow data fields for workflow policies.
step processor: An application that provides the information and resources a participant needs to complete a step in a workflow.
storage policy: A policy that provides mapping to specific physical storage areas and is used to specify where content is stored for a given class or object with content, such as a document.
stored search: A file that displays a list of the documents that meet the search criteria.
subclass: In a generalization relationship, the specialization of another class; the superclass.
submap: A map that is called from within another map. Submaps are often used to map child business objects.
subscription: A method that sets up the conditions required for an event action to take place and the class, object, instance or workflow that event acts upon.
superseded version status: A major or minor version that is not the most recent.
supplemental marking: An additional non-hierarchical security marking.
symmetric encryption: A common key and mathematical algorithm used to both encrypt and decrypt a message. For two people to communicate securely with each other, both need to agree on the same mathematical algorithm to use for encrypting and decrypting data. They also need to have a common key: the secret key. Symmetric encryption is also referred to as secret key encryption.
synchronous: Occurring with a regular or predictable time relationship.
system field: A system-defined workflow field that the user can make visible at a step, use it to determine conditional routing, and expose it for searches and sorting. A system field value cannot be edited.
system function: A function that performs general flow-control and logic-control instructions commonly used in workflow processing, such as Begin Timer and Invoke (a web service).
system queue: A queue that holds work items undergoing or waiting for processing by the workflow system. There are two system queues: delay and instruction sheet interpreter (ISI). See also queue.

T

tabbed page

A logical page or section in a window that has a tab at the top. Users can click the tabs to move between tabbed pages.

task

The smallest unit of work in a workspace that can be assigned to one Content Contributor.
One or more actions associated with a case. A task has one or more steps that must be completed to finalize the task. For example, a task might be to review new hire applications. A case is not complete until all required tasks are completed or manually disabled. Each task has roles that are associated with it.

template

An object used to create new objects of the same type. The created object has the same characteristics as the template. 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 access control entry (ACE) whose source type is template.

tracker

A user who is authorized to monitor, manage, and modify workflows.

transfer

To send data from one location to another.

transfer mapping file

A file that maps one product’s property names to XML property names that a transfer tool includes in an XML file when importing or exporting to another product’s entities.

transformation plug-in

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

tree view

A view that provides a hierarchical view of an object and the objects that it contains.

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. At run time, 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): The server name and network name combined. These names together identify the resource on the domain.
upgrade: To install a new version or release of a product to replace an earlier version or release of the same product.
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 an inbox. See also queue.

V

version: The set of properties and content associated with an instance of a document in an object store. 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.
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, template.
version series: A series containing all versions of a document.
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.
view: The form in which an object is presented. A choice in the action bar that a user selects to look at an object from various perspectives is an example of a view.
virtual server: The logical service point that Content Platform Engine clients interact with. A virtual server can map to a single independent server instance or to a set of server instances. A client issues a request to a virtual server and one server instance responds. See also server instance.
vital record: An essential business record needed to meet operational responsibilities.
volume: A logical subdivision of a record folder into smaller and more easily managed units. A volume has no existence independent of the folder.

W

web client: An application that accesses object stores and workflows through a web connection.
web service: A self-contained, self-describing modular application that can be published, discovered, and invoked over a network using standard network protocols. Typically, XML is used to tag the data, SOAP is used to transfer the data, WSDL is used for describing the services available.
wizard: An active form of help that guides users through each step of a particular task.
work class: See workflow definition.
workflow: The sequence of activities performed in accordance with the business processes of an enterprise.
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: A database containing 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. It acts as a processing template that the workflow system 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 field: A data field or a system field associated with a single workflow. The value of a field is a workflow property, therefore it can be used in one or more steps of a workflow.
workflow group: A collection of users who perform a particular job function in a workflow. For example, claims adjustors and supervisors are workflow 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 and routes between the steps indicate one or more possible processing paths.
workflow policy: A policy used to map form template fields to workflow step element parameters. See also form policy specification document class, form template document class.
workflow roster: A database table that stores the current location of, and other information about, all workflows. Workflow rosters provide the workflow systemwith 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.
work item: 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, or by an automated process. See also queue.

X

XML classifier: A Content Platform 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: See Extensible Stylesheet Language.
XSLT: See Extensible Stylesheet Language Transformation.

Z

ZeroClick: A feature that provides the ability to automatically declare records without user involvement.