Checkinstall reported customizations

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Checkinstall reported customized tables, triggers, indexes and constraints during an upgrade, which ones to delete?

After running checkinstall, if you see many objects reported as potential customizations in the database_customization_*.txt files, please refer to the information below:

Resolution

• Checkinstall is an upgrade script running prior to upgrade, which will perform a basic comparison and indicate database objects that may possibly not be standard or OOTB. These objects will be listed in text files inside checkinstall directory, i.e.:
  • database_customization_triggers.txt
  • database_customization_indexes.txt
  • database_customization_constraints.txt
  • database_customization_tables.txt
• However sometimes checkinstall will actually indicate as custom some objects that are OOTB. Why is this happening : it's because apart from regular OOTB objects in Clarity, Clarity is also a tool that can be customized a lot (by enabling a standard functionalities like Audit or creating custom objects etc.) This will actually create objects with different names which cannot be easily matched to a list of objects on a new Clarity installation.
• We are constantly improving the tool, and adding different objects, but for some of the objects related to custom objects for example, the objects names can be different for every customer.
• This is why checkinstall text customization logs should be taken mostly as guidance. They will contain any possible customizations. Customers are encouraged to check the list and delete all known custom objects (created by them on the database) and leave all objects they have not created, or are not sure they did.
• The text logs may then be used by Clarity Support in case any issue arises, it will help to quickly track down the cause.