Action-Based tab

Scan Configuration > Explore Options > Action-Based tab.

In this tab you configure settings that affect Action-Based exploring. This tab is active only if the Action-Based Explore Method is selected in the Main tab.
Setting Details
General
Explore Timeout (minutes) The default time limit for Action-Based Explore of a site is 30 minutes, after this time the Explore stage stops even if the site has not been fully covered.

If AppScan misses significant parts of the site in this time, you can increase this timeout.
Minimum wait before invoking actions on page (milliseconds) ADAC attempts to identify that a page has loaded completely before it starts exploring it.
If you add a minimum wait period here, ADAC always uses this setting as the minimum wait period (even if it detects that the page has loaded), but will wait more than this time if it detects that the page has not loaded.
Tip: If when reviewing the Explore data, you see that AppScan failed to execute all the possible actions on a page, this can indicate that its dynamic wait time was too short. You can also see this during the scan if you enable the browser:
  1. Go to Tools > Options > Advanced
  2. Locate SessionManagement:ShowActionBasedPlayerWindow, and change its setting to True.
  3. Run a scan. The browser will open when scanning, and you can watch as AppScan explores your site. If you notice that it continues to a new page before the current page is fully loaded, increasing the wait time may solve the problem.
Note: Changing this setting might affect Explore time, so you may also want to consider increasing the Explore timeout (above).
Auto-detect dynamic-page loading By default, ADAC actively detects dynamic page content and treats the page as such. In rare cases this may prevent the page from loading correctly, and therefore affect scan coverage.
Tip: To identify this issue:
  1. Go to Tools > Options > Advanced
  2. Locate SessionManagement:ShowActionBasedPlayerWindow, and change its setting to True.
  3. Run a scan. The browser will open when scanning, and you can watch as AppScan explores your site. If you notice that pages which load successfully in a regular browser do not load correctly during the scan, clearing this check box may solve the problem.
Filters
Skip actions on identical DOM elements AppScan identifies actions that it has already executed on a previous page based on various criteria. If your site includes different actions that might seem identical due to their DOM element, AppScan might incorrectly ignore them. If this happens, clear this check box.
Note: AppScan does actually repeat identical actions a few times, to make verify that they really are the same, before deciding to ignore future iterations.
Use Machine Learning to analyze and skip redundant actions AppScan uses Machine Learning to improve Explore stage efficiency. AppScan can predict actions that are likely to lead to already-discovered parts of the site, so it can avoid them.

If your site includes many pages whose only difference is their content, this feature can greatly increase site coverage within the defined Explore Timeout. The precise gain will vary depending on the site.
Actions to skip This is a list of actions for AppScan to ignore as they could adversely affect the scan, or even the application. Actions to be skipped are identified based on the Id, name or ng-model attributes of the DOM element for the action. Any action whose DOM element attributes' Id, name or ng-model contain one of the words in the list, will be filtered out of the scan.

You can Add to, Edit, and Delete items in this list.