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.
Background jobs
Let a server function continue in the background while the original workflow returns a job ID. This is useful for work such as preparing a report or processing a batch of records. What counts as a job?. A function or endpoint is not automatically a background job. A job is created only when a workfl...
Workflow templates
Keep reusable workflows in a private library within your workspace. Save a useful endpoint, function, middleware or event, then install independent draft copies when you need the same starting point again. Related workflows are included automatically where supported. Open Workflow templates from the...
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...
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...
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...