Cyber Workflow
From a tested workflow to an interface
Read an execution, then build a page with fields, a run button and a result.
The Editor, Runs and Interface tabs are three views of the same workflow. Build the logic first, check what an execution actually does, then choose the controls and results people should see on its interface.
Start with an execution you can inspect
Open the Editor and run a small workflow. Switch to Runs to select an execution and inspect its steps. Read the status and timing before you change the design: the interface cannot fix an unconfigured action.
If an execution fails, open the relevant step and its logs. Correct the action or the required input in the Editor, then run it again. A failed execution is evidence about the workflow, not a reason to add more interface blocks.
Add only the controls you need
Open Interface and use the block palette. Start with a heading, an input field, a run button and one result block. The inspector lets you adjust the selected block’s settings and bind supported fields or outputs to workflow values.
Choose a result block that fits the value: text for a message, a table for rows or an image block for an image. Move and resize the blocks in the grid so the order reads naturally from input to action to result.
Preview before you publish
Switch to the interface preview and test the same workflow through its controls. Check the field labels, the run button and the displayed result. Use a second input to make sure the page is not only showing an old result.
When the interface is ready, open Publish. The dialog checks the address and the workflow before publishing. Read any reported issue, fix it, then try again. Keep the resulting link only after the publish operation confirms success.
Cyber Academy
What to remember
- Verify the workflow in Runs before designing its interface.
- Bind fields and outputs to the values they should use.
- Test in preview and wait for a successful publish confirmation.