Editing an Application Page in App Builder
App Builder is the Enterprise authoring environment for application pages. From Applications, an authorized builder can open a specific page for editing or use the header's App Builder action to enter the broader builder environment.
Editing is a live-production action. The confirmation in RAPTIX warns that changes can take effect for everyone using the application, so coordinate and test according to your organization's release process.
Before you start
- Sign in at
https://<workspace>.raptix.appand open/applications. - Confirm that the organization is on an Enterprise plan.
- Confirm that you have an Edit grant at global, workspace, application, or page scope that covers the target page.
- Use a supported desktop browser and save any unrelated work before opening the builder.
- Identify the application owner and the expected validation path for the change.
Open a specific page for editing
- Select the workspace and application that contain the page.
- Stay on the application's Pages tab.
- Find the App Builder page card and select Edit.
- Review the dialog titled Edit “page name” in the live editor?
- Select Yes, edit live app to continue, or Cancel to return without opening the builder.
- Wait while RAPTIX creates an authenticated handoff and opens the page's edit address.
- Make and validate the intended change using the controls shown in App Builder.
RAPTIX records the page-edit action in Applications activity. The builder's own save, preview, and publication behavior is controlled by the builder version and your organization's process; follow the controls and release rules presented there rather than assuming that a draft is safe to expose.
Open the full App Builder
Use the header action when you need to work across multiple applications or pages.
- Return to the main Applications header.
- Select App Builder.
- While RAPTIX prepares the authenticated handoff, the button changes to Opening….
- In the builder, navigate only to resources you are authorized to maintain.
The header action is shown only when all applicable gates pass: the workspace is Enterprise, your role exposes App Builder, and your Applications grants allow builder access. Page-specific Edit access and global App Builder access are related but not identical.
Distinguish page editing from workflow-form editing
The Pages view can also contain cards under Runnable workflows. Their Edit action opens Flow Builder, not App Builder. Use this guide for App Builder page cards; use the workflow-building guides for runnable forms.
Access behavior
| Action | When it appears | Where it opens |
|---|---|---|
| Open | The page has a live view address. | The live application page. |
| Edit on an App Builder page | The workspace is Enterprise, the page has an edit address, and your grant includes Edit for the page or a parent scope. | That page in the live App Builder, after confirmation. |
| Edit on a runnable workflow | Your workflow scope includes Edit. | The workflow in Flow Builder. |
| App Builder in the header | Enterprise plan, App Builder feature access, and an applicable builder-opening grant. | The App Builder entry area. |
Controls that fail their access or plan checks are hidden rather than disabled.
Safe editing practices
- Make one focused change at a time and test the affected path before broad use.
- Confirm you are editing the intended workspace, application, and page before changing anything.
- Treat data queries, JavaScript logic, authentication, and integration settings as security-sensitive changes.
- Coordinate with other builders before editing the same page.
- Keep secrets out of visible widget properties, scripts, screenshots, and support messages.
- When validation fails, stop and restore the last known-good configuration using your organization's builder process.
Troubleshooting
The Edit action is missing.
The workspace may not be Enterprise, the page may not have an edit address, or your effective grant may not include Edit. Ask an administrator to check the page, its parent scopes, and the organization's plan.
The header does not show App Builder.
Global access requires more than the ability to view Applications. Ask an administrator to verify the App Builder feature toggle and your builder-opening grant. Page-specific Edit may still be available when the global action is not.
The confirmation opens, but the builder does not.
Allow pop-ups and redirects for your RAPTIX workspace, confirm your session is active, and try once more. If it still fails, report the page name and time to your administrator.
The builder asks me to sign in.
Return to RAPTIX and open the page again so it can request a fresh handoff. Do not reuse a transient authenticated URL or another person's session.
I can open the builder but cannot change the page.
The builder can enforce additional authoring rules after RAPTIX opens it. Ask the application owner or administrator to verify your builder-side access; do not bypass the restriction with a shared account.