Help with mapping Software Models generated by Salesforce integration to License Entitlements

[simonorange]

Hello All,

I am attempting to deploy the SOW Direct integration profile for Salesforce to our ServiceNow instance. I have successfully managed to get it connected to Salesforce, authenticate, validate, run through the scheduled jobs and generate a number of Models. 

Here's my problem. The number of software models that have been created, far exceeds the number expected. I have been told by our Salesforce tech team that these are too granular. How do these software models map to Salesforce license SKU's that would be listed on a order form, as this is the only way to be able to identify quantities and usage rates purchased.

Has anyone deployed this integration and how did you map the models generated to software entitlements, that could be mapped to a SKU in order to allocate license numbers and costs?

Many Thanks

[dreinhardt · Accepted solution]

Hi @simonorange,

this is correct, the integration imports the the product level and does not take care about any bundling etc. done in SF (maybe you could raise a IDEA portal request for this?)

What we did, we’ve created additional software models and linked the base products as suite components to rebuild the same structure as in SF. Depending on the setting, one or multiple user subscriptions of the base products will trigger the consumption of the suite. It works, but requires additional effort.

let me know if this helps. If not. Please share additional details/examples.

best. dennis

[dreinhardt · Accepted solution]

Hi @simonorange,

this is correct, the integration imports the the product level and does not take care about any bundling etc. done in SF (maybe you could raise a IDEA portal request for this?)

What we did, we’ve created additional software models and linked the base products as suite components to rebuild the same structure as in SF. Depending on the setting, one or multiple user subscriptions of the base products will trigger the consumption of the suite. It works, but requires additional effort.

let me know if this helps. If not. Please share additional details/examples.

best. dennis

[simonorange]

Hi @dreinhardt 

Thanks for this suggestion. It looks like method we could use. Where would you assign the Software Entitlements, I assume to the Software Models that are defined as the top level suite? Do we need to assign entitlements also to the lower base products, but with no cost or license count ? 

As an example I have a product: "Sales & Service Cloud - Unlimited Edition", which I can work out a number of licenses and individual cost, So I create an entitlement for that. The suite children would be for example "Sales Cloud Unlimited", "Sales Cloud Analytics Cloud Integration", "Sales User", and "Sales Cloud Sales Insights Integration", which I don't have specific numbers or costs for these.

Also what is the Mandatory Options best set as for these children ? It is confusing the terminology ServiceNow is using. 

[dreinhardt · Accepted solution]

Hi,

your assumption is correct, to assign the entitlements only to the model they belonging to (e.g., SF Sales&Service Cloud).

The other models doesn’t any entitlement, as per correct software model setup each of the base product will be covered by a parent model with entitlements.

Software model setup: This depends on your configuration in SF and if any of the products is mandatory or not. Our bundle contains only two components and we added them both as „Optional“ with a „Suite Inference Number“ of 1 - so at least one user subscription for this product will trigger the license consumption for the user.

Best, Dennis