Attended Activity

Represents an activity performed manually by a human operator within a batch processing workflow.

Remarks

An Attended Activity is a type of Activity that requires direct user interaction, typically through the Attended Client interface. These activities are designed for scenarios where automated processing is insufficient or where human review, validation, or intervention is necessary.

Attended Activities are initiated by opening a Processing Task from the Batches or Tasks page. Examples include document review, manual classification, data entry, or exception handling.

Usage Overview

• Attended Activities are configured as part of a batch process to handle steps that require user input.
• When a batch reaches an attended step, a Processing Task is created and must be completed by a user.
• The activity exposes properties such as 'Content Scope' to control which Document Types are available for review or classification.
• Predefined flag messages can be configured using the 'Flag Messages' property to standardize user feedback or issue reporting.

Key Concepts

• Content Scope:
  Restricts the set of Document Types available to users during review or classification. If set, only types descending from the selected type are available; otherwise, all types are shown.

• Flag Messages:
  Provides a list of standardized messages that users can apply to documents or folders to flag issues, exceptions, or required actions.

• Task Lifecycle:
  The methods OnTaskOpen and OnTaskClose allow customization of behavior when a Processing Task is opened or closed in the Attended Client.

Typical Workflow

1. A batch reaches an attended activity in its process.
2. A user opens the corresponding Processing Task from the Batches or Tasks page.
3. The user performs the required manual actions, such as reviewing documents, assigning types, or entering data.
4. The task is completed, and the batch proceeds to the next activity.

Related Concepts

• Activity: The base class for all activities in a batch process.
• Processing Task: Represents a unit of work assigned to a user for attended activities.
• Content Type: Defines the structure and data model for documents being processed.
• Batch Folder: The organizational unit within a batch, often representing documents or groups of documents.

For more information, see the documentation for Activity, Processing Task, and Content Type.

Properties

Name	Type		Description
Content Scope	Content Type	►	The Content Model or Content Category containing the set of allowed Document Types. EditorContent Scope Editor The Content Scope property determines which Document Types are available to users during attended activities such as review or manual classification. By setting this property, you can restrict the list of document types that users may assign or select within a Processing Task. Only types that are descendants of the selected Content Model or Content Category will be available. If the property is left unset, all Content Types in the repository are available for selection. Usage Guidance Set 'Content Scope' to a specific Content Model or Content Category to limit the available document types to a relevant subset for the current activity. This is especially useful in environments with many document types, or when a particular review step should only allow certain classifications. If not set, users will see all Content Types when assigning or changing document types during attended processing. Example Scenario Suppose your repository contains multiple Content Models for different business units. By setting 'Content Scope' to the appropriate Content Model for a given activity, you ensure that users only see document types relevant to that business unit during review or classification.
Flag Messages	Embedded Lexicon	►	A list containing pre-defined flag messages. ConverterExpandable Converter The Flag Messages property provides a configurable list of standardized messages that users can apply to documents or folders during attended activities, such as review or exception handling. This property uses an Embedded Lexicon, allowing you to define local entries, reference external Lexicons, or include values from a parent field. Each entry represents a message or reason that can be selected when flagging an item for follow-up, correction, or special attention. Usage Guidance Add common flag messages as local entries to promote consistency and reduce manual entry errors. Reference external Lexicons to share flag messages across multiple activities or projects. Enable advanced options such as case sensitivity or regular expression matching if needed for specialized workflows. Users will see these messages as selectable options when flagging documents or folders in the Attended Client. Example Scenario Typical flag messages might include: "Missing required page" "Illegible handwriting" "Incorrect document type" "Needs supervisor review" By standardizing these messages, you ensure clear communication and easier reporting or filtering of flagged items.

Derived Types

There are 1 implementations of Attended Activity.

Review

Defines a human review activity to be performed on the Review Page within a Batch Process.

See Also

Content CategoryContent ModelDocument TypeForm TypePage TypeEmbedded Lexicon

Used By

Batch Process StepProcessing Job