Govern App Builder Automation Safely

Ordinary users do not need to edit page code or call an API to connect an application page to a workflow. Use the visible integration controls in Flow Builder and review the result in App Builder.

Use the supported visual path

• For a workflow's starting form, configure the Start step and select the target App Builder page.
• For an assigned task, configure the Task step and select the page used to complete that task.
• After saving, refresh the page in App Builder, review the generated connections, and test with non-production data.
• Redeploy the connection after renaming, adding, or removing a widget that participates in the workflow.

Protect live pages

• Confirm the workspace, application, and page before saving the connection.
• Use a test page or duplicate when changing a production application.
• Review unrelated unpublished page changes first because deployment can publish them with the integration.
• Coordinate changes with other builders and keep integration credentials out of screenshots, tickets, and documentation.
• Do not delete generated page objects or bindings manually. A future deployment can replace them.

Administrator-managed automation

Direct inspection or modification of App Builder configuration is an advanced administrative task, not a feature exposed in the Applications user interface. If the visual integration cannot perform a required change, stop and ask the platform administrator to use the current technical reference and change-control process. Do not copy old endpoint examples or scripts into a live workspace.