--- sourceDocument: Australia ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-administration Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Jumbo apps and entitlement validation # Jumbo apps and entitlement validation {#ariaid-title1} Release version: Australia Updated August 27, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Jumbo apps and entitlement validation Jumbo apps are large application bundles that allow administrators to select mandatory and optional components during installation. Entitlement validation ensures that administrators have the necessary licenses for mandatory apps before installation proceeds, while providing licensing status for optional apps to guide installation choices. This approach prevents unauthorized installations and offers flexibility in deploying optional features. Show full answer Show less ## Key Features * **Jumbo apps vs Standard Products:** Jumbo apps differ from standard products by redirecting admins from Product Hub to App Manager for installation, enabling detailed version selection and optional feature configuration. * **Mandatory and Optional Apps:** Mandatory apps are essential and require valid licenses to install; admins cannot deselect these. Optional apps enhance functionality, can be chosen or skipped, and their licensing status is informational rather than blocking. * **Entitlement Validation Workflow:** Validation occurs in two stages: * Pre-modal validation checks licensing for mandatory apps before showing the selection modal. * Post-modal validation informs admins about optional app licensing inline, allowing informed decisions. * **App Manager Integration:** All licensing checks rely on App Manager APIs, which serve as the authoritative source for entitlement status. Product Hub does not cache or override these rules. * **Installation Enforcement:** Installation is blocked if App Manager detects invalid licensing at any stage, ensuring compliance. ## What This Enables You to Do As a ServiceNow customer, this feature allows you to deploy large, complex application bundles with confidence that licensing requirements are enforced automatically. You can control which optional components to install based on real-time licensing information, optimizing your application footprint without risking unlicensed usage. ## Practical Impact * Prevents installation of unlicensed mandatory apps, ensuring compliance. * Provides transparency about optional app licensing, supporting informed installation choices. * Streamlines installation by integrating with App Manager for accurate entitlement validation. * Maintains system integrity by blocking installations if licensing conditions change during the process. Jumbo apps are large application bundles that support mandatory and optional app selection during installation. Entitlement validation confirms that admins have appropriate licensing for mandatory apps before installation proceeds, while optional apps display licensing status inline to inform installation decisions. Jumbo apps are large product bundles that bundle multiple applications together. Unlike standard apps or smaller product packages, jumbo apps support granular control over which components are installed by offering mandatory and optional app selections. Product Hub workflow leverages entitlement validation to confirm licensing requirements are met before allowing installations to proceed. Entitlement validation operates at two levels: mandatory app validation and optional app validation. This layered approach prevents invalid installations caused by missing licenses while giving you the flexibility to defer optional components when licenses aren't available. ## Jumbo apps vs standard products {#ia-jumbo-apps-valid__section_jumbo_vs_standard} Jumbo apps follow a different installation workflow than standard products: * Standard products: Use the app selection modal within Product Hub, where admins select mandatory and optional apps directly. * Jumbo apps: Redirect admins to App Manager, where they configure version, choose optional features, and complete installation. {#ia-jumbo-apps-valid__ul_d13_dys_jkc} Note: For jumbo apps, when an admin selects Install from Product Hub, they are navigated to App Manager to complete the installation experience. ## Mandatory vs optional app designation {#ia-jumbo-apps-valid__section_mandatory_vs_optional} Business Units (BUs) register jumbo apps by populating specific fields on the Product Hub resource table: * Mandatory apps: Identified through the product resource configuration. These apps are essential for core functionality and can't be deselected by admins. Note: Licensing for mandatory apps is a hard requirement --- installations can't proceed without valid entitlements. * Optional apps: Also defined in product resource configuration. These apps add supplementary capabilities and can be selected or deselected by admins during installation. Licensing for optional apps is informational --- admins can defer installation if licenses are unavailable. * Jumbo app identification: The system distinguishes jumbo apps from regular apps through a product type flag or resource classification. This classification enables the mandatory/optional app selection modal and triggers enhanced entitlement validation workflows. {#ia-jumbo-apps-valid__ul_f13_dys_jkc} ## Entitlement validation rules {#ia-jumbo-apps-valid__section_validation_rules} Entitlement validation follows these rules: * Mandatory apps require active licensing: Every mandatory app in a jumbo bundle must have a valid, active entitlement. Expired, inactive, or missing licenses block installation and prevent the modal from displaying. * Entitlement checks validate against mandatory apps only before modal display: Pre-modal validation only checks mandatory apps. Optional app licensing is evaluated after the modal displays, allowing admins to see the full picture before deciding which components to install. * Optional app licensing is non-blocking: If an optional app lacks valid entitlements, it displays as disabled within the modal with an inline message. Admins can proceed with installation of available apps. * App Manager is the source of truth: All entitlement queries delegate to App Manager APIs. Product Hub doesn't cache or override App Manager licensing rules. If App Manager reports an app as unlicensed, it is treated as unlicensed regardless of other factors. * Installation fails if App Manager validation fails: Even if pre-modal and modal-level validation passes, if App Manager rejects the install request during submission (for example, due to a changed licensing state or validation rule), the installation is blocked with an error message. {#ia-jumbo-apps-valid__ul_g13_dys_jkc} * **[Entitlement validation rules reference](https://www.servicenow.com/docs/9s2cwgnc6Xclr~Uzjdu1ag)** Technical reference documenting entitlement validation rules, error states, and validation logic for jumbo apps and App Manager integration in product bundle installation workflows.