Flow Action form
Completing the HTML tab

Field

Description

Select:

• Reference HTML to use an HTML rule that defines the presentation.
• Reference Section to use a section rule that defines the presentation. This approach is often suitable to present an embedded list view to users. See How to present a list view display within a section.
• No HTML to indicate that this connector flow action requires no user input. B-20520 BUG-4748 not No Prompt.

The Define Form value, available in flow action rules created in releases before V6.1+, is deprecated and not available for new flow action rules. See More about Flow Action rules.

Selecting Reference HTML, displays the HTML Reference field.

Enter the second key part — Stream Name — of an HTML rule that defines what appears when a user at runtime selects this flow action from a Perform harness form. The system uses the Applies To key part of this flow action as the first key part of the needed HTML rule.

If this flow action doesn't require users to read or complete any fields, you can identify an HTML rule that doesn't contain any fields. The standard flow action Work-.ActionNoFields meets this need.

Select to cause your application to immediately validate the format of user input to dates, integers, and other fields within the browser window when focus leaves the form field, before a user submits the form. C-1197 42SP6

This checkbox affects the input of many dates, times, text areas, and selected other properties, depending on the HTML Property rule associated with the property at runtime. See client-side format validation.

This feature operates best for those Flow Action forms that use the SmartFrames version of the Layout  tab and use only JSP tags, no directives.

Select to enable client-side format validation here for this flow action form. A similar checkbox on the HTML tab of the Harness form enables client-side format validation for the rest of the work object form, exclude the Take Action area. GROVS 5/2006

As a best practice, check when users are to enter dates, times, integers, or text through typing rather than through selection. Workstation-level validation can detect and mark invalid input earlier, and may consume less network traffic and bandwidth. Do not select if the flow action form contains only checkboxes, selection lists, combo boxes, and other input widgets that do not require typing.

Standard client-side validation scripts are in the text file rule webwb.CSValid.js; the corresponding error messages are in the HTML fragment rule CSValidBug-13661 GROVS 12/4/08 to allow for localization. You can add custom client-side validation scripts or error messages on an application-wide by overriding the HTML fragment rule UserWorkForm, which is included in the fragment WorkFormStandard, which in turn is included in the HTML code for every work object form. R-20339

Select to enable automatic update of the display of certain computed property values on the flow action area of the work object form. C-2337 For example, the flow action runtime form may contain a total that sums values entered into an array.

You can enable this if the flow action form:

• Displays one or more properties computed by Declare Expression rules using forward chaining.
• Allows users to input another property value that affects the computed property.

Computation begins when user focus leaves the input field for a source property. The workstation transmits the input value to the Process Commander server (using Asynchronous JavaScript and XML or AJAX), which applies the declarative rules and sends the results back for display. Only a portion of the form is redisplayed. Results may include a message indicating that a constraint was not met.

For Declare Expression rules, both the input property or properties and the computed or target property must appear on the flow action form, not elsewhere on a work object form. See More about Declare Expression rules.

A similar but separate checkbox appears on the HTML tab of the Harness form; that field controls automatic expression calculation in areas of the work object form other than the Take Action area.

Reference Section is the default setting for all flow actions created in V6.1+. Flow actions automatically include a section.

Select On to indicate that you have designed and implemented your HTML to meet your accessibility requirements.

The Application Preflight tool evaluates this field on each rule in an application that displays it, when calculating application accessibility levels for the preflight Accessibility Report. See Using the Application Preflight tool.PROJ-901 5.4

Indicate which browsers and versions can correctly process the HTML code from this rule.

When you specify that the code is to be auto-generated, Process Commander includes only those tags that can be displayed across recent versions of Internet Explorer, Firefox, and Safari, and the value of this field is set to IE 6+, Firefox 2+ and Safari 3+6.1. The value is read-only.

If you edit the generated code or manually provide the code for the rule, specify the browsers that can display it. When you do not use auto-generated code, Process Commander does not validate your code. You must determine that it can be displayed across the browsers and versions you specify.

The Browser Compatibility Report, in the Preflight tool, checks this field to determine what percentage of the rules in your application provide cross-browser support.PROJ-282 5.4

If your application includes auto-generated harness rules that you created in a version prior to V5.4 that include only sections and properties where the value of this field is set to IE 6+, Firefox 2+ and Safari 3+6.1, open and resave such section rules in V5.4 to have this field correctly reflect the setting. MAYED S4/24/08 SR-16854

Selecting No HTML generates the following message in the Layout tab:

This layout is NOT Auto Generated.
(No HTML must be checked to show this view. See HTML Tab.) Issue - the Auto-generated box is no longer there! check up on this and change text - HG