Before the user updates the CMDB record I want the CI to be sent for approval.

[SahithiAnka]

Before the user updates the CMDB record I want the CI to be sent for approval. Once approved the chnages should be reflected in the Database..How to acheive this?

Description: Could you please let me know how can we acheive the below requirement.
Below are the three action item performed by the user
1) Create a new CI
2) Update an existing CI
3) Decommision a CI

Before updating a CI, the fields which the user wants to update has to be sent to approval to the CI Owner. Once approved then only the changes should be reflected in the CMDB table

[fknell]

@SahithiAnka You can also use a standard change, which could be added to the catalog too. 

[Dr Atul G- LNG]

NO mate, Standard change dont need any approval. B

[Tony Branton]

As a few others have suggested, the best method for supporting an approval process for creating or updating a CI is through a catalog request.

As for decommissioning a CI, that depends on whether you mean retiring a CI or something else.  You can retire a CI using Data Manager which has OOB support for approving the retirement of a CI via a task.  The only gotcha is that Data Manager uses a policy-base approach that targets CIs that meet specific criteria as opposed to something that's driven by a user for an individual CI (e.g. an action on a CI form). 

The main advantages Data Manager gives are that it's automated and it supports retiring the CIs that are dependent on the CI being retired, preventing orphans from being created.