21 docs tagged with "Legacy"

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.

The article describes the legacy bot step configuration flow. For the recommended approach, refer to Configure bot steps in UI.

The article describes the legacy bot step configuration flow. For the recommended approach, refer to Configure bot steps in UI.

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:

By default, WorkFusion security blocks all Data Store (DS) API calls from Manual Tasks, except Allowed Data Store Queries. Therefore, if you develop a custom Manual Task that uses DS API calls from JavaScript, you must create such allowed queries.

The instruction describes the legacy way to design Manual Tasks. The recommended method to design any custom Manual Task (MT) type is to use the 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.

PDF

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.

Following the steps below, you can migrate AutoML models from environments with version 9.2 or 9.3 SPA to those with any platform version (v.10.1+) without retraining.

The page describes how to migrate configuration and Business Process data from IA Cloud Business to Work.AI for their further use in Work.AI Developer. The guide assumes that you have parallel installations of both IA Cloud Business and Work.AI because the in-place upgrade is impossible.

The instruction describes how to migrate Business Processes with Manual Tasks that use qualifications from the WorkFusion platform v10.1.x to v10.2.1 and higher. For more information, refer to Migrating users and qualifications from previous platform versions | Migrating qualifications.

The article details instructions on structuring layouts and controls for legacy Manual Task designs implemented via Code Editor.

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 article details instructions on setting up a title and the Instructions section in a legacy Manual Task design.

Transaction tracking is applied at the Business Process (BP) level. It is possible to track only specific or multiple steps or exclude them from tracking. The feature enables collecting Service-Level Agreement (SLA) and Straight-Through Processing (STP) metrics and getting them displayed.