Digital Product Release and using the service_model table

[MelanieS]

Is is possible to utilize Digital Product Release using the service_model table in lieu of application_model?

Currently application_model is utilized for infrastructure and third party software whereas our proprietary software Products releasing are built out in Product service_model. We are eager to build out release policies and templates with DPR but it appears currently the software is hard coded to use application_model

[Dr Atul G- LNG]

Hi @MelanieS 

As per the update and OOTB, currently, DPR supports only Software products, not hardware. What you are looking for is product-level change and it is not easy to do quickly. You can log a Now support case.

[Colin OBrien]

Hi @MelanieS

As Atul said, this is not something currently out of the box with DPR. However, supporting other extensions to the Product Model table (Service Model, Hardware Model, etc) are planned. The blocking issue that has stopped us from implementing this feature so far is that only Application Models have a corresponding "Version" record. Our architecture today is that a Release validates a Version is ready, so without a Version record we don't have something to validate.

We are currently working with the CSDM team on as a part of CSDM 5 initiative to rectify that issue so that we can support any type of Product release. This is one of our high priority roadmap items

To help us with our designs, could you give a few examples of what you would manage in the Service Model table?

Thanks,

Colin

[MelanieS]

cmdb_service_product_model is where are Product Releases and versions are built for all software being deployed to our customers. cmdb_application_service_model is utilized by our IT department for software purchased from other vendors such as Microsoft, Zoom, etc. 

Our entire system and customer center is built off service_product_model and links to entitlements, licensing, releases,  as well as some custom tables.

[MelanieS]

Hi Colin, 

When implementing SN we used service_product_model to build out the Customer Center, link entitlements, releases, versioning, defects and feature work. While application_service_model is used by our internal IT department for purchased hardware such as laptops, zoom software, Microsoft office etc. 

Ideally we would like to implement DPR using the service_product_model as using application_service_model would be a complete overhaul of our setup. Would if be possible to tweak the code to use the product_model and our linked version table on Product Releases?

When you say high priority on the road map, do you anticipate this to be delivered in the first half of 2025?

Thanks, 

Melanie