Managing Pages

The Pages & Forms list provides the tools to create, locate, open, preview, rename, clone, and delete Pages, Forms, and Structured Pages within a Project.

This guide covers the management actions available from the list and important considerations when modifying existing items.

Finding and Opening Pages

Pages & Forms supports both Tile View and Table View for browsing the items in a Project.

• Tile View displays items as visual tiles.
• Table View displays items in rows with their name, type, status, access configuration, and URL.

Use the Search field to filter the list by the available search criteria. Clear the search to return to the full list.

If the Project has no pages or forms, the list displays an empty-state message prompting you to create one.

To open an existing item, select Edit. This opens the Page Editor, where you can modify its visual content, configuration, and behavior.

Previewing from the Pages & Forms List

Select Preview from an item's actions to open its saved development version directly in Preview. This shortcut lets you test a Page or Form without first selecting Edit and then selecting Preview from the Page Editor toolbar.

The shortcut uses the current preview user context, which is Admin by default. To select Public, Any User, or a configured User Group before opening Preview, open the item with Edit, select the required preview user context in the Page Editor toolbar, and then select Preview.

Preview runs saved changes and does not publish the Project. For information about saving before testing, preview user contexts, responsive viewport controls, the Preview console, and development data behavior, see Previewing.

Creating a Page or Form

Click New to create a Page, Form, or Structured Page.

Provide a unique Page/Form ID and select the Type. The ID must contain alphanumeric characters and cannot be changed after creation.

For an explanation of the available types and when to use each, see Page Types.

After creating the item, open it in the Page Editor to configure its content and behavior.

Renaming a Page or Form

Use Rename to change the display name of an existing item.

For example, you can rename RegistrationForm to Event Registration to make the item easier to identify in the Project Editor.

Renaming affects only the display name:

• The original Page/Form ID remains unchanged.
• The Page URL remains unchanged.
• The page's content, configuration, and behavior are not modified.

To change the published URL, configure Page URL in Page Settings.

The Page/Form ID itself is immutable. If an item needs a different ID, create or clone it using the new identifier.

Cloning a Page or Form

Use Clone to create a new item based on an existing Page, Form, or Structured Page.

Cloning is useful when building similar interfaces, adapting an existing workflow, or creating a variation of a working implementation.

To clone an item:

1. Select Clone from the item's actions.
2. Provide a new, unique Page/Form ID.
3. Create the clone.
4. Open the cloned item to review and customize it.

Reviewing the Clone

A cloned item may retain configuration and references originating from the source item. Before using it, review the following:

Area	What to check
Name and URL	Assign an appropriate display name and verify the page path.
Status and Access	Confirm the intended availability and security settings.
Page Flow	Review actions, navigation, and references associated with the original implementation.
Widgets and Forms	Verify configuration, data sources, and references to other items.
Database and Cloud Flow	Check that the copied implementation uses the intended data and backend operations.

Cloning does not automatically adapt application logic to a new purpose. Review and test the cloned item before publishing.

Deleting a Page or Form

Use Delete to remove an item from the Project.

Before deleting, check whether the item is referenced elsewhere in the application.

Dependencies may include:

• Menus, navigation links, and buttons.
• Page Flow actions that open or navigate to the item.
• Other pages containing references to the item.
• Data Table actions and modal form workflows.
• External links or bookmarks pointing to its published URL.

Deleting an item does not automatically update every part of the application that references it. References to a deleted item may cause navigation failures or broken workflows after the change is published.

Update or remove these dependencies before deleting the item.

Deactivation Instead of Deletion

If an item needs to be temporarily unavailable but may be used again, consider deactivating it rather than deleting it.

Deactivation retains the item in the Project while preventing it from being served as an active published page.

Use the Active option in Page Settings to manage availability.

Where to Go Next

• Page Types — Understand the supported Page, Form, and Structured Page types.
• Page Settings — Configure page URLs, access, status, and other settings.
• Page Editor — Edit page content and behavior.