Workflow Preview and Publish

Portal Workflow

What To Validate

Re-Teach During Test & Improve

When a draft step is wrong in preview, an authorized reviewer can pause the run and re-teach only that step from the app. The SDK captures the corrected interaction and submits it back to the current draft in the background.

• Use re-teach for localized issues such as a changed button, a fragile selector, or the wrong expected screen state.
• You do not need to record the full workflow again when only one step needs correction.
• Re-teach is an internal review tool. End users only experience the published workflow, not the authoring flow behind it.

How New Versions Are Created

Portal versions are created when a draft change from Test & Improve is applied. That includes accepted feedback changes and step re-teach corrections.

1. Start Test & Improve on a draft workflow.
2. Apply a correction from feedback or from a re-teach capture.
3. Portal saves the updated draft as the next version, such as v2, v3, or later.
4. Use Version Inspector to compare applied changes, keep refining the current draft, then publish when ready.

Programmatic Launch

URL-triggered previews are useful, but production apps often launch a workflow from a button, checklist item, empty state, or chat bubble search flow. Use startWorkFlow(workFlowId) to fetch and start an onboarding workflow directly from code.

import { useModelNex } from '@modelnex/sdk'

export function SetupButton() {
  const { startWorkFlow } = useModelNex()

  return (
    <button onClick={() => void startWorkFlow('FLOW_ID')}>
      Start Workspace Setup
    </button>
  )
}

In Portal, these code-driven and search-driven launches are grouped under the manual trigger label "Manual or Search".

Fixing Preview Failures

You usually do not need to re-record a flow. Most preview failures can be fixed directly in Portal.