Web Client Guide

324
ProScan Portlet | Change Management / ProScan
elsif($input_source =~ m/description/){
print("Success");
}
else
{
print("Failure - no description found");
}
Tip
Notice that you can also combine these scans with the Edit Source Group Criteria regular expressions to
streamline them.
Java (Groovy)
When you select Groovy as the type of Config term, an editor appears that lets you enter that type
of scans.
As the screen says this implements ProScanGroovy or Groovy Java classes. The method should
return ‘Success or ‘Failure -’ results, and assumes
public String validate (String
input) {
precedes what you enter in the text editor. The following is example of the type of Java
code you can enter that scans for contents like
description
in shut down interfaces, and prints
output “Success” visible in the Audit viewer when it finds a matching term like
description
in
whatever source you select: