Configuring Mapping Rules - Application Enabler - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Premier - Essential - Standard

Application Enabler

Platform
OnBase
Product
Application Enabler
Release
Foundation 23.1
License
Premier
Essential
Standard

Windows-based application configuration involves mapping keywords and hotspots. In many cases, the default settings allow Application Enabler Configuration to accurately map fields. Use the default settings for your first configuration attempt. Click Next to continue. If you accept the default settings, skip to the Logging on to OnBase and continue your configuration.

If your application does not enable during your first configuration attempt, you may need to repeat the configuration process and adjust the mapping rules described below.

If the default settings do not successfully map keywords and hotspots, you can adjust the way Application Enabler identifies them by clicking the Configure Mapping Rules button on the Settings screen and changing options on the following tabs:

Tab

Description

Order

The order in which child windows of the screen window are enumerated may be used as mapping criteria. Using just the order as mapping criteria is the most efficient mapping style for applications that keep the enumeration constant. To use the order as mapping criteria select the Use window order when comparing against this screen check box. This option is enabled by default.

Window ID

The Window ID is displayed on the Window ID tab. It is one of the properties that the operating system stores for each screen. Most applications assign a constant, unique Window ID to each of its controls, which allows Application Enabler to use the Window ID to uniquely identify a window within the application. For this reason, the Window ID is selected as the default means of identifying a screen. When a Window ID is not detected during configuration, a value of 0(zero) is stored as the Window ID. If you are configuring multiple screens in a single application and more than one of the screens stores a 0, you must select an alternate means of window identification. To choose another identifier, disable the Use window id when comparing against this window check box and choose the Order or Metrics tab.

Metrics

Some applications display screens within a parent window. When enabling this type of application, Application Enabler can use the position of the screen within the parent window to identify the screen.

Relative Position

If the application screen can be resized and the edit field is resized by an equal height/width ratio, Application Enabler can use the relative position of the field as an identifier. The relative position is measured as a percentage of the length or height of the application screen. Horizontal Location and Vertical Locations are the options available.

Accepted Delta Variance

Most applications render their screens using the exact same size and location for all fields within a given screen. Some applications render fields within a screen at a slightly different location and/or size depending on the hardware, fonts, operating system, and other factors. This variance keeps Application Enabler from being able to identify such fields. This setting only applies when using metrics for the mapping rules. The value for the Accepted Delta Variance specifies how many units the X or Y coordinates of enabled elements can vary before the elements are no longer matched by the Application Enabler. See Determining the Accepted Delta Variance for more information.

Note:

When configuring screens, the settings are remembered from the previous screen's settings within the application.