{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":38845,"path":"platform-administration/ia-entitlement-validation-rules.md","title":"Entitlement validation rules reference","bundle":null,"doc_type":null,"release":"australia","body":"\n# Entitlement validation rules reference\n\nTechnical reference documenting entitlement validation rules, error states, and validation logic for jumbo apps and App Manager integration in product bundle installation workflows.\n\n## Validation phases\n\nEntitlement validation occurs in three distinct phases during the apps installation workflow:\n\n|Phase|When it occurs|What is validated|Result if validation fails|\n|-----|--------------|-----------------|--------------------------|\n|App selection|After the admin starts the installation workflow|For jumbo apps, Product Hub redirects the admin to App Manager. App Manager determines which apps are mandatory or optional and displays the selection experience|The selection experience remains available and displays information about missing dependencies when applicable.|\n|Install submission|After the admin submits the install request|App Manager performs the required installation checks before proceeding|Installation is blocked and App Manager displays an error or dependency message|\n\n## Mandatory app validation rules\n\nFor jumbo apps, App Manager determines which apps are mandatory and which are optional.\n\n-   Are determined by App Manager\n-   Can't be deselected\n-   Remain visible in the selection experience even when required dependencies or entitlements are unavailable\n-   Can prevent installation from completing if App Manager detects missing dependencies or other validation issues\n\n## Optional app validation rules\n\nFor jumbo apps, App Manager determines which apps are optional.\n\n-   Can be selected or cleared during the installation process\n-   Are presented by App Manager based on the product configuration and instance state\n-   Don't affect the selection state of mandatory apps.\n\n## Error states and messaging\n\n|Error state|When it occurs|User action required|\n|-----------|--------------|--------------------|\n|Missing dependency|A required dependency is unavailable during installation|Review the message provided by App Manager and resolve the dependency before retrying|\n|Install validation failed|App Manager can't complete the install request|Review the error details and retry after addressing the reported issue|\n\n## App Manager integration\n\n-   Product Hub redirects jumbo app installations to App Manager\n-   App Manager determines which apps are mandatory and optional\n-   App Manager displays the app selection experience and any dependency-related messaging\n-   App Manager performs validation checks before installation\n-   If required dependencies are unavailable, App Manager can block the installation and provide guidance to the administrator.\n\n## Implementation notes\n\n-   Jumbo app identification: Product Hub identifies jumbo apps and redirects administrators to App Manager for installation. App Manager determines which apps are mandatory or optional based on its configuration and business logic.\n-   Jumbo app installation workflow: For jumbo app installations, Product Hub redirects administrators to App Manager. App Manager provides the installation experience, including app selection, dependency messaging, and installation validation.\n-   Fallback behavior: If App Manager can't provide the installation experience or validation results, the administrator receives an error message and installation can't continue until the issue is resolved.\n\n**Parent Topic:**[Jumbo apps and entitlement validation](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/ia-jumbo-apps-valid.md)\n\n"}}