How to obsolete Customization files in IFS Cloud

If the obsoletion of customization files are done while doing a release update they can be deleted, otherwise follow these instructions.

To obsolete customization files you need to use the "Make Model Obsolete" or "Make File Obsolete" RMB options in the Developer Studio Tool navigator.

Obsolete model files and implementation files

When you obsolete a model file it is recommended to obsolete the respective implementation files (.views, .storage, .plsql, .plsvc, etc...) to avoid unnecessary implications. Can keep a short message to denote the file is obsoleted when obsoleting the file. But the length of the text should be less than 20 characters.

The empty files should commit into Customer Solution Repository. There obsoleted files will get picked by the delivery build and the respective changes will get reflected in the environments after the next build and deployment process.

Obsolete Java Implementation files

When you obsolete a java projection model file, you should obsolete the respective java implementation files as well to avoid build errors. When obsoleting java impl files, instead of completely removing the content of java files, remove the methods and keep the main class only.

Obsoleting scrips

when you want to obsolete database scripts such as insert/delete scripts, you can remove the content of the script and commit to the customer solution repo.

Note: It is not recommended to delete the customization files from the customer solution repository. When a file is deleted, those files will not get picked by the delivery build and the files in the Sanity build home will not get replaced. Hence the change would not get reflected in the customer environments.