Understanding Catalog Item Pricing and GlideappProcessPriceUpdater Behavior

[Ashu_8871]

Hi ServiceNow Experts,

I'm trying to better understand how pricing works for catalog items in our environment.

We store the cost of software in the Software Model table and the cost of entitlements in the Software Entitlement (alm_license_list) table. When we publish a catalog item from a software model, both the Price and Cost fields in the catalog item are populated.

We also use a lookup-type variable set that dynamically updates the price on the Service Portal based on the entitlement selected by the end user. However, this variable set currently adds the entitlement cost to the existing catalog item price, which causes confusion. The requirement is to display only the cost of the entitlement (license).

To address this, we:

• Commented out the line in ProductCatalogUtils that sets the price field.
• Set the Price field in the catalog item to 0, so the variable set shows only the entitlement cost (i.e., 0 + entitlement cost = entitlement cost).

However, when the price is updated to 0, a business rule triggers the following line:
GlideappProcessPriceUpdater.updateProcessPrice(current);

This seems to update a flag called ignore_price to true when the price is 0. I want to prevent this behavior so that the ignore_price flag remains false even when the price is set to 0.

The issue is:

• I can't find the GlideappProcessPriceUpdater script anywhere in my instance or in a PDI.
• I suspect it's part of a protected or platform-level script include, but I need to understand how to override or disable this behavior.

Any guidance on how to approach this—or alternative solutions to meet the requirement—would be greatly appreciated!

Thanks in advance!