About Legacy Packages
During the capture process, a legacy package will be created automatically and used by the NoetixViews Workbench to manage the legacy customizations. The scripts corresponding to the legacy customizations are captured and added to the legacy package. By default, the legacy package is named as " Legacy Package".
Note: If you do not want to capture the legacy customizations, or if you do not have any legacy customizations to capture, the legacy package will be empty.
The scripts that are captured in the legacy package include the following:
Scripts that are available in the NoetixViews schema folder and not present in the scripts.cab file.
Scripts that are modified in the NoetixViews schema folder and also available in the scripts.cab file.
All wnoetx*.sql files except for the scripts that are not considered for the capturing process. The wnoetx gseg flex kff cols.sql and wnoetx qa plan gen options.sql scripts are captured only when changes are detected in these files.
The legacy scripts that are not captured in the legacy package are as follows:
Scripts with names that start with "mk or
Scripts with names that start with "t" or "T" because you should not create or maintain such custom scripts in the NoetixViews schema installation folder.
Scripts with names that start with "N KFF ".
All nvwb *.sql files.
All wnoetxu* prerequisite.sql files.
Scripts containing configuration-specific settings:
Scripts related to role prefix settings
Scripts related to security settings
wnoetx cm schedule defaults.sql
wnoetx gseg ans col type.sql
wnoetx ou xop check.sql
wnoetxu4.sql
wnoetxuq.sql
wnoetxus.sql
wnoetxut.sql
wnoetxuu.sql
dlglbmsg.sql
dlgprfx.sql
gallhlp.sql
ganswers.sql
gcomplet.sql
ginst1.sql
ginst2.sql
ginst3.sql
grefreshsecuritydm.sql
gusrrole.sql
i kff data upload.sql
wgenhlp.sql
wizpass.sql
wmshtml.sql