Connect a Workflow Task to an App Builder Page

What the task integration does

An Enterprise workflow Task node can deploy task-handling logic to an App Builder page. The deployment deletes every JavaScript object whose name is TaskActions, TaskData, or begins with either name, including manually created objects. It then creates one new TaskActions object containing both task-action and task-data helper functions. Any manual code in the deleted objects is lost.

Use this integration when a task needs a purpose-built App Builder interface. For the standard RAPTIX approval experience, use the Manager Approval screen instead.

Transition note: The current Task properties screen may still show the technical category and panel label Appsmith. This is the App Builder task integration described here.

Before you start

You need:

• Enterprise access;
• permission to edit the workflow and use App Builder;
• an existing App Builder page for the task;
• a Task node with its assignee and allowed actions defined; and
• a test workflow run that can create a real assigned task.

If the task page uploads attachments, the App Builder integration credential must be configured before deployment. Use the page only in a trusted context and follow Protect an App Builder Workflow Integration.

Duplicate or back up a production page before deployment. The integration may update widget bindings, file-picker configuration, and page-load behavior. It also copies the complete unpublished page to the published page, so unrelated pending edits can go live.

Current authorization limit: The Enterprise API requires an authenticated user with general Applications access, but it does not enforce the Applications ACL for the target page. Use the deployment only through an approved page-change process.

Configure and deploy the task page

1. Open the workflow in Flow Builder and open the relevant Task node.
2. Configure the task title, description, assignee, and completion rules.
3. In Actions, add the actions the assignee may take. Use stable lowercase action IDs and user-facing names. Mark actions that require a comment.
4. In the task form settings, choose the App Builder category. If the screen still shows Appsmith, select that category.
5. Select Connect, then choose the workspace, application, and page.
6. Save the Task properties. The current deployment sends the selected page identifier; widget, Entity, and Main document selections do not control the generated task deployment.
7. When the deployment success dialog appears, review the page and deployment status, then select Continue to finish saving the Task.
8. Open the page in App Builder and review every generated binding before testing.

RAPTIX removes every matching TaskActions* and TaskData* object, creates one replacement TaskActions object with a new identifier, publishes the current unpublished page, and records the deployment result with the Task node. Refresh the App Builder page before testing.

What the deployment can change

Depending on the page, deployment can:

• replace all matching task objects with one unified TaskActions object;
• bind matching widgets to task data;
• configure FilePicker widgets for task attachments, whose upload helper uses the embedded integration credential;
• configure a container to load task data; and
• expose the Task node's allowed actions through TaskActions.

Review the generated result in App Builder. Do not hand-edit generated task connections because the next deployment can replace them. If you rename a bound widget, deploy again and verify that the new widget name still matches the task data it should show.

Bind the task action buttons

The deployment does not automatically create or bind action buttons because each workflow can expose a different action set.

1. In App Builder, create or select one button for each Task-node action that the page should expose.

2. Set the button's onClick binding to the matching stable action ID. For example:

   {{TaskActions.executeWorkflowAction('approve', Input_Comments.text)}}
   

3. Use an empty second argument when the action does not collect a comment.

4. Review and publish the bindings through the approved App Builder change process.

Test with an assigned task

Do not validate the page by opening a raw page URL alone. Task actions require the context of an assigned workflow task.

1. Start a test workflow run.
2. Confirm that the Task is assigned to the test user.
3. Open the task from Pending Tasks or the workflow detail page.
4. Verify that the page shows the correct record and task data.
5. Run each allowed action, including any required-comment validation.
6. Confirm that the task completes or changes state once, and that the workflow continues correctly.
7. Verify any uploaded document from the workflow and Documents views.

Troubleshooting

Deployment times out

The Task may still be saved without a successful page deployment. Reopen it, confirm the selected page, and deploy again before testing.

The page opens without task data

Open it from an assigned task, not from a bookmark. Then confirm the selected page and widget bindings and redeploy.

An action is missing or its button does nothing

Check the Task step's Actions list and stable action ID, then review the button's action binding in App Builder. Save and deploy again when the generated connection is stale; deployment does not bind these buttons automatically.

A renamed widget no longer updates

Review the renamed widget's current name and redeploy. Generated bindings scan the page's current widget names; selecting a widget in the Task settings does not control this deployment.