Assign from Stock Business Rule overriding Life Cycle Stage

[John Cuenca]

Hi everyone!

Currently I'm using the new CSDM Life cycle fields along with the legacy fields in Washington version. We have multiple Catalog Items for requesting physical devices wherein it creates or updates a CI record then tagging it to an existing Asset Record.

At the end of the flow, we set the Life Cycle Stage/Status to "Operational - In Use" in the CI. Afterwards, when closing the RITM, the "Assign from Stock" BR is getting triggered and sets the install status to "Pending Install". This will then sync to the new Life cycle fields, changing the Life cycle to "Deploy - In Stock"

How important is this OOB BR? I understand the importance of it in marking CIs as it assumes that some work is being done on the CI to fulfill the request but for RITMs where Life Cycle Stage needs to be assigned, how can it work with/around this Business Rule?

[Kieran Anson · Accepted solution]

That BR isn't really used on newer instances as the system property 'glide.itam_update_ci_status_from_ritm' now defaults to false. It's definitely one of those legacy things in SN that existed before better solutions were available.

Check to see if glide.itam_update_ci_status_from_ritm is true, if your instance is an older instance it might be set to the old value.

The other basis in which the BR is allowed to run is when the asset request line is the current RITM. If you've created your own process, I see no harm in deactivating this BR