ServiceNow: Best Practices for Custom CI Lifecycle Stage/Status

[Faycal]

Hallo ServiceNow Community 

In a scenario where Company X enters the hardware asset (server) lifecycle at the 'Deploy' phase (specifically 'In Test' or 'In Transit'), and does not handle product model creation or hardware asset purchasing/inventory management which is managed by Company Y . Since I dont want to disable the ServiceNow mechanisms that automatically set life stage Status and Life Cycle stage, because this can potentially have an impact on other lifecycle-linked processes that ensure CIs are not lost in the CMDB. So how should we handle this scenario?

My question is:

What is the recommended ServiceNow best practice for handling this scenario when the "entry point" in the CI lifecycle is Deploy-"in Test" or "in Transit" ? 

Generally 

What is the best approach in managing the Life Cycle Status and Life Cycle Stage in ServiceNow ?

Are business rules the general go-to solution for managing custom lifecycle stage/status behavior, or are there alternative, more sustainable methods for handling this?

Thank you for you help. 

[Kieran Anson]

Hi @Faycal  I think part of your scenario is missing to understand your business process that is conflicting with OOB behaviour? Or maybe I'm not understanding the issue where you're seeing the need for a customisation/extension to normal behaviour?

Would appreciate some extra guidance so I can help you 🙂 

[Faycal]

Hi Kieran,

thank you for showing interest in helping me.

What i want to know is: 

If I start at the deploy stage---> how do I manage the Life cycle Status or Stage. Do I use a business rule to achieve this or is there another accepted method like I don't know I can change one attribute say "installation status" and that will take care of the life cycle Stage and Status ?  

Thank you.

[Kieran Anson · Accepted solution]

You'd generally have a user do this via the form (once you've added the fields). Who will then change the Life Cycle Stage, and provide a status too. 

I'm not sure when you'd need a BR, not unless you have some requirement that if certain field values are set, then a certain life cycle value should also be set?

[Faycal]

Ahh Ok so it's pretty straightforward 😄 ! I can make sure that certain fields are made available to the user in a form by referencing ServiceNow life stages/status etc. and the rest can be picked up by the mechanisms that are OOB in ServiceNow to make sure that we stay on track with the rest of the other life stages.

Okay. I think this is a step towards the right direction. Thank you for your help.