Kofax Kapow User's Guide Users EN

Title:

Language: English French German Spanish

Format: Paperback Hardcover Audiobook

Reader Age: Infant Teenager Adult

98 Kofax Kapow User's Guide A form contains a number of fields. For example, the first -tag in the example form defines a field named "book_author". Note that the name of a field is usually different from what the user sees in a browser. For example, the "book_author" field will appear to be named "Author" in the browser, not "book_author". A field can be defined by more than one tag. For example, the "book_format" field is defined by three -tags in the example form. Tags that use the same field name and are of the same field type (text field, radio button, check box, etc.) define the same field. A field can be assigned one or more values. For example, the "book_format" field can be assigned the value "format_pb" to select paperback format. Note that, like the field name, the value assigned to a field is usually different from what the user sees in a browser. For example, the user will see the text "Paperback", not the value "format_pb", when choosing the paperback format. Depending on the field type, some fields can be assigned more than one value at the same time. For example, since "book_format" is a check box field, we could assign both the value "format_pb" and the value "format_hc" to the "book_format" field to select both the paperback format and the hardcover format. Most fields have a default value. The default value is the value that is initially assigned to the field in the form. For example, the "book_language" field has the default value "lang_0", because of the "selected" attribute. A form is submitted by sending the current values of the fields to the web site. Only fields that have one or more current values are sent. For example, if none of the check boxes of the "book_format" field in the example form are checked, no value is sent for that field. In a browser, the submission of a form usually happens when the user clicks a submit button. There are two kinds of submit buttons: normal submit buttons and image submit buttons. Normal submit buttons are defined using a -tag or an -tag, in both cases with the "type" attribute set to "submit". If a normal submit button has a field name and value, that field is sent with the specified value when the button is clicked. Image submit buttons are defined using an -tag with the "type" attribute set to "image". An image submit button defines two fields, named "button name.x" and "button name.y", where button name is the name contained in the "name" attribute of the -tag. If the -tag has no "name" attribute, the fields are named "x" and "y". When an image submit button is clicked, these two fields are assigned the xand y-coordinates of the position in the image where the mouse was clicked. Some web sites use this for creating image maps with different behavior depending on where the user clicks. Some forms use JavaScript. For example, the

-tag may have an "onsubmit" attribute that contains JavaScript to be executed before the form is submitted. Similarly, an -tag may have an 99 Kofax Kapow User's Guide "onclick" attribute that contains JavaScript to be executed when the user clicks on the field. The robot will automatically execute this JavaScript. For performance reasons, you may decide to ignore the JavaScript execution when submitting the form. To do this, you must clear the "Execute JavaScript" option in the options in the form submitting step. Determine the Step Action The simplest way to submit a form is to fill in the form using the appropriate actions. For more complex submissions, you can loop through a form to get the desired result. Consider the book search example form. • To search for books in all available languages and for all reader ages, the site may not allow such a general search. You can loop through the languages and reader ages, making a form submission for each combination of language and age. To do this, use the Loop Form actions: • Loop Field Values • For Each Option • For Each Radio Button • The Loop Form actions does not submit the form, so this must be done separately in a subsequent Click action that clicks one of the submit buttons of the form. • To loop over a combination of field values, place several steps with Loop Form actions after each other prior to the Click action that submits the form. • To create a URL that represents a submission of the form, use the Extract URL action on the form's submit button. Use the Loop Form Actions There are three Loop Form actions: Loop Field Values, For Each Option and For Each Radio Button. The three actions correspond to the three kinds of form controls for text input (INPUT elements with type "text" and TEXTAREA elements), options (SELECT elements) and radio buttons (INPUT elements with type "radio"). Watch the video below or read on to learn how to use these loops. See Loops in Forms tutorial for more information. To loop over a form, you need to decide which form controls to loop over and in which order (this determines the order in which output values are generated). Next, insert a step for each with the loops with the corresponding Form action. This can be done by right-clicking the control in the Page view and choosing Forms > from the context menu, where is the appropriate action. For example, if the control is a text input control, you would choose Forms > Loop Field Values. Every time a Loop Form action is executed, a value is changed in a form control element in the HTML page. This corresponds to what you would have done manually in a browser. If the form control has a JavaScript event attached to it, this event would be fired and some JavaScript executed. In some cases this JavaScript may change the form, such as the options of a SELECT element. In this case you must be careful and choose the right order in which to loop over the controls to ensure that the right options are available to the robot when it needs them. Normally, if you follow the order that you would use when doing this manually in a browser, it should work just fine. Once all the Loop Form action steps have been inserted in the robot, you should add a step with a Click action that clicks one of the submit buttons of the form. 100 Kofax Kapow User's Guide Upload Files Some forms contain file fields that allow you to upload files. A file field is defined by an -tag of type file, such as the following: In the Select File action, there are two ways to upload a file using a file field. 1. The first way is to upload a file from the file system. To do this, select File in Local File System from the list and enter the file name. When the form is submitted, the specified file is loaded from the file system and uploaded as part of the form submission. Note The file name must be an absolute file name, including the drive name, if any, and the directory path to the file. 2. The second and most common way to upload a file is to specify the file contents to upload, instead of loading the file from the file system. To do this, select File Contained in Variable from the list. Then, you may select the variable that holds the file contents from the File Content list. Typically, you get the contents from either a binary variable in which you have downloaded the file earlier using the Extract Target action, or from a variable containing text that you have extracted earlier. Optionally, you can specify the content type and the file name of the file. The content type should be the MIME type of the contents, optionally followed by a charset. You may use one of the predefined content types, acquire it from an attribute or specify a custom content type. For example, the content type could look like this for an image: image/gif and like this for a plain text: text/plain; charset=iso-8859-1 Note that when downloading files using Extract Target, you can store the content type and file name of the downloaded data in other variables. You can then use this information when uploading the file with the Select File action. Use the Context Menu on the Page View You can use the context menu in the Page View as a shortcut for selecting and configuring the Submit Form and Loop Form actions. 1. To select the Submit Form or Loop Form action in the current step, right-click inside a -tag in the Page View. 2. In the context menu, Forms submenu, select Use Submit Form or Use Loop Form. 3. If the current step contains a Submit Form or Loop Form action, in the Page View, Forms submenu, right-click a field and select Add Assignment to Field in the Forms submenu. A dialog box appears. 4. Assign a field value. 101 Kofax Kapow User's Guide 5. If the current step contains a Loop Form action, in the Forms submenu, right-click a field and select Add Looping over Field to loop through the field. 6. A dialog box appears where you can configure a One field with values to loop through field group for the field. 7. If the current step contains a Submit Form or Loop Form action, in the Page View, right-click a submit button. 8. In the Forms submenu, click Select Submit. Loop Through Tags on a Page A robot often needs to loop through elements on a page to perform some action on each element. For example, you might be interested in extracting certain properties from each result in a search or from each row in a table. The following topics explain how to do this: • Loop Through Tags with the Same Class • Loop Through Tags with Different Classes Keep in mind, with multiple different types of loop steps, there are many ways to handle the same situation. Loop Through Tags with the Same Class There are a couple of ways to set up a loop. The first way is the easiest if it is viable, and involves looping over tags that all share a class attribute. Note Each div element has the attribute class="story". To determine whether looping through tags with the same class is possible, find the elements in the HTML view. In the case shown above, it is possible to loop through the three div tags with the attribute class="story". 1. Right-click the first tag and selectLoop > For Tags with Class > story. 102 Kofax Kapow User's Guide This creates a For Each Tag Path step in the robot, which loops through all elements on the page with the given class. 2. On the Loop step, use the arrows to ensure that the correct tags are included in the loop. There might be other tags on the page that you do not wish to include in the loop but that use the given class. These can be excluded from the loop with an easy fix. 3. To exclude tags with the selected class, click For Each Tag Path. Review the HTML view. 103 Kofax Kapow User's Guide The For Each Tag Path has automatically included the entire page as the found tag. Notice the tag with class="story" near the top of the page. It is being purposely excluded from the loop. 4. Change the found tag to force the robot to only loop through tags within another given tag. Once the loop has been successfully created, any steps added after the For Each Tag Path step is repeated for each iteration of the loop. Steps after the loop step are executed for each iteration. In the example above showing the robot view, the robot extracts two pieces of text, a title and a preview, and return those values, for each iteration of the loop. Loop Through Tags with Different Classes Looping through tags with the same class is a common scenario, but not the most simple one you might run into. Often it is necessary to loop through tags that do not all have the same class. An alternative scenario will be explored here. The For Each Tag step is very efficient in most cases where For Tags With Class fails. The For Each Tag step loops over all types of tags, which are directly inside the found tag. It does take a little more configuration than just right-click and insert. Here is how to use it. Use For Each Tag to loop over each tag of a given type, which is directly inside the found tag. Note that the found tag contains three div tags, but they do not all have the same class. In this scenario, use For Each Tag to handle the differences. 1. Insert an empty New Step and select the For Each Tag action. 104 Kofax Kapow User's Guide 2. In the Page View, select the Found tag. 3. In the Step Action View, Tag field, select the tag type. In the preceding example, the tag type is div. 4. Add steps after the For Each Tag step. These steps are repeated for each iteration of the loop. Loop Through HTML Pages A robot often needs to loop through pages. For example, many web sites that present the results of a search request will do so over several pages, each containing e.g. 20 results from the search. To get the search results, you need to loop through the pages and process one page at a time. The following topics explain how to do this. • First Page Links to All Other Pages • Each Page Links to Next First Page Links to All Other Pages When the first page contains direct links to all other pages, you can follow a link to access any page directly from the first page. Note The first page can also contain a link to itself. In this example, you can easily loop through pages using a For Each Tag step, as shown in this excerpt from a robot. 105 Kofax Kapow User's Guide In this illustration, the robot loops through the result pages from a search request, symbolized by the Submit Form step. The first result page is processed directly, shown by the connection from the form submission step directly to the Process Page step. The remaining pages loop through using the For Each Tag action in the second branch. The Test Tag step checks to confirm there is more than one page. • If the first page links to multiple pages: 1. Loop through the tags containing the links to the pages. 2. Load each page using a Click action. 3. Continue to page processing. • If the first page links to itself: 1. Configure the For Each Tag action to skip this first link. The first page is not processed twice. Each Page Links to Next Pages are linked to a subsequent page, typically with a link at the bottom to the next page. Use the Repeat action to loop through such pages. This action loops through the pages that are supplied to it by another action named Next. See the Repeat-Next tutorial for more information. Repeat and Next must be used collaboratively to have any effect. 1. On the first page add a Repeat step. 2. Insert additional actions as required. 3. Insert a Next step. When the robot execution reaches the next step, it reverts back to the repeat step and executes another iteration of the steps. The page is transferred to the repeat step and a new page is loaded with each iteration. 106 Kofax Kapow User's Guide Note You can add other loops between the repeat and next steps to extract additional information from the page, as needed. Here, like before, we are looping through the result pages from a search request, symbolized by the Submit Form step. The form submission step will output the first result page, which we give to the Repeat action. In the first branch from the Repeat action, we process the current page. In the second branch, we load the next page by clicking its link. The Next action sends the page back to the Repeat action, which will output it in the next iteration. When the last page is reached, the Click action generates an error. To do this, the Click step is configured to terminate the loop. In the Click step, this is done in the Error Handling tab by setting the Then property to Break Loop. 4. To terminate the loop, In the Error Handling tab, set the Then property to Break Loop. If the process does not find a Next page, the process terminates. See Handling Errors for more information. An alternative way of handling the last page is shown in the following robot excerpt: You can use a Test Tag action in a second branch to detect when the last page has been reached. The Test Tag action checks that the page contains a next-page link, for example by looking for an -tag containing the text Next. If the page contains such a link, we load this page and give it to the Next action. When the last page is reached, the Test Tag action stops execution down the second branch, and no new page is given to the Repeat action, causing the loop to end. Finding the link to the next page can be tricky. A common mistake is to find the previous-page link on some pages instead of the next-page link, because the layout of the pages changes slightly between the first page, the subsequent pages, and the last page. Another common mistake is to not detect the last page reliably. You may have to configure the tag finders of the steps carefully to make things work (see Using Tag Finders). Note When you are working with a robot in Design Studio, you may not always be able to step correctly back and forth between iterations of a Repeat action. If you are not sure whether Design Studio has gotten it right, click Refresh to update. 107 Kofax Kapow User's Guide Use Wait Criteria Wait criteria in the Continue when option are powerful instruments to help you build robots that are faster and more reliable than in versions prior to 9.6. Note Wait criteria are available when using the Default browser engine. To use wait criteria, select the Execute JavaScript option on the JavaScript Execution tab in the Options dialog box. Every robot step, which requires the browser to start running, can now be configured with a set of criteria to pinpoint when the processing of an action (such as a click or a page load) has completed enough for the robot to continue. The Continue when feature, combined with the built-in algorithm allows for browser steps to run only aslong-as-needed for the robot to be able to continue. Also the user can now point and click an element on the page and create a new stop criterion for the browser step. Wait criteria can be specified in the following step actions: • Click • Close Window • Create Page • Enter Password • Enter Text • Execute JavaScript • For Each Option • For Each Radio Button • Insert Tag • Load Page • Loop Field Values • Move Mouse From • Move Mouse To • Press Key • Raw HTTP • Replace Tag • Scroll • Scroll To • Select File • • • • Select Multiple Options Select Option Select Radio Button Set Checkbox All robots created in Kapow version 9.6 and later have their default waiting set to Page Stops Changing for 500 ms. You can see this setting on the Advanced tab of the Robot Configuration window. All waitcriteria-enabled steps have a default No Page Changes for 500 ms wait criterion with the enabled 108 Kofax Kapow User's Guide Resume button, which can be seen in the Result View. this wait criterion is always grayed out in the Wait view and always met. All other browser steps have a default Initial Page Load Complete wait criterion with the disabled Resume button. This criterion is also always grayed out in the Wait view and always met. If you migrate the Default browser engine robot to a Classic browser engine robot, the following rules are applied: • If a step in the Default browser robot has a specified wait criteria, this step in the Classic browser robot is set to Wait Real-Time for Timer Events=true • If a step in the Default browser robot has Legacy timing, in addition to Wait Real-Time for Timer Events=true, this step in the Classic browser robot has Max Wait for Timer Events set to the time specified in Legacy timing. • If you migrate the same robot back to the Default browser robot, wait criteria are not restored. Adding Wait Criteria To specify a wait criterion for a step, click + in the Continue when field and select a criterion: To add Wait criteria from the Browser and Source view after execution of a wait-criteria-enabled step, right-click the browser or source view, choose Wait for from the menu, and select a criterion. The step is re-executed after the criterion is added, which is shown by the Re-execute step button in the wait criterion configuration window. Once the criteria are added, you can add, remove, move up, move down, and edit wait criteria using the panel under the list. Right-clicking a wait criterion in the Continue when list, opens an option menu to copy, cut, and paste a criterion. You can add more than one wait criterion to a step. If you have several wait criteria, execution stops when any wait criterion is met. You can have several met wait criteria such as if you are waiting for two HTML elements that appear on the same load, or if you are waiting for an element on the main frame, and Initial Page Load Completes is set. If adding a wait criteria to a wait-criteria-disabled step from a shortcut menu, the criteria is added to the previous wait-criteria-enabled step. For example, if you try to add a wait criterion after the Extract step as in the following example: 109 Kofax Kapow User's Guide the criterion will be added to the Load Page step. Wait View The Wait view shows the results of wait criteria execution as well as disabled wait criteria. Right-clicking a criterion in the list opens a shortcut menu. You can enable, disable, and delete a criterion as well as open properties for the selected criterion. For HTML Element Appears, you can select an element found in the DOM in the Browser view. This view also shows whether the page was completely loaded. If the page is loaded completely, the Resume button is disabled. If the page is not completely loaded, because of the short timeout, the Resume button is disabled and you need to extend the timeout. The Resume button in the Wait view is used to resume the browser operation after a wait criterion is met. If you have several wait criteria and one of them is met, clicking the Resume button marks the met wait criteria with a grey sign and the browser continues working until the next wait criterion is met. Once all criteria are met, clicking the Resume button starts loading the page during the time specified in the Timeout for Each Attempt option in the Options dialog box. Note The Resume button is enabled for wait-criteria-enabled steps. For default wait criteria you can click the Resume button as many times as you want. For non-default wait criteria, you can click the Resume button only once. If a wait criterion is displayed without an icon, the criterion is not met. Wait Criteria Properties Each wait criterion except Initial Page Load Completes has its settings. To configure a wait criterion, either double-click a criterion in the Continue when or Wait view, click in the Continue when view or rightclick a criterion in the Wait view and select Properties. Disabling Wait Criteria Wait criteria can be disabled and enabled in its configuration window. By default all criteria are enabled. To disable a wait criterion, clear the Wait criterion enabled check box. When a wait criterion is disabled, it is not taken into account during the step execution. Note You can right-click a wait criterion and use the shortcut menu to disable and enable a criterion. After you disable or enable a wait criterion, the previous step is re-executed. 110 Kofax Kapow User's Guide Ignore All Pending Loads When Met Each wait criterion except Initial Page Load Completes has the Ignore All Pending Loads When Met option that stops loading a page when a wait criterion is met. This option can help in cases when a wait criterion is already met, but timers continue execution and loading does not stop. This option is not selected by default. If the browser was stopped by this option, a warning sign is added to the green icon in the Wait view. HTML Element Appears This criterion is met when a specified HTML element is present in the DOM tree. This criterion configuration is similar to the Tag Finders tab in "Step Configuration", except for two elements in the Found Element Must be group: • Enabled: If this option is selected, execution must stop when result = !element.disabled; • Visible: if this option is selected, execution must stop when result = style.display !== "none" && style.visibility !== "hidden"; If HTML Element Appears criterion is met, it is marked in the Browser and Source views when you use the Select in Browser View command on the Wait view option menu. HTML Element Disappears This criterion is met when a specified HTML element disappears from the DOM tree. This criterion configuration is similar to the Tag Finders tab in "Step Configuration", except for an additional property: Initial element Detection that contains two options. • If you select Element is Found on Page option, the robot waits until an element appears on the page and only after that the robot waits for the element to disappear from the DOM tree. • If you select Wait for Fixed Amount of Time option, the robot waits the specified time and then verifies if element exists in DOM. • If the element is present in the DOM tree, the robot waits until the element disappears. • If the element is not present in the DOM tree, the wait criteria is met and the robot proceeds to the next step, even if the element has not appeared in DOM since the beginning of page load. Page Stops Changing This criterion is met if the DOM tree is not changing for the specified time. To set the time, open the criterion properties and specify a timeout in milliseconds in the Timeout (ms) text box. Initial Page Load Completes This wait criterion is met when the initial page load completes similar to the Javascript onload event. Note Though this criterion does not have the Stop All Loads When Met option, by default the loading stops when all loads are met. Waited Fixed Amount of Time This wait criterion is met when the execution is waited for a specified time. To set the time, open the criterion properties and specify a time in milliseconds in the Wait (ms) text box. Old Robots in Kapow 9.6 and Later When you open your Default Browser robots created in Kapow version prior to 9.6, you can see the following Default Waiting settings on the Advanced tab of the Robot Configuration dialog box. 111 Kofax Kapow User's Guide Default Waiting settings for Robots from previous releases is Use Pre 9.6 Default Waiting. For such robots you can change this setting to Page Stops Changing for 500 ms. • If Default Waiting is set to Use Pre 9.6 Default Waiting, adding a new wait criterion to a step produces a warning. • If Default Waiting is set to Use Pre 9.6 Default Waiting and the step is set to use the Legacy Timing wait criterion, changing the Default Waiting to Page Stops Changing for 500 ms produces an error. 112 Kofax Kapow User's Guide Upgrading Existing Robots to 9.6 If you open your robots created in Kapow version prior to 9.6 (9.3, 9.4, 9.5), depending on the Max. Wait for Timer Events and Wait Real-Time for Timer Events settings, you must perform different steps to use new wait criteria in your robots: Max. Wait for Timer Events and Wait Real-Time for Timer Events settings are not default If Max. Wait for Timer Events and Wait Real-Time for Timer Events settings are not set as default in your robots, Design Studio adds a non-editable Legacy Timing criteria to your robot. This wait criterion is always green after step execution. If you add any new wait criterion, Legacy Timing is automatically removed and you can take advantage of the new Wait criteria. Max. Wait for Timer Events and Wait Real-Time for Timer Events settings are default If Max. Wait for Timer Events and Wait Real-Time for Timer Events settings are set as default in your robots, you need to perform the following to switch to the new default settings when updating an existing robot to 9.6: go to the File > Configure Robot dialog box, click the Advanced tab and clear the Use Pre 9.6 Default Waiting check box. Now you can take advantage of the new Wait criteria in your robots. Fixing Page Load In some cases when a robot uses the Use Pre 9.6 Default Waiting or Legacy Timing options, after loading the page you get the Page loading completed message, but the page is not completely loaded. This might happen when previous page loads were aborted. To fix page load, remove the Use Pre 9.6 Default Waiting option by changing it to the Page Stops Changing option and use a new wait criterion on the step. Extract Content from HTML Design Studio has six step actions for extracting content from a tag in an HTML page: • The Extract action is used to extract text content from the tag, optionally including the HTML tags. • The Extract URL action is used to extract a URL from a tag attribute containing a URL, and make that URL absolute. • The Extract Tag Attribute action is used to extract the value of a tag attribute. 113 Kofax Kapow User's Guide • The Extract Target action is used to extract binary data such as images and PDF files, but it handles any kind of binary data. • The Extract Form Parameter action is used to extract a form parameter from a form URL in the found tag and then store its value in a variable. • The Extract Selected Option action is used to extract the selected option from a -tag and then store it in a variable. To reformat (or normalize) the extracted content, use the Extract and Extract Tag Attribute actions and configure data converters in the list. There are two actions to extract data from various binary data formats, for example, PDF or Flash. These are different from the preceding actions in that they extract the data and produce an HTML page that contains the data in a structured form that lets your robot access the data. These actions are used in an initial step before the actual data extraction, in which you may loop over the produced HTML and extract text. • The Extract Text from PDF action is used to extract text from a PDF document contained as binary data in a selected attribute. • The Extract from Flash action is used to extract data from a Flash object in a found tag. Extract Text 1. On the Action tab, select Extract. 2. To extract short text, such as a product name or a price, extract as Only Text. This extracts the text between the tags. 3. To extract longer text with sections, headings, and so on, you can select as plain text. If you want the text to appear close to how it appears in a browser, extract the text as Structured Text. 4. To extract with special markup, such as brackets surrounding the headings, select Structured Text. Structured Text has rudimentary support for special markup. 5. If the markup requirements cannot be fulfilled using the Structured Text option, select Advanced Structured Text. This option allows you to set mappings from the HTML tags into your proprietary markup. Extract Binary Data Extract binary data using the Extract Target action. On the Action tab, select Extract Target. The URL data is loaded and stored in a variable, or directly into a file. Typically, binary variables are used to store the loaded data. The available types of binary variables include Binary, Image, PDF, and Session. They are all equivalent except that the Image, PDF, and Session types allow you to preview the data. Use the Context Menu in the Page View 1. Right-click the text or tag to extract from, or right-click the link to load from. 2. On the Extraction context menu, select the appropriate option. 114 Kofax Kapow User's Guide Perform Common Tasks Extracting Only Part of a Text To extract only a part of the text in a tag, you can use patterns on the text in the tag. For example, you might want to extract the name "Bob Smith" from the following text: "The article is written by Bob Smith." To do this, use the Extract data converter (do not confuse this with the Extract step action) and configure it as described in this topic. In this example, the pattern used is ".*by\s(.*)\.", which means that the text between "by" and the period will be matched by the subpattern. For more information, see Patterns. 1. Open Extract Configuration, and select the Basic tab. 2. In the Pattern field, enter the text pattern to extract. Configure the Pattern property to match the entire text, with the text to extract matched by a subpattern, enclosed by parentheses. 115 Kofax Kapow User's Guide Converting Content To normalize content, use Conversion, such as replacing text with another text. For example, suppose you want to normalize country codes to their natural language description, such as normalizing "US" to "United States." • For plain text conversions, use the Convert Using List data converter. • For conversions based on patterns or expressions, use the If Then data converter. Extracting and Formatting Numbers 1. To extract a number from content, add an Extract Number data converter. 2. To perform additional number formatting, use the Format Number data converter. Extracting the Date from Text Extracting dates should be done in the same fashion as extracting numbers. 1. To extract a date from text, add an Extract Date data converter to your robot. Extract Date uses patterns to extract the date. The pattern does not have to match the entire text, only the date. The extracted date is converted to standard date format. 2. To perform additional date formatting, use the Format Date data converter. 116 Kofax Kapow User's Guide See the Simple Date Extraction and Complex Date Extraction tutorials for additional information. Extracting Only a Subset of the Tags in a Found Tag Sometimes, you want to extract from a range of tags rather than a single tag. For example, consider the case of extracting the body text of an article, where the body text is made up of individual sections, each in their own tag, and where information about the article title and author is contained in some other tags. To extract only the body text without the article title and author, use the Extract action to extract the text, and configure the action so that only the range of tags spanning the body is extracted. 1. On the Action tab, select Extract. 117 Kofax Kapow User's Guide 2. Specify the first tag in the range. 3. Specify the last tag in the range. Extract Content From an HTML Table HTML tables can be irregular in both content and structure. Design Studio has been designed to deal with such irregularities as described in this topic. Note The techniques described in this topic are not limited to table content and structure irregularities. You can also use this technique to handle other tag irregularities. 1. Insert a Loop Rows step in your robot. 2. Configure the Loop Rows step with a For Each Tag action that loops through the