Reject/Repair

Description

Use the step to create a Document Review task in the AutomationEdge portal. Approvers use this task to review and edit data extracted from documents. The step functions identically irrespective of whether the process runs through an AutomationEdge Agent or directly from Process Studio.

Important: Reject-Repair step is compatible from AE 8.2.0 onwards only.

Prerequisites:

• A Task Template of type Document Review must be defined in AE UI. See Work with Tasks in the AutomationEdge User's Guide.
• To use a predefined document structure, define the Document Metadata in AE UI before configuring the step.

Specifying the Document: Provide the document in one of two ways (at least one is required):

• Document source file path: Specify the full path to a document file on the disk which needs to be attached along with task step
• Document file input parameter name: Specify the name of a workflow input parameter that refers to a file already uploaded to the server. Use the option for agent execution.

Note: When using the input parameter name, ensure the Auto Delete Input Files option in the Workflow Configuration remains unchecked after publishing and before running the workflow from the agent. Otherwise, the referenced input file might delete before the step runs.

Process Studio Execution: When the workflow runs directly from Process Studio instead of an agent, the following conditions apply:

• Creating tasks requires the Manage Document Metadata and Task Templates permissions.
• The step sets the Request ID (req id) of the created task to 0.
• The step applies the Process Studio workflow name directly to the workflow name field in the AE UI task details.

Notes:

• When running Reject/Repair workflows from Process Studio, use the Document source file path field to specify the document. Reserve the Document file input parameter name field strictly for agent execution scenarios.
• When you are running the step in the context of the Process Studio, a task is created with the request ID 0, which is purged along with the other request IDs as per the purge schedule configured in AE. For details about purging, see Work with Purging in AE User's Guide

Configurations

Field Name	Description
Step name	Specify the unique name for the workflow.

Multiple documents can be attached to a document review task. The workflow designer decides how to process these documents: • Option 1: Process all documents first and then create a single review task that attaches all documents together. • Option 2: Process documents one by one and attach each document to the same review task incrementally. This flexibility lets the designer align the workflow with the required review and approval strategy. For Option 2, the user selects the Task already exists? checkbox and enters the ID of the existing task in the Task ID field.

Field Name	Description
Task already exists?	Select the Task already exists? checkbox to use an existing task and enter the Task ID. In this case, you do not need to configure other fields such as the template, approvers, or deadline. Keep the checkbox clear if the task does not exist and specify the template details in the General tab. Note: A document review task can include multiple attached documents. To process them one by one and attach them incrementally to the same review task, check the Task already exists? checkbox, and enter the ID of the existing task in the Task ID field.
Task id	If the task already exists, specify or select the task id. Note: The field is available only if you select the Task already exists? checkbox. The field is mandatory.
General tab:	Note: If Task already exists? Checkbox is checked; the following fields are disabled.
Task template name	Specify the task template created in the AE UI. Or Click the picker icon () next to the field to select an available template. A warning icon () appears next to the field if the template cache or document metadata cache is empty (typically after restarting Process Studio). Hover over the icon for details, open the picker, and click Sync to clear the warning. The field accepts variable or static values and is mandatory. Notes: • The task template name is case-sensitive. Specify it exactly as defined in AE UI. • While creating the task, the AE UI refers to the specified template and displays the action buttons on the approval page. • Based on the selected template, the AE UI also determines whether workflow execution pauses until the task request is approved.
Select Task Template ()	Click the picker icon () next to the Task template name field to open the Select Task Template pop-up. The pop-up displays only Document Review templates and shows details including Name, Version, Description, and Last Updated date. The picker includes the following behaviours and features: • Filter: Type a name or description in the filter box to narrow down the template list. • Sync: Click Sync to load templates from the AutomationEdge server into Process Studio's local cache. Subsequent opens reuse this cached list until you sync again. • Sync Status: The picker displays the last sync time or indicates if a sync has never occurred. • Shared Cache: The task template and document metadata pickers share a single sync action. Clicking Sync in either picker refreshes both caches for the remainder of the Process Studio session. • Cache Clearing: The local cache empties automatically after a Process Studio restart. Note: You must have the Manage Document Metadata and Task Templates permission to sync the caches. • Tooltips: Hover over a truncated description or column name to view the full text. • Column Mapping: Selecting a template automatically applies its column labels in the Custom Columns tab. • Document Keys: The Documents tab key list populates separately from the document metadata picker, not from the task template.
Task title	Specify the title for the task. The field accepts variable or static values. Note: If specified, AE UI creates the task with specified title; otherwise, it uses the default title defined in the template.
Action deadline (Duration)	Specify the duration for the task in minutes (m), hours (h), or days (d). For example: • 30m or 1h or 1d OR • 2d 20h 10m The duration sets the deadline for approvers to take action on the assigned task. The field accepts variable or static values and is mandatory Notes: • Approvers can view the remaining time in Pending Tasks in the AE UI. • If no action is taken within the specified duration, the approver sees an Overdue tag on the Pending Tasks page. For more information, see Work with Tasks in the AutomationEdge User's Guide.
Approvers	Specify a valid AE user's group, valid AE users, or both to send the request. Specify approvers as: A single user, A single user group, Multiple users, Multiple user groups, or A combination of users and groups (separated by commas). One of these fields is required. The field accepts variable or static values and is mandatory. Notes: • In the current plugin version, manually enter the exact username (used to log in to the AE UI) or the group name (for groups). • The task is completed when any nominated user or any member of a nominated group takes an action. After that, the task is marked as Completed and appears in History under the Tasks tab. The task is resolved on a first-come basis. • All valid AE users in the selected group or AE users receive the task in their Pending Tasks list. For more information, see Pending Tasks in the AutomationEdge User's Guide.
Approver (Groups)	Specify one or more valid AE user groups to assign the task. Separate multiple groups with commas.
Approver (Users)	Specify one or more valid AE usernames used to log in to the AE UI) to assign the task. Separate multiple usernames with commas.
Output field	The step returns the task ID of the newly created document review task. You can use this ID to perform further actions. Default Value: task_id

Task group Config tab

Use the Task Group Config tab to link the HITL task to a task group created by a HITL Task Group Starter. Once linked, the task is listed under the matching group on the Task Group tab, letting reviewers process related work together.

Field Name	Description
Part of the Task Group	Select the checkbox to make this HITL task part of a task group. When it is selected, the task is routed to the task group specified below. Leave it cleared if the task does not belong to any group.
Task Group Id	Specify or select the task group ID produced by a HITL Task Group Starter. The task is added to this group. The field accepts static or variable value.
Task Group Level	Select the task's level within the group. The level sets the task order inside the group - 0 is the first task, 1 is the second, and so on. Allowed range: 0 to 4

Custom columns tab

Use the tab to provide a runtime value to the additional columns defined in the task template.
Example — Utility Bill Payment workflow
An Admin team uses an invoice-processing template with fields for Account Number, Amount, and Due Date. By mapping these template fields to Column 1, Column 2, and Column 3. Approvers can see and verify the extracted value directly on the Pending Task table. For more understanding, see section Templates from AutomationEdge User's Guide.

Field Name	Description
Column	Select the required column from the list. Note: You can select any of the 6 columns. Column 1 represents the first column defined in the task template and so on.
Value From Field	Select the value field coming from the previous step to set the column value.
Value From Variable	Specify the workflow variable (e.g., ${status}) to set the column value.

Documents tab:

Document code/name

The table displays the code or name of the documents that you add using the Document dialog.

Figure: Reject/Repair step with the Documents tab and Document code/name table.

To open the Document dialog and add document details, click add (+). You can add multiple documents, edit the details of a particular document, or delete a specific document as needed.

Field Name	Description
Document metadata type	Select the document metadata type from the list. Available types are: 1. Use Document metadata defined on the server: Select to use data fields defined in the document metadata**.** For more information, see section Work with Tasks in AutomationEdge User's guide. 2. Use server-compatible Document metadata generated at runtime: Select to define Meta JSON at runtime. You can pass either the field name or a variable that contains the JSON. 3. Use Document metadata generate at runtime (raw Json): Select If you have already generated metadata JSON. Note: Metadata must still be provided in JSON format; however, the JSON can follow any structure. In this case, AE does not render a UI—the JSON is displayed as-is.
Document code	Specify the Document code same as defined in AE UI. Note: If you select Use server-compatible Document metadata generated at runtime or Use Document metadata generate at runtime (raw Json) as the metadata type and the server has no metadata defined, provide a unique name to identify the document. The field is mandatory.

Field Name	Description
Document source file path	Specify path of the document to be uploaded on the server while creating the document review task. Note: Make sure to specify the full document path including filename. The field accepts variable or static values
Document file input parameter name	Specify input parameter name that refers to the document file. Note: Use if the file is already uploaded to the server as an input.

Specify the following field details, if you set the Document metadata type as Use Document metadata defined on the server. The user needs to define runtime values for the metadata that has been defined on the server. Or, Click to fill the table rows with the field keys defined in the metadata of the selected document. The button applies different behaviour depending on the document status: • Different document selected: The system clears and rebuilds the table with one row per metadata field key from the new document. If the table currently contains data, a prompt requests confirmation before discarding existing rows and values. • Same document, re-synced: The table updates in place. The step adds new fields, removes fields no longer present on the server, and retains entered values for existing keys. If the update requires removing rows, a confirmation prompt appears first. Notes: Selecting a document using the Select Document picker automatically populates the Key dropdown with the associated metadata field keys but does not add or change table rows. Rows update only after clicking Populate () • The behavior applies to documents using a server-defined metadata type. For other metadata types, the system disables the document fields table and requires providing the metadata as JSON instead.

Field Name	Description
Document meta key	Specify unique key associated with a specific attribute defined in the metadata on the server.
Metadata JSON	Specify or select the generated metadata field to automatically map the extracted data and highlight the coordinates. The Metadata JSON column accepts a single JSON object from the GenAI step. This object contains the complete data package for an extracted item. • Purpose: Use this column to map all extraction data in a single step instead of mapping individual data points manually. The field accepts the ?{<FieldName>_metadata} output. • Contents: The column automatically reads the extracted value, confidence score, page number, page dimensions, and bounding box coordinates directly from the JSON string. • Required action: When you map data to the Metadata JSON column, leave the Extracted value, Coordinate details, and Confidence level columns blank for that row. The Reject Repair step extracts these details automatically from the JSON object.
Extracted value	The actual value extracted from the document for the specified attribute.
Coordinate details	Specify the coordinates for the extracted values. AE UI can use this information to highlight the extracted value in the document.
Table json format	Select the table format of the extracted value. Available Formats: • None- Select this option if the value is obtained from a step other than DocEdge:Get Table or DocEdge:GenAI • DocEdge:Get Table - Select this option if the value is obtained from the DocEdge:Get Table step. • DocEdge: GenAI - Select this option if the value is obtained from the DocEdge: GenAI step. Notes: • If the attribute type is defined as a table on the server, you can select the appropriate format from the dropdown. • If a format other than None is selected, a compatible JSON must be provided in the Extracted Value field.
Confidence level	Specify the confidence level as High, Medium or Low for the extracted value. The confidence level appears on AE UI as follows: • Low: appears next to the extracted data. • Medium: appears next to the extracted data. • High: appears next to the extracted data. Note: Confidence level is case sensitive, for example, use Low and not low.
Meta json (Field/Variable)	Specify a Json field or variable based on the selected document metadata type. Note: Field is enabled if you set Document metadata type as Use Document metadata generated at runtime (raw JSON) OR Use Server-Compatible Document Metadata generated at Runtime and, disabled for Use Document metadata defined on the server.