Account Identifier enforcement for manual pending event resolution

^{Minor Upgrade}

When a Marketplace Manager manually resolves a pending integration event as Success, Account Identifier enforcement is now scoped by integration and event type. This replaces the global validation introduced in Account Identifier now required to resolve pending events, which required a non-empty account identifier for every manual Success resolution when enforcement was enabled.

When enforcement is enabled for your marketplace, the Account Identifier field in the Resolve manually workflow behaves as follows:

Scenario	Account Identifier field
The event already has an Account Identifier	Shown read-only in Event Details; the input row is hidden
Manual web app events	Hidden
Microsoft or MOSI events	Hidden
Non-MOSI integrated subscription lifecycle event resolved as Success with no Account Identifier	Shown and required (*)
Failure resolutions, non-subscription events, or disabled enforcement	Hidden

When the field is required, the platform blocks saving until you enter a non-empty value.

❗ Important: While pending events for ISV-integrated products should be rare, if you must enter an Account Identifier, ensure the value matches the Account Identifier on the ISV side. A mismatch can break the integration for that subscription.

📝 Note: This change does not affect previously resolved events.

Refer to View and resolve pending events for more information.

Feature enablement

This behavior applies when Account Identifier enforcement is enabled for your marketplace. Contact your AppDirect technical representative to request it.

Setting enablement

No setting enablement is required.

Documentation

No documentation updates are required.