Subscription-Based Software Model Creation and Display Name Logic.Summary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article explains how subscription-based integrations create or reuse software models and how the software model display name is generated. For SaaS subscription integrations, the software model display name is automatically derived from the software model attributes populated from the vendor/product content. The display name is generally composed as: Publisher + Product + Version + Edition Values such as Pro, Standard, Enterprise, or similar product variants are typically populated from the Edition value in the product content. These values are not manually appended by the integration. How the software model is identified : When the subscription integration runs, each subscription includes a vendor-provided identifier, such as a SKU, product code, offer code, or subscription identifier. The integration uses this identifier to determine the correct subscription product definition. That product definition contains the entitlement details used to identify the expected software model. How an existing software model is reused Before creating a new software model, the integration first checks whether a suitable software model already exists. The integration may reuse an existing software model when: A previous subscription with the same subscription identifier is already linked to a software model.An existing software model matches the subscription product definition and entitlement details. If a valid matching software model is found, the same model is reused and no new model is created. When a new software model is created A new software model is created only when the integration cannot find an existing matching software model. In that scenario, the integration creates a new record in: cmdb_software_product_model The software model is created using the product and entitlement attributes provided by the subscription product content. Relevant script includes The following script includes are involved in this behavior: SampSaasSubscriptionIdentifierUtils This script include is responsible for identifying the software model for a subscription identifier. It checks whether the subscription identifier is already linked to a software model, attempts to find a matching software model from the subscription product definition, and handles unrecognized subscription identifiers when no matching content is found. SAMPremiumUtils This script include is used when a new software model needs to be created from the entitlement definition. It populates the software model attributes such as product, version, edition, platform, language, and related values from the entitlement content. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } NA