Member Junction
    Preparing search index...

    Promote a Pending override to Active. Flips:

    • target Override: Status='Active'
    • target Override's Component: Status='Active'
    • prior Active sibling Override: Status='Inactive'
    • prior Active sibling Component: Status='Inactive'

    "Sibling" = same EntityID + (Scope, UserID, RoleID) tuple as the target Override. The target is the row identified by the input OverrideID; the priors are any rows currently Status='Active' at the same scope target.

    Idempotency. If the target Override is already Active, returns SUCCESS with a no-op message. If it's Inactive, that's a misuse — we surface NOT_PENDING so the agent / UI can ask the user what they really want.

    Inputs:

    • OverrideID (required, string) — the Pending override to activate

    Outputs:

    • ComponentID — the Component now Active
    • OverrideID — echoed for convenience
    • PreviousActiveOverrideID — the override that was demoted (or null)

    Hierarchy (View Summary)

    Index

    Constructors

    Methods

    Constructors

    Methods