AR System installed forms
AR System server installed forms A to C
Form name | System | Description |
Application forms:
| + | Used for queuing processes and requests. This form works with the Dispatcher thread, which routes requests to the appropriate queues. The Dispatcher wakes up the process that the Application Pending request indicates requires execution. For more information about the Dispatcher thread, see AR-System-server-architecture-and-scalability. |
| + | Used to monitor and analyze the performance of your deployable applications and forms.
|
| + | Verifies or changes application and form statistics logging settings. |
| + | Defines the development state (such as Test or Production) for a deployable application. You can edit the entries in this form in the user client or create workflow that acts on this form to change the application's state. Changing the state changes the access permissions to the application (and to objects owned by the application) according to the role-group mappings defined for each state in the Roles form. See Specifying-roles-for-deployable-application-states for more information about application states. |
| + | Required by the following applications (and their earlier versions) to load their systems, sub-systems, and help:
|
| + | |
AR System Message Catalog | + | Enables administrators to provide localized versions of error messages, help text, menus, and other text strings displayed to users in applications that are customized by locale. The use of this form can be enabled or disabled. See Localizing AR System applications for how to use this form. |
AR System Object Relationships | + | View forms providing access to the object relationship data recorded when Record Object Relationship is selected on the Configuration tab of the AR System Administration: Server Information form. For more information, see Setting-administrative-options. |
AR System Orchestrator Configuration | + | Used by administrators to configure the integration between AR System and TrueSight Orchestration. For more information, see Defining-TrueSight-Orchestration-web-services. |
AR System Resource Definitions | Used to define templates. For more information, see Resources-for-templates. | |
AR System Searches Preference | Stores searches that users can create and save for a form. Each search is an entry in this form. For more information, see Types-of-browser-searches-for-end-users. | |
AR System Server Group Operation Ranking | + | Stores the ranking of servers for operation ownership within a server group. This form is loaded only when the AR System server is configured to be a member of a server group. |
Assignment Engine forms:
| Used to run the Assignment Engine. For more information, see Automatic-request-assignment. | |
BMC Atrium Web Services Registry integration forms:
| + + | Used by the integration between AR System and the BMC Atrium Web Services Registry. For more information, see Registering-a-web-service. |
Alert forms:
| + | Contains alerts that are sent to users. If a notify action of a filter or escalation sends an alert, the alert text and reference is stored in this form. For more information, see Enabling-alert-notifications. |
| Provides a web view with an alert list field already created. You can add this form to your web-based applications for viewing lists of alerts in a browser. | |
Business Time forms:
| + + + + + + + | Used to define periods of availability and unavailability, workdays, and holidays to calculate business schedules. For more information, see Business-Time-introduction. |
Currency forms:
| + | Holds the currency codes that are available on a server. Each code can be activated or inactivated by checking the Active field on the form. Activating a currency code makes it available to the clients. |
| + | Contains localized labels that override the currency codes in the menus associated with currency fields in browsers. |
| + | Queried by clients to retrieve overridden currency labels. There is no interaction with this join form. |
| + | Holds the ratios for converting one currency to another. This form can include ratios for both conversion directions (for example, from USD to Euro and from Euro to USD) because these conversion rates are sometimes different. This form can store current and historical conversion rates. |
AR System server installed forms D to L
Form name | System | Description |
Data visualization forms:
| Used to set up a data visualization module to display graphical data in a field on a form. For more information, see Data-visualization-fields. | |
DSO forms:
| + | Defines and maintains parameter and data control values for a specific distributed mapping. |
| + | Maintains a queue of pending distributed transfers, updates, returns, and deletes. |
| + | Maintains a queue of failed pending distributed operations. Includes information about the error that caused the failure. |
| + | Defines and maintains definitions of specific distributed pools. |
Flashboards forms:
| Used to create and add flashboards to a form and to handle them at run time. For more information, see Creating-and-managing-access-control-groups. | |
Group | Used to create access control groups to which you grant or deny access to AR System objects. There must be exactly one Group form defined on a server. See Creating-and-managing-access-control-groups for how to use this form. | |
Home Page | Used as a convenient starting point for administrators and site managers to display entry points. This default form is automatically installed with AR System. | |
inetorgperson | Provided as an example form based on an industry standard directory service user schema. Each field on the form references an attribute defined by the inetorgperson object class. | |
LDAP forms:
| Enables administrator to view and modify configuration parameters for the ARDBC and AR System External Authentication (AREA) LDAP plug-ins that are stored in the AR System Administration: AR System Configuration Generic UI form. Requires the Configuration ARDBC plug-in. For more information, see ARDBC-plug-ins-introduction. | |
| Enables administrators to view and modify the parameters for the AREA LDAP plug-in. The parameters are used to query the LDAP-enabled directory service for authentication purposes and user information. | |
| Enables administrators to view and modify the parameters for the ARDBC LDAP plug-in. The parameters are used to establish connections with LDAP-enabled directory services. | |
Licensing forms:
| + | Used to add, activate, modify, deactivate, and remove licenses for the AR System server, server components, and applications based on AR System. For more information, see Adding-or-removing-licenses. |
| Tracks all licenses currently in use on the server when the Enable License Tracking option is selected in the AR System Administration: Server Information form. Note: AR System Current License Usage form tracks only fixed and floating licenses. | |
| Tracks information about licenses that are released when the Enable License Tracking option is selected in the AR System Administration: Server Information form. Note: AR System Historical License Usage form tracks only fixed and floating licenses. | |
| + + | Internal supporting forms for licensing. |
Log forms:
| + + + + + + + + + + | Receives log information when a log mode is configured to log to a form. For more information, see Working-with-logs. |
AR System server installed forms M to Z
Form name | System | Description |
Metadata forms | + | View forms used by AR System client programs to access server objects. These forms are not designed for access using the browser. |
Preference forms
| Store user preferences centrally, providing "roaming profiles" for any AR System user. These forms are loaded when they are selected in the Select Action Request System Components dialog box during installation of the AR System server. Users can access these forms in a browser to view and set their preferences. In Developer Studio, select Window > Preferences to set preferences. For more information, see Setting-user-preferences. | |
Query builder widget forms
| + | Enables developers to configure the fields displayed in the Query builder widget list. Defines unique query information to be displayed in a query widget |
| + | Enables developers to configure the fields displayed in the Query builder widget list. Backend form that contains the list of fields to be allowed in creating the query |
| + | Enables developers to configure the fields displayed in the Query builder widget list. Join form that can be used by the Query builder widget to get the list of field IDs and information to be used in the Query builder widget |
Reporting forms:
| Links reports to forms on the same AR System server that hosts the Report Form, and provides the structures needed for granting permissions to run a report for specified groups. Administrators and individual users can submit entries to this form. For more information, see Defining-reports-and-permissions. | |
| Provides the interface to create and maintain AR System native report definition files. This form is a vendor form using an ARDBC plug-in. The data is actually stored in the Report form as attachments. This is a legacy report form. For more information about this form, see Where-reporting-tasks-are-performed. For more information about ARDBC, see ARDBC-plug-in-API-functions. | |
| Records report file names. | |
| Specifies how each type of report is created, edited, and run. Generally, only administrators can submit or modify entries in this form, but users must be able to view the entries. For more information, see Defining-report-types. | |
| Used in workflow to prompt users to select a report to run. This form has no entries. This is a legacy report form. For more information, see Where-reporting-tasks-are-performed. | |
Roles | + | Defines roles for each deployable application, and maps the roles to explicit groups on the server. You must map roles to groups for each application development state, such as Test or Production. See Creating-and-mapping-roles for how to use this form. There must be exactly one Roles form defined in a server. |
Server Events | + | Contains a record of internal events for a particular server. Event types that can be recorded include server structure changes, user and group changes, and server setting changes. Set options for recording server events using the AR System Administration: Server Information form of the AR System Administration Console. For more information, see Capturing-server-events-for-workflow-or-API-calls. |
Server Statistics | + | Enables the server to automatically store server statistics. These statistics can then be graphically displayed by client programs such as Flashboards and used to analyze server performance. For more information, see ARGetServerStatistics. |
User | Used to define users, their characteristics, and their access rights within AR System. There must be exactly one User form defined on a server. For more information, see Creating-and-modifying-users. | |
User Password Change | Used by users to change their passwords. | |
Version control forms: | For information about the features that use these forms, see Version-control-in-AR-System. | |
| + | Stores information about labels used to identify a collection of objects for versioning purposes. See Version-control-in-AR-System. |
| + | Stores information that links a version control label to various objects. See Adding-version-control-labels-to-objects. |
| + | Records changes to server objects. |
| + | Records object reservations. |
| + | Reserved for future development. |
View selection forms:
| Stores actor definitions for actor-based view selection. Each actor is an entry in this form. See Configuring-actor-based-view-selection. | |
| Stores information that links actors to views for actor-based view selection. See Configuring-actor-based-view-selection. | |
Visualizer forms:
| Store Visualizer configuration. |