Page History, Publishing and Copied Connections
Test a page connection, inspect the URL retained by a copied page, use Undo, Redo and History, and publish synthetic pages to verify their real dropdown choices.
Watch tutorial (9:50)
Test a page connection, inspect the URL retained by a copied page, use Undo, Redo and History, and publish synthetic pages to verify their real dropdown choices.
Watch tutorial (9:50)
Publish individual workflow changes and inspect their versions.
Recorded with an earlier Twidget interface. Names, control locations and available options may differ; use the linked documentation for current guidance.
Watch tutorial (2:24)With Twidget's publishing feature, you can seamlessly push your changes live, ensuring that your updates take effect on the specified endpoint, function, or event. This feature also allows for version control, enabling you to revert and manage different versions of your changes effectively.
To publish your changes:
In the sidebar, you will have the option to add a message. This message acts as a summary for the changes you are making. It is recommended to add a brief description to keep track of the modifications.
After optionally adding your publish message, click on Publish. Your changes will now go live, and a new published version will be stored in the system.
Twidget stores each published version, allowing you to:
Revert to Previous Versions: You can roll back to any previously published version at any time.
Delete Published Versions: If needed, you can also delete specific published versions, restoring the endpoint, event, or feature to an earlier state.
Publishing Changes:
Click the Publish button to open the publish sidebar.
Optionally, add a summary message.
Click Publish to go live with the changes.
Version Control:
Each publish is stored for future reference.
You can revert to or delete any published versions as necessary.
By following these steps, you ensure that your updates are made live efficiently with a robust version control system, allowing you to navigate forwards and backwards in your change history.
Reusable Middleware
Middleware is a reusable workflow that runs before or after an endpoint, function or event. Build it once, then apply it wherever you need the same input checks, response formatting or logging. Create middleware. Open Middleware from the sidebar and choose Create Middleware. Give it a clear name, su...
Inputs
Overview. In Twidget, inputs are essential elements that allow you to configure endpoints and functions. Events do not use inputs. Endpoint Inputs. Endpoint inputs are used to retrieve data from requests. The available types of endpoint inputs are: 1. Path: Variables that are part of the URL path. 2...
Changes
In Twidget, every modification you make in our no-code builder is meticulously documented and stored as a change. Whether you are creating an input or editing a command, each action is captured in the platform. Important: Please note changes will not go live until they are published. Viewing Changes...
Testing
To pause an isolated test and move through commands, see [Live debugging](/docs/builder/live-debugging). In Twidget, you can easily test your endpoints and functions directly within our code builder. This guide will walk you through the steps to efficiently test your functions to ensure they meet yo...
Functions
In Twidget, you can build custom reusable functions. These functions can be utilized across various sections including endpoints, events, and other functions. Instead of creating the same commands repeatedly, you can create a function once and reuse it wherever necessary, making your workflow more e...