Member Junction
    Preparing search index...
    • Create and save a scheduled Record Process that scores targetEntity's rows with modelId on a recurring cadence. Operates in one of two modes, driven by whether opts.outputField is supplied:

      • Write-back (outputField present): each run writes the prediction into that target column (via the Record Process OutputMapping), AND this helper records a MJ: ML Model Scoring Bindings lineage row (Mode='Scheduled') tying the model → Record Process → target entity/column so the operationalized model is discoverable by the UX surfaces that read those bindings. result.binding is the saved row.
      • Generic (outputField omitted): no OutputMapping is set and no binding is created — each run's predictions are recorded in the process run history (MJ: Process Run Details) only. result.binding is null.

      In both modes, saving the Record Process auto-creates its owned MJ: Scheduled Jobs row (so the run is live on the schedule immediately).

      Parameters

      Returns Promise<ScheduledModelScoringResult>

      the saved Record Process AND — in write-back mode — its scoring binding (null in generic mode); see ScheduledModelScoringResult

      if a required input is missing, the scope is not exactly one selector, the target entity is unknown, the Record Process fails to save, or — in write-back mode, after the Record Process was saved — the binding fails to save (the message carries the cause). The binding save is intentionally fail-loud (not swallowed): a saved RP without a binding would run invisibly to the lineage UX, so we surface the inconsistency.