Managing Legacy Packages
If you have customization scripts that are not supported or captured by the NoetixViews Workbench (NoetixViews Workbench) and want to retain them, you need to add them to the legacy package. Then, you need to update the wnoetxu2 legacy.sql or wnoetxu5 legacy.sql script to add references to the legacy scripts so that they are invoked and run during Stage 4. You can also export or remove legacy customization scripts in the legacy package.For more information about modifying the legacy package, see Modify a Package in Manage Packages.
To manage legacy package
To add the scripts to the legacy package, do the following:
On the NoetixViews Workbench home page, click Manage Packages. On the Manage Packages page that appears, in the package list, click Legacy Package. The scripts of the legacy package are displayed.
Click Import Scripts. The Add Script to Legacy Package dialog box appears.
In the box provided, enter the path to the legacy script that you want to add to the package. If you want to search and find the script, click Browse, navigate to the location of the script, and select the script.
Click Upload. A message will appear adjacent to the box indicating that the script has been successfully uploaded to the server.
If the script that you want to add already exists in the legacy package and you want to overwrite the script, select the Overwrite script, if already exists check box. If you have not selected the check box, you will receive an error message indicating that the script cannot be added to the legacy package unless you overwrite the script.
Click Add to package. The script will be added to the legacy package.
NOTE: You can also perform this step after capturing legacy customizations by clicking the Import Scripts option on the Advanced » Captured Files page.
NOTE: The script name can contain a maximum of 255 characters and must contain only letters, digits, periods, underscores, and dashes.
To export a script from the legacy package, select the check box corresponding to the script that you want to export, click Export, and then, save the script.
To remove all the legacy customizations from the NoetixViews schema, you need to stage the legacy package to the NoetixViews schema folder, and then run Stage 4. If you want to remove a script from the package, do the following:
Select the check box corresponding to the script you want to delete, and click Delete. The Delete Selected scripts dialog box will appear indicating that the selected scripts will be deleted from the package.
Review the list of selected scripts that will be displayed in the dialog box, and click OK.
For the NoetixViews Workbench customizations that are dependent on legacy customizations, if a view revision is dependent on a legacy customization script, and if the legacy script is modified or deleted, do the following:
Unmanage the view in the NoetixViews Workbench to remove all the existing customizations.
Run Stage 4 to apply the legacy customization changes.
Recreate the discarded customizations using the NoetixViews Workbench. Now, they will properly be based upon the latest legacy customizations, if any.
NOTE: The wnoetxu2 legacy.sql and wnoetxu5 legacy.sql scripts in the legacy package cannot be deleted.
For example, a column is added to a view using a legacy customization script. If the column is modified using the NoetixViews Workbench, the view revision is dependent on the legacy customization script that added the column. Then, if the legacy customization script is deleted, and Stage 4 is run to apply the customizations pertaining to the view revision, the NoetixViews Workbench customization will fail because the column will no longer exist. Therefore, it is required to unmanage the view, and run Stage 4 to eliminate the column. Then, in the NoetixViews Workbench, you can add the column with all its properties set according to your requirements.