Member Junction
    Preparing search index...

    Loads and changes the contribution rows behind one entity's form.

    Reads come from InteractiveFormsEngine, which already caches every row for every scope and status and emits when one changes — the same cache the form runtime reads, so the manager cannot disagree with the form it is managing.

    Writes go through BaseEntity.Save() and .Delete(). Direct SQL against an entity skips the Record Changes audit row, the server cache invalidation, entity actions and validation, all of which fail silently and leave a database that looks right.

    Turning a form or panel on follows the rule the Activate actions follow: the one live under the same key for the same audience is retired first, in the same transaction, and each component's status mirrors its row's.

    Index

    Constructors

    Methods

    • Writes a new placement onto an existing row, through the same row mapper the Create and Modify actions use.

      Every claim column is rewritten, including the ones the decision leaves out, so a claim the user has just dropped is actually cleared. The key is the one the decision names, or the one the write path derives from its grid claim or the row's component. The order, rail inclusion and configuration, which the placement dialog does not edit, are kept.

      Parameters

      • rowID: string
      • contribution: FormContributionSpec
      • status: "Active" | "Pending" | "Inactive"

        What the row is saved as: on, a draft, or off. On retires the panel live under the row's new key for its audience, in the same transaction.

      • Optionalprovider: IMetadataProvider | null

      Returns Promise<FormPanelAdminResult>