Workflow Preview and Publish
Review, preview, test, publish.
Portal Workflow
Open the draft in Portal
Review generated metadata, copy, checkpoints, and success-state hints.
Save corrections
Persist targeting and content fixes before each new preview pass.
Launch preview in your app
Use Portal preview or ?modelnex_test_workflow=FLOW_ID for deterministic replay.
Publish after validation
Release only after the preview matches the real customer path.
What To Validate
Broken targets make the experience feel unreliable immediately.
The user should return to the intended task, not a nearby page.
Completion copy should reflect the actual post-task screen.
If the user returns halfway through, the language should remain coherent.
Programmatic Launch
URL-triggered previews are useful, but production apps often launch a workflow from a button, checklist item, or empty state.
import { useModelNex } from '@modelnex/sdk'
export function SetupButton() {
const { startFlow } = useModelNex()
return (
<button onClick={() => startFlow('FLOW_ID')}>
Start Workspace Setup
</button>
)
}Fixing Preview Failures
You usually do not need to re-record a flow. Most preview failures can be fixed directly in Portal.
Agent cannot find the element
Edit the selector or text-match rule so the step points at a stable element.
Step fires before page load
Add a wait condition or a short delay so the target exists before the agent acts.
Recovery lands on the wrong page
Update the step target URL so recovery takes the user back to the intended route.
Narration sounds confusing
Rewrite the step copy in Portal and re-run the preview immediately.
Use Workflow Authoring for capture and draft generation. Use this page for review, preview, testing, and publish decisions.