Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

CMS UI2018.05

Use > CMS Modules > Smart Software Analytics > Use > How to Review SAI Entries on SSA

How to Review SAI Entries on SSA

Through the SSA user interface, you can review SAI entries in the autoteach.zsai file and commit them to a user SAI file of your interest. To do this, follow these steps:

Access the Smart Software Analytics module. For details, see How to Access Smart Software Analytics.
On the Smart Software Analytics page, click TEACH SERVER. The View Teaching Status page for the autoteach.zsai file opens and a list of SAI entries which are grouped by publisher is displayed.
Locate the SAI entry that you want to review.

To help locate the SAI entry fast, you can filter the displayed SAI entries by using the search function on the View Teaching Status page. For details, refer to Search for an SAI Entry.
Hover your mouse over the SAI entry that you want to review, click the ellipsis icon that appears, and then select Review.
A reviewed icon then appears to the left of the entry. Meanwhile, a dialog box appears at the bottom of the page, asking you to commit the reviewed SSA result to a user SAI file.

For example, if you have reviewed the contents of a publisher, you will see a dialog box resembling the following:

Click the drop-down arrow to select the user SAI file to which you want to commit the reviewed entry. Then, click COMMIT.
Note
- If no user SAI file is available, a text box with a grayed new.sai hint inside will appear where the drop-down combo box is located as shown in the screen shot above. Directly click COMMIT so that a user SAI file named new.sai will be created and the reviewed SSA result will be moved to this user SAI file. Or, type a different name in the text box for the SAI file to be created and then click COMMIT.
- When you commit an entry to a user SAI file, all contents under this entry, including information of its sub-levels, will be committed to that user SAI file.
The reviewed entry is then moved from the autoteach.zsai file to the specified user SAI file.

You can also review multiple SAI entries at the same time by using the batch review icon on the toolbar of the left or right pane.

Recommended Review Process

When reviewing SAI entries, you can refer to the following process that we recommend:

Before reviewing SAI entries, expand the Publisher, Application, Release, Version and File layer one by one.
Check and edit the entries starting from the lowest level to the top level, in an order as shown below:
1. Check and edit the properties of all files under the same version
2. Check and edit the properties of all versions under the same release
3. Check and edit the properties of all releases under the same application
4. Check and edit the properties of all applications under the same publisher
5. Check and edit the properties of the publisher
With information of all levels checked and confirmed, review the publisher and commit it to a user SAI file of your interest.

Note If you want to review and commit properties contained in a sub-level instead of reviewing and committing the whole publisher, do remember to commit the properties timely because if you re-log in the UI without the commit operation, the uncommitted information would be lost.

Send Help Center feedback