23 docs tagged with "Manual Task configuration"

You can use links to secure S3 buckets in the input data files for Manual Tasks and Business Processes.

You can add a Manual Task (MT) to a Business Process (BP) using one of the following methods:

The Run Priorities tab allows you to control the order in which Manual Tasks are processed.

The article details instructions on adding table structures to a legacy Manual Task design implemented via Code Editor.

The article focuses on applying the FreeMarker Template Language to deliver a legacy Manual Task design via Code Editor.

To set run parameters for a Manual Task (MT), open a task and navigate to the Run tab. In addition to setting the parameters, the tab allows you to do the following:

The instruction contains customization samples for legacy Manual Task designs in some of the most typical scenarios. There're two groups of samples described for the following groups of Manual Tasks:

The article is a runbook describing how to create complex custom configurations for Manual Tasks in MT Designer and resolve related issues. Before reading the topic, read the instructions for simpler use cases in Design Manual Tasks via Task Designer Operation.

The section refers to the legacy Manual Task design via Code Editor. Before reading the article, see the Design Manual Task in Task Designer mode topic.

The Task Designer Operation is the recommended method to design Manual Tasks (MT). It provides a no-code way to implement Manual Task forms: to generate them from a template or build manually in a drag-and-drop editor.

The Grid Answer Type allows workers to enter answers in a grid with a defined column structure and a dynamic number of rows. This feature is useful when the exact number of answers is unknown.

The article describes setting up a Manual Task with denormalized input data using the unique column name functionality.

FIFO (First In, First Out) is a prioritization strategy in which the oldest (first) entry is processed first. The FIFO strategy helps improve adherence to the service-level agreement (SLA) for record processing time.

Information Extraction (IE) is a special answer type used for extracting structured content from raw unstructured text. It displays input data as non-editable text where a user can select text chunks and tag them.

The Answer Types tab allows creating and managing Answer Types in Control Tower. These Answer Types are used for the following actions:

Templates allow you to reuse objects. Almost every object in the Work.AI platform, including Manual Tasks and Business Processes, is based on templates.

The Crowd is a group of workers in Workspace that corresponds to a set of pre-defined requirements. The following requirement types are applicable:

The article details instructions on setting up two major sections in a legacy Manual Task design: Questions and Answers.

The article contains instructions on customizing legacy Manual Task designs via Code Editor to enable the PDF content review.

The article describes a solution for a Manual Task with the Grid Answer type that contains the page number required to scroll XML content using this page number.

The multi-document Manual Task enables automation for cases when multiple documents represent a single transaction and have to be processed together, both manually and by machine learning. For example, a letter mentions an invoice and has this invoice attached. Thus, a letter contains an invoice number, and the attached invoice contains all the remaining information, such as the amount to pay.

The Taxonomy Answer Type can be used for classification of products, businesses, and articles. In WorkFusion, you can use this answer type along with Data Stores.

The article details instructions on setting up a title and the Instructions section in a legacy Manual Task design.