Change Management - Mass Update CI class vs Dynamic CI Group

[IndianaJones]

Its not very clear what direction we should use since both options exist. We have an option for "Mass Update CI class" which looks to function almost the same way a Dynamic CI Group works. Does anyone have a suggestion on which one we should be using? An example being, we are submitting a change request to patch all windows servers. In this example I could use both options, but our IT teams are wondering which one is best practice. 

Mass update CI documentation:
https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/change-management/c...

Dynamic CI Group

https://www.servicenow.com/community/cmdb-forum/what-is-dynamic-ci-group/m-p/2530643

[Kieran Anson · Accepted solution]

Hi,

Mass update has been a feature for a long time, and existed before Dynamic CI groups. Mass update CI is about updating your CMDB data. Dynamic CI groups allow you to represent a collection of devices as a single record.

So for your use case, a Dynamic CI group would be the correct solution. 

[Dr Atul G- LNG]

Hi @IndianaJones 

In simple words

Mass Update CI - It is plugin to update the set of CI , in one go. You need to mark the flag true in change for this.

Dynamic CI group : This is mainly used for approval in changes for some set of CI classes.