|
This topic guides you through the Capture step of the Application Document Wizard for an Application Document template.
Review best practices for optimal results.
Use the options in this section to build a catalog of images capturing each of your application's UI components.
Start by selecting a skin in the Preview Style field. The value you select applies style and formatting to your application so you can preview different options in your screenshots without physically changing the application's skin.
Click Capture All to build the initial Screenshot Catalog table. Wait for the progress bar to complete and then review results for each image in the Status column of the table.
Click the Detect Updates button in subsequent iterations of the wizard to find and review rules that need new or updated screenshots. You can ignore the results or click Capture Updates to update the image catalog.
The message No screens to capture appears in this section when you have not: selected any case types to document, defined screenshot data, or linked any specifications to connectors in your flows.
Use the table in this section to review and override your application screenshots. Each row represents an image of a rule such as a harness or flow action.
Use the column headers to sort and filter results. Interact with each column to customize the results:
|
Column |
Description |
|
Name |
The name of the Image Content data instance containing the screenshot. Click to open the rule. |
|
Type |
Read-only. The type of rule captured in the screenshot. |
|
Applies To |
Read-only. The applies to class of the rule captured in the screenshot. |
|
Override |
An action you can take on a screenshot. Click Add to override the original image with a custom image. Click View to open a custom image. |
|
Status |
Read-only. The result of the most recent screen capture process. Screenshots with a Failed status appear as a placeholder image in the generated document. |
Click Document Now to review your screenshots in the generated document, or continue to Step 4 to configure the table of contents.
 Step 2
|
Step 4
|