Customizing SPM for Lifecycle Tracking

[KumarA913649730]

We're looking to set up a system to track entities throughout their lifecycle, from introduction to completion. After digging into Service Portfolio Management (SPM) and its modules, it seems like the idea-demand flow might be a good fit for our needs.

However, we've hit a snag when it comes to customizing fields. We need additional fields like state, city, village, and several others related to finances and other aspects that aren't available out-of-the-box in the demand table of ServiceNow.

We also follow a specific process flow tailored to our needs. While I know we can manually create this flow, I'm wondering if there's a more seamless way to integrate our custom requirements into SPM.

If anyone has any suggestions or advice on how to tackle this, I'd really appreciate it.

#spm 

[Sohail Khilji]

Hi @KumarA913649730 ,

There is always a big space for enhancement when it come to SPM module.

check for specific requirements for tracking entities throughout their lifecycle. Identify all the additional fields you need, such as state, city, village, financial information, etc. Also, define your process flow and any specific stages or steps involved.

(Stick to best practice ) Start by leveraging the existing functionality within SPM to see how far it can meet your requirements without customization. ServiceNow provides various configuration options, such as adding custom fields, modifying forms, and defining new workflows.

If the out-of-the-box functionality doesn't fully meet your needs, you can create custom fields within the demand table or even create new tables to store additional information. your open for it.

you can also customize the proccess and workflows as needed for your environment. also there is a scope of integrating this module with other tools which your env has. I hope this helps...

[KumarA913649730]

Appreciate your quick response, however, as much I have researched about the possibilities, I am curious how to implement those as well. The point is clearly to use the maximum OOB features. However, my immediate concerns are:

making a new alternate demand table with all required columns and getting all other Demand functionalities like process flow, related lists etc., integrated into the alternate table(basically, replacing the original demand table). 

I am new to SPM and ServiceNow in general. And some guidance in the right direction would be really helpful.