Add a form when a workflow requires capture of index data.
|Form Name||The name of the form to be displayed on the desktop hierarchy. A maximum of 32 characters are displayed by the AutoCapture client.|
|Icon File||Browse to the folder location that contains image icon file for this menu entry. The menu icon is 12x12 on the standard windows explorer AutoCapture client.|
|Button Name||The button name that will be displayed at the lower right corner of the form. Use a descriptive action name such as "Submit".|
|Form Type||Choose one of the two form types:
Style Sheet — Enter the name of an XSLT style sheet. The style
sheet contains templates that match XML element names for field types
(ACBoolean, ACButton, ACDateTime, ACLabel, ACNumber, ACString, ACList,
ACStringMultiline). If you leave this field blank, the AutoCapture default style sheet
The default style sheet is AC.xslt, which is located at the AutoStore installation directory. The style sheet contains templates that match XML element names for field types (ACBoolean, ACButton, ACDateTime, ACLabel, ACNumber, ACString, ACList, ACStringMultiline).
You can copy the default style sheet and use it as the basis for creating your own XSLT style sheet that formats your form. When a user right clicks on a file and selects a form, the AutoCapture client retrieves the form definition from the server in XML format. The form definition has all the field setting definitions for the form. The XSLT style sheet specified here transforms the field definitions to display in HTML format. The HTML code uses the cascading AC.css, also in the AutoStore installation directory, which you can edit to change how content is styled, as defined by your business needs.
Whether you copy and modify the default XSLT style sheet or create your own from scratch, your XSLT style sheet must render of the ACForm element as defined in the AutoCapture XML schema.
If there are references in the custom XSLT style sheet to external files, you can enter a "comma" or "semi-colon" separated list of files in the following order:
Script File — Enter the VB Script file name for loading/validating the index data on the client.
Run on form load — If this option is checked, the provided script file will be executed on the server prior to loading the form on the script enabled client.
Run on form validate — If this option is checked, the provided script file will be executed on the server to determine if the form data submission is allowed.
Add fields by clicking on the new field button, labeled by N in the column header. After you add a field, you can press the Tab key to navigate between field attributes and to add additional fields.
For each field you can configure the field attributes:
On submission of the form, all the standard HTML control name/value pairs along with any hidden fields (the name of the hidden field must end with _RRT) will be captured as RRT enabled meta data.
|RRT Fields||A comma-separated list of field names contained on the web form to be populated in the available RRT window when configuring the other components in the task. This field is optional as RRTs may be entered in the fields on the web form using RRT syntax (for example, ~ACC::%WebForm_Field1%~ ).|
The Components tab lists processing and routing components in a workflow, their description, type, and the configuration button to set component options. The configuration button is labeled by the ellipsis (…) in the last column of each row.
Select a component by clicking the configuration button and configuring options in its properties dialog box. For some components, you have to explicitly activate the component by selecting the Activate button in its properties dialog box. Others are activated after you configure options that allow them to function, such as the destination folder for the Send To Folder component.