Publish and Run a Workflow Form from Applications

Overview

RAPTIX can publish a Manual Start workflow as a native form. The form receives a tenant-relative share link in this format:

/f/:token

Enabled, non-inactive published forms appear under Runnable workflows in the appropriate Applications page view. A visible card shows whether the form is Public or Private and marks it Active.

This is the preferred experience when a workflow needs a straightforward intake form. It does not require an Enterprise App Builder page or custom page JavaScript.

Before you start

• Place the workflow in the intended RAPTIX workspace and application scope.
• Decide whether the form is Private or Public and review the security implications.
• Define stable variable names for every field used by later workflow nodes.
• Prepare non-sensitive test values and files for the first submission.

Build and publish the form

1. In Applications, open the workspace and application where the form belongs.
2. Create or open the workflow in Flow Builder.
3. Open the Start node and select Trigger Manually.
4. Add the Manual form fields. Use stable variable names because downstream workflow nodes read those names.
5. Configure required fields, selection options, display order, Entity field, and Main document as needed.
6. Enable Expose as app.
7. Choose Private for signed-in organization members or Public for approved anonymous intake.
8. Configure optional branding, success text, redirect, and consent.
9. Select Save Start Properties.

RAPTIX saves the workflow settings and generates or refreshes the /f/:token share link in the same action.

For the access-mode security differences, see Choose Private or Public Access for a Workflow Form.

Find the form in Applications

Return to Applications and open the same workspace and application. On the Pages tab, the form appears in the Runnable workflows section when all of the following are true:

• a share token was generated;
• the workflow is enabled;
• the workflow is not inactive; and
• the workflow is assigned to the current workspace/application scope.

Select Open to launch the form in a new tab. Users with Flow Builder permission and an applicable edit grant can also select Edit to return to Flow Builder.

Submit the form

1. Open the form from Applications or the share link.
2. Complete every required field.
3. Add files and accept the consent notice when the form requires them.
4. If the form is Public, complete the verification challenge.
5. Select Submit once.

RAPTIX validates only the fields declared by the workflow, starts the workflow, and returns a minimal success result. The form then shows its configured success message or follows its configured redirect.

For a Private form, an unauthenticated visitor is sent to sign in and then returned to the same link. For a Public form, the submitter is recorded as public-form context rather than as a signed-in member.

Update, disable, or revoke the form

• To change fields, access, branding, consent, or success behavior, edit the Start node and save again.
• To stop new runs, disable the workflow or set it to Inactive. The form card is removed from Runnable workflows in the current Applications interface.
• To invalidate the share link, open the Start node and select Revoke link. The old link becomes unavailable and the runnable card disappears.

Do not reuse a revoked token in documentation or bookmarks. Copy the current link from the Start-node settings after republishing.

Troubleshooting

The Runnable workflows section is missing

Confirm that the form was exposed and saved, the workflow is active, and its workspace/application scope matches the view you opened.

The form redirects to sign-in

It is Private. Sign in as a member of the same RAPTIX organization, or ask the builder to review the access mode.

A Public form cannot be published

Follow the message in Flow Builder. Public forms cannot contain high-risk anonymous behavior such as database-query or Python-script nodes, and unsafe email-recipient patterns are also refused. Use Private access if the workflow requires those steps.

Public submission says it is not enabled

The platform's anti-bot configuration is unavailable. Ask the platform operator to enable public forms; do not replace the form with an unprotected endpoint.

The form rejects an attachment

Check the size, total upload count, and supported type. See Upload Documents from a Workflow Form.

When to use App Builder instead

Use an Enterprise App Builder page when the form requires a highly customized interface, complex widget behavior, or an existing low-code application. Follow Connect an App Builder Page to a Workflow.