setMapMigrationAssetApproval
Record or withdraw an operator's sign-off on a converted asset.
Approval is recorded, never inferred: most converted assets need no edits, so "was it changed" would leave a reviewed-and-perfect asset indistinguishable from one nobody has opened. Passing approved: false withdraws a previous sign-off.
publish decides whether sign-off also makes the asset LIVE. Defaulting to
false is deliberate: approval and publication are separate acts, and a
migration is non-destructive until someone chooses otherwise. An operator
reviewing a folder of converted forms should be able to work through them
without any of it becoming reachable by a visitor.
publish is REFUSED for an email, rather than ignored. What "live" means for
something that is sent is APPROVED — the send gate — and PublicationStatus
has no DRAFT -> APPROVED transition: on a product with Approvals enabled that
path runs through a designated approver, and a migration must not be the way
around it. With Approvals disabled the conversion already lands the revision
APPROVED, so there is nothing left to do. Approving an email here records the
review and changes no publication state.
setMapMigrationAssetApproval(
asset_id: ID!
approved: Boolean!
publish: Boolean = false
): MapMigrationAsset!
