AR System Administrator

From Wikipedia, the free encyclopedia
Jump to: navigation, search

AR System Administrator is a client application of Remedy's Action Request System. It is used exclusively for building, customizing, maintaining, and supporting AR System applications. It reads and writes data to the metatable section of the AR System's database.

From Version 7.5 of AR System Platform, AR System Administrator is replaced with Developer Studio, which is based on Eclipse Plug-ins.

Objects created and modified via AR Administrator[edit]

These are the objects that AR Administrator is tasked with creating, modifying, and maintaining. Definitions of some of these can be found in the Action Request System article. Forms

  • Forms(Regular Form,Join Form,Vendor,View,Display only Form)

Types of forms There are five types of forms you can create: regular, display-only, join, view, and vendor. Regular forms, or data forms, are the forms discussed so far that contain information stored in database tables. Display-only forms contain one or more display-only fields that enable users to accomplish specific tasks. They are most commonly used to create control panels, which serve as launch points from which users choose other tasks. (Control panels are discussed in more detail in the section “Acting as a control panel” on page 38.) Display-only forms can also be used to create dialog boxes, which prompt users as they fill out a form. (For more information about dialog boxes, see the section “Open a window” on page 83.) Display-only forms do not actually contain data, so no database tables are associated with these forms.

Join forms are composed of fields from one or more existing forms. They are useful when you have information in multiple forms that you want to display as a single form, for example, for reporting purposes. Like display-only forms, join forms do not actually contain data, so they have no database tables associated with them. The data is contained in the underlying forms that comprise the join. Join forms are discussed more fully in the section “Join forms” on page 40.

View forms enable users to connect to database tables that were not created by the AR System. View forms enable you to bring data from outside applications that are stored in a database directly into the AR System without replication or programming.

Vendor forms enable users to connect to external data sources, such as text or spreadsheet data, that reside on local or remote servers. Vendor forms enable you to bring data from other applications that are not stored in a database, using the AR System without replication; however, some programming is required to link to the other data source.

  • Active Links

An active link is an action or group of actions performed on the client, which is the portion of the software with which users interact. Active links are triggered by user actions on the screen and can be used to perform a variety of tasks, such as giving quick responses during data entry and auto-filling fields. For example, an active link can verify the value in the Employee ID field after it is entered and pull information from a supporting People form to fill in the values for other fields on the form, such as Requestor Name, Department, and Phone Number, dramatically reducing the time it takes support staff to fill out a request.

A group of active links can be combined in an object called an active link guide. Active link guides can augment training by leading users through the steps necessary to fill in one or more forms to accomplish a specific task. For example, an active link guide could open a business cards form and then display input instructions, field by field, until the request is complete and ready to submit. Active link guides can also be used as subroutines to accomplish common tasks.

  • Filters
  • Escalations
  • Guides
  • Applications
  • Packing Lists
  • Menus
  • Distributed Mappings
  • Distributed Pools

Administrative changes not handled by AR System Administrator[edit]

Although AR Administrator is designed to handle admin needs, some administrative changes are made via AR System User.

  • Adding/removing users records
  • Changing User Name and passwords
  • Modifying user permissions
  • Changes to data-driven functionality

Since the AR System has an open API, source code can be written and called from the AR User that creates workflow. This technique is used in the service level agreement application, as well as the Business Rules module of Remedy CRM versions 4 and earlier.

External links[edit]