AR System forms overview
Forms are the foundation of Action Request System. A form captures and displays information, and a set of forms can be grouped into an application. A AR System application is a server object that contains references to one or more forms. When an application references a form, AR System automatically includes all the workflow and other components (such as menus) associated with the form in the application.
Sometimes a single form can contain all of an application's functionality. For example, a small application that tracks product defects can use a single defect-tracking form to capture and display all required information.
Most applications, however, need several forms to capture, track, and organize information. One or more forms make up the application's main forms (sometimes called primary forms) that users interact with directly. Often, the main form is a console that serves as a navigation and information center. The application can also have other forms, called supporting forms, which supply information that the main forms need. For example, a service desk form captures information needed to fix a user's computer problem. A purchase requisition form captures the information needed to purchase an item. The following figure illustrates a AR System form.
Each form contains fields. Some fields, known as data fields, capture a certain type of information, such as a user name or problem details, and have their own set of rules about who can view or modify that information (see Fields-overview). Some fields can have attached menus that help users fill in the form (see Field menus).
Watch the following video (3:13) to get an overview of AR System forms:
https://www.youtube.com/watch?v=l4tSKd327eY
Example of a AR System form
Each form in an application is like a template to capture or present information. When a user opens a form to perform a task, the template is presented to help the user complete the task. When the form is filled in and submitted to AR System, the system creates a request, also known as a record in database terms.
Forms are stored as tables in the database. Each data field on the form corresponds to a column in the table. A request corresponds to a row (or record) in the table.
A form from the view of the database
Form types
You can create the following types of forms, as illustrated in the following figure.
Form type | Description |
|---|---|
Regular | Information submitted through and displayed in regular forms is stored in database tables. These forms are typically the main forms in applications. They are also called data forms. |
Display-only | These forms contain display-only fields that enable users to accomplish specific tasks. These forms are typically used to create control panels, which are launch points from which users choose other tasks. Display-only forms can also be used to create dialog boxes, which prompt users as they fill out a form. Display-only forms do not contain data, so no database tables are associated with them. |
Join | These forms are composed of fields from two or more existing forms. Join forms are useful when you have information in multiple forms that you want to display in a single form. Join forms do not contain data, so they have no database tables associated with them. The data is contained in the underlying forms that make up the join form. |
View | These forms enable users to connect to database tables created outside of AR System. These forms enable you to bring data from other applications that is stored in a database into AR System without replication or programming. |
Vendor | These forms enable users to connect to external data sources such as text files, spreadsheets, or database tables residing on local or remote servers through an ARDBC plug-in. Some programming is required to connect to the data source. |
Form views
A view is a visual representation of a form. To reuse a form for diverse groups while accommodating each group's unique needs, you can create a different view of the form for each group. This enables you to customize the interface of a AR System application so that each group sees the system as its own.
You can create as many views of a form as you need. For example, you can provide views customized according to the following criteria:
- Users' roles (requesters, managers, and so forth)
- Size of the screen (for example, laptop or desktop)
- Language or locale (for example, Brazilian Portuguese)
When creating form views, you can:
- Change the layout of the form
- Use different fields in different views
- Tailor views to provide the best result in the target display environment, such as a browser
- Use terminology or language specific to the group using the view
Related topic