Handling of the Archives After Their Expansion

When an archive is expanded, its contents are extracted to a folder automatically created (with the archive’s name) directly under the archive’s parent folder. What happens to the archive once it is expanded depends on the Delete Archive Files After Expansion option selected.

For example, suppose the archive AppsSport.zip is located in the coreApps directory in your uploaded codebase. The AppsSport.zip archive contains the files hockey1.exe and tennis.exe.

Archive Retention Configured

If Delete Archive Files After Expansion is not selected, the archive AppsSport.zip is retained in its parent folder, coreApps, once it is expanded. The resulting codebase tree looks like this, where both AppsSport.zip and a folder AppsSport, containing the archive contents, are found directly under coreApps:

coreApps
---AppsSport
-----hockey1.exe
-----tennis1.exe

---AppsSport.zip

Note:When an archive is retained, both the archive and its extracted files are processed during a codebase scan. This can result in a duplication of inventory.

Archive Removal Configured

If Delete Archive Files After Expansion is selected, the archive AppsSport.zip is removed once it is expanded, resulting in the following codebase tree:

coreApps
---AppsSport
-----hockey1.exe
-----tennis1.exe