Configure an ordinary activity

When you add an activity, by default, the Ordinary activity is added and the Configuration tab is open.

  • You can change an existing activity to a different activity type. For example, you can change an ordinary activity to a .NET activity. If you change an activity to an automatic activity, the resources assigned to the activity are removed, and the settings previously configured for the activity are automatically applied to the changed type. You can then configure only the properties specific to the changed activity type and modify other properties.
  • You cannot change the activity type for the following activities and nodes:

    • Embedded process activity

    • Decision node

    • Start node

    • End node

  1. Enter a Name for the activity.
  2. Under Configuration, perform the following steps:
    1. To add variables as input to the activity, click Add for Input variables.
      1. Select the variables. You can provide any number of input and output variables of any type, including Document or Folder variables. You can also select System properties or document types of a document set for an activity.
      2. Click Done.
      3. Similarly, click Add for Output variables to add variables as output to the activity. See Input and output for more information.
    2. Select Track variable changes to track the changes and allow the variable history of an activity to be recorded.

      You can see the variable value before and after the activity is executed.

  3. Under User interface, configure the following properties.
    • Associated file path:

      The path of the file (form), which is to be associated with the activity. When you generate an Activity or a Multiview activity form based on this activity, the form name appears in the Associated file path field or it can be manually populated. When you take this activity, you are redirected to the form specified in the Associated file path field. If the field is blank, you are redirected to the generic Activity form.

      Note This property is only available for ordinary activities.

    • Help text: Information you can add about an activity as Plain text (default) or a URL.
    • Mobile friendly: If selected, makes the activity mobile friendly. A number of activities cannot progress through a phone device because they require significant quantities of data. Therefore it is imperative to indicate if an activity can be performed from a phone device to prevent the work queue from getting cluttered.
      Note The Mobile friendly property is only available for ordinary activities.
    • MFP ready: Enables a manual activity to be Multi-Function Peripheral (MFP) ready. (Default: No). Available options:
      • No: The activity cannot be completed on an MFP device.
      • MFP friendly: Enables the activity to be completed on an MFP device and desktop.
      • MFP only: Enables the activity to be completed only on an MFP device.
      • MFP only - no password required: Enables the MFP operators to take the activity on the MFP without specifying the password. This setting is available for HP, MFP Emulator, and Lexmark eSF devices.

Additional information about input and output variables

You cannot add the same variable more than once as input and output. However, you can add the same variable as both input and output. When using an entity variable to an activity as input or output, either set an entire entity or an individual attribute as input or output variable.

You can use both process and server variables as input (NOT output) to Classification, Extraction and Composite activities for use in the Kofax Transformation Designer script. However, you can only use simple variable types and cannot use Document, Folder, Entity, Checklist, XML, XML expression and Complex variables. Therefore any document or folder variables configured for these activities are not available for use as input variables. The String input variable for Scan profile name on Composite activity is also not available for use.

Input variables for capture activities become available in Transformation Designer script. For example, if you consume an input variable called "test", you can access this variable in the Transformation Designer script as:

pXDoc.Fields(1).Text = pXDoc.ParentFolder.XValues.ItemByName(KTA.InputVariable.test).Value

You can configure the following document set properties as input or output to an activity.

System properties
Number of Documents Number of documents available in the document set.
Documents Document ID, Name (specified in document set for the Document Type), Source (source defined when you add a document to document set), Document Type ID, Document Type Name, Document State, Document State Description, Date Received.
Documents Summary Document Type, Source (source defined when you add a document to document set), State Description and Date Received.
Required Document Summary A list of document type names and description provided in the document set.
Received Document Summary The description of document type names and the rule comments (if any rule is applied).
Document type
Number of Documents Number of documents in a document type.
Status Status of the document type.
Status Description Description of the document type status.
Comment Document type rule comments (if a rule is applied for a document type).

You can set the document set properties as input (not output) in the following nodes: