A hot fix provides enhancements to the updateindex command in the SAS Risk Governance Framework. This command is used to update index data for the global search feature.

The enhancements to the updateindex command include the following:

• A new option specifies that the web application should ignore any errors encountered while indexing attachments. With this option, any errors found in the indexing of attachments are reported as warnings. To ignore errors found during the processing of attachments, specify a value of true for the w option, as shown in the example below:

• When the updateindex command fails, the web application logs an error message in the monitor.log file. With this hot fix, the error message now includes the object type and object RK for the business object that failed, as shown in the example below:

• When the command encounters an error during indexing, it generates a message similar to the following to indicate the last object that was processed successfully:

• After you fix the cause of an error, you can now specify that the updateindex command should start processing at the point where the previous execution failed. As a result, you are no longer required to restart the process from the beginning and to re-index the objects that were processed correctly. To resume processing at the previous point of failure, specify the r option with the object handle of the last object that was processed successfully. To resume processing, you should also specify a value of false for the x option to ensure that the command does not clear previous search index entries. See the example below:

Notes:

1. The default value for the w option to ignore errors while processing attachments is false.
2. The default value for the x option to clear previous search index entries is true.
3. For ease of use in viewing the output from the command, you can pipe the output to a file, as shown below:

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Risk Governance Framework 7.4 is available at: