How form views are selected

To provide each user with the best possible view of a form, AR System server uses this order of preference to determine which form view to display:

  1. View requested by a user or by workflow. For example, a view can be specified in an Open Window active link action or a URL for the browser. If no view is requested, or if the requested view does not exist, the default view is used.
    When Mid Tier is the client and if the view is not specified in the URL, then Mid Tier determines the view to display by evaluating the below high-level criteria:

    • The view label or name is matching with the value of Default Form View field on the AR System User Preference form.
    • The view label or name is matching with the default view of form from the application properties.
    • The view label or name is matching with the value of the View Label field defined on the AR System Actor View form.
    • The view is configured as default view in the form definition.
    • The view is configured as default view in the form definition and view label or view name is matching with the value of Open Window View Extension field on the AR System User Preference form.
    • The view locale value is empty.
    • The view country value is matching with the country value of the current user session locale.
    • The view language value is matching with the language value of the current user session locale.
    • The view type is matching with the value of Prefer Standard/Windows View option (standard or web) in the Mid Tier Configuration Tool.

    For more information, see Configuring-the-mid-tier.

  2. Actor-based view.
     This view represents the function that a user performs in an application. For example, a user might use an application to manage, submit, or audit help desk requests. In AR System server, each of those functions, manager, submitter, auditor, is called an actor. Each actor can be associated with a different view. See Configuring-actor-based-view-selection.

    An actor is not related to access permission roles.

  3. Default view specified in the User Preference form.
  4. Default view specified in the form.

After using this order of preference to select a base form view, the system selects a version of the base view appropriate for the user's locale. If no version exists for that locale, a fallback mechanism finds the closest possible locale to the one requested. The resulting view is then displayed for use. The following figure illustrates the AR System form view selection process:

view_selection.gif