Adding a required attribute while having CIs of this type for VCM version earlier than 7.6

VCM does not allow CTD to be changed significantly while having CI of this CTD in system

We have few options in hand:

1. If you are using VCM 7.6, you can use Content Type Evolution feature of VCM 7.6 2. If you are using VCM 6.5 or earlier, this feature is not there. Then, you have two options:
   
   1. Export all instances of the content type with vgnexport.
   2. Delete all instances.
2. Make the necessary changes to the content type.
3. Unpack the exported package and remove the CTD nodes from packageBody.xml. Once this is complete, re-package and import. Skipping this step will cause the old CTDs to be re-imported.
4. Import the instances back into the system with vgnimport.

But, import/export is also not very easy to do specially, if you have huge amount of data in system. In this case, you can use:

1. Alter the CTD table to add an extra attribute.
2. Add this extra attribute to your CTD using AppConsole.
3. Try to make it require, it will give you exception.
4. Run the query given below against your VCM system database:update vgnasattrdef set required='T' where name='Attribute-Name';where, Attribute-Name is xml name of the attribute which we added and want to make that require.
5. Make sure the 1 row updated with last query.
6. Restart the vgnvcmserver.

Go to AppConsole and confirm that your attribute is required now.