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.
Command Output
Some commands in Twidget return outputs, which are essential for dynamic and conditional logic within your workflows. These outputs are displayed next to the command and are prefixed with an "as" to indicate the variable name. Using Output Variables. Once a command returns an output, you can use the...
Commands in Twidget
Commands are the building blocks of Twidget's no-code platform. They function like code statements and can perform various operations such as creating and updating variables, loops, conditionals, retrieving and manipulating data in the datastore, and much more. Creating a Command. 1. Navigate to the...
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...
Working on smaller screens
Twidget adapts its navigation, lists and editing panels to phones, tablets and smaller laptop windows. You can use the same workspace and saved workflows across these views. Open your workspace tools. On a phone, use the menu button at the top to open workspace navigation. Choose a tool from Build, ...
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...