This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Setting administrative options

Use the Configuration tab to set administrative options.

To set configuration options 

  1. In a browser, open the BMC Remedy AR System Administration Console, and click System > General > Server Information.
    The AR System Administration: Server Information form appears.
  2. Click the Configuration tab.
    AR System Administration: Server Information form — Configuration tab

    Edit the options, as needed:

    Configuration tab fields

    Field NameDescription
    Users Prompted For Login

    Specifies whether users are prompted for their log on credentials.

    • By Preference --- The prompt appears by preference.
    • Once Only — The prompt appears only once per session.
    • Always — The prompt appears every logon session.


    This field is not required for BMC Remedy Mid Tier.

    Max Entries Returned by GetList

    Limits how many database entries are displayed on one page from search result.

    For example, setting the maximum entries to 50 shows 50 entries on each subsequent pages for the given search result.

    If you specify a maximum in their preferences, the lesser value is used. 0 (default) specifies 2000 entries per page.

    Server Table Field Chunk SizeFor server-side table fields, determines the number of entries (or size of the chunk) that the server retrieves at one time from the database and stores in-memory to process during filter or filter guide actions. The server then retrieves, stores, and processes the next chunk until all the rows are processed. Entering a value of 0 causes the server to retrieve an unlimited number of rows. The default is 1000 rows. Entering a low value in this field causes the server to process smaller chunks, which keeps the server memory usage down, but results in slower processing because the server needs to access the database many times, especially for large tables. Entering a high value causes the server to retrieve and process large chunks of data and access the database fewer times. This results in higher performance at the cost of memory use.
    Server LanguageDisplays the language and character set of the computer on which the server is running.
    User Email Notifies FromIdentifies the sender of email notifications. The default sender for email notifications is ARSystem. To specify another user name, enter that name in this field. The name must match the name you use in the BMC Remedy AR System Email Configuration Form for notifications. For more information about configuring a mailbox for notifications, see Sending notifications.
    Minimum API Version

    Specifies the oldest version of the C and Java APIs with which the server communicates. The corresponding API and BMC Remedy AR System versions are as follows:

    Remedy AR System
    Minimum API version

    If you set the minimum API version to 14, clients earlier than version 7.5.00 cannot communicate with the BMC Remedy AR System 7.5.00 or later server. If you set the API version to 0 or none, all clients can communicate with the server. For information about setting passwords to increase security, see Configuring server groups.

    Default Home Form

    Specifies the path to a home page form to be used system-wide as the default home page for this server when a user logs in. This default Home form is only used if one of the following statements is true:

    • This server is designated as the server for the home page in the BMC Remedy AR System User Preference form.
    • This server is designated as the home page server on the General Settings page in BMC Remedy Mid Tier Configuration Tool. See Homepage Server.
    • No home page is specified in the BMC Remedy AR System User Preference form.

    Note: If the home page form is deleted, this field is cleared and you must re-enter a default home page.

    Max Number of Password Attempts 

    Specifies the maximum number of consecutive bad password attempts allowed for a user after which the user account is marked INVALID.

    For example, if the value is set to 3, the user has 3 chances to log on. If all 3 attempts have bad passwords and the user enters a bad password in the fourth attempt, then the user account is marked INVALID.

    Values for this field are 0 (turns features off) and all positive integers. This option can also be set with the AR System Configuration Generic UI form.

    This parameter can be used in conjunction with Display-General-Auth-Message. See Configuration settings C-D. See also the description for error 624.

    Next Request ID Block SizeSpecifies whether to allocate Next-IDs in blocks rather than one at a time. Allocating in blocks increases performance during a create operation. To allocate in blocks, enter a positive number greater than 1 (up to 1000). The default value is 1 (Next-IDs are not allocated in blocks). If 0 or a negative number is used, the server uses the default value of 1. You do not need to restart the server for the change to take effect. The option is started immediately. Warning: The use of this configuration setting might result in unpredictably large Next-ID sequence gaps. The likelihood of this occurring increases with the use of multiple servers that share a database. The BMC Remedy AR System server does not malfunction because of this gap and should not be considered a defect.
    Allow Guest Users

    Specifies whether BMC Remedy AR System permits access to guest users, who are not registered users of the system, to log on. If the check box is selected (default), guest users can log on and perform the following tasks:

    • View all forms and fields for which the Public group has Visible permission.
    • Execute all active links for which the Public group has permission.
    • View all fields for which the guest user is the submitter or assignee, if the Submitter Group or Assignee Group has View permission for the field.
    • Submit new requests if the fields on a form have the Allow Any User to Submit check box selected. See Special submit setting.
    • Modify all fields for which the guest user is the submitter, if the Submitter Group has Change permission for the field and if the Submitter Mode is Locked, as described in Setting license options.
    Give Guest Users Restricted ReadDefines whether guest users receive a restricted read license when they log on to BMC Remedy AR System. If this option is not selected, guest users receive a read license.
    Allow Unqualified Searches

    Defines whether the server accepts unqualified searches (searches for which no search criteria are specified). If the check box is

    • Selected (default) — All database searches are allowed.
    • Cleared — You force users to enter a search criteria when performing queries.

    Note: Consider restricting unqualified searches to prevent the performance penalty of retrieving and returning large blocks of data because of accidental unqualified searches to the database. 

    Administrator-Only ModeEnables only administrators and sub-administrators to access BMC Remedy AR System. Users who are not administrators or sub-administrators cannot perform any BMC Remedy AR System operations. This is useful during system maintenance. By default, this option is not selected. Only administrators (not sub-administrators) can set the Administrator-Only Mode. After an administrator sets this option, sub-administrators can access only forms for which they have permission.
    Disable ArchiveDisables the archive operations on the server. You can disable one server operating with one database, but in the case of multiple servers attached to the same database, you can disable all servers except one to prevent conflicts. By default, this option is not selected. See Archiving data. Server groups can be configured in the BMC Remedy AR System Server Group Operation Ranking form to make sure that only one server performs the operation. See Configuring server groups.
    Server Group MemberIndicates whether the server is a member of a server group. By default this option is selected and is not changeable.
    Disable Admin Operations

    Disables certain operations performed only by administrators and sub-administrators, which enable you to control changes to the database by disabling administrator (Developer Studio) operations. You can disable one server operating with one database, but in the case of multiple servers sharing same database, use this setting to disable all servers except one to prevent conflicts. If the check box is

    • Selected — Administrators cannot perform operations that affect the server's data dictionary.
    • Cleared (default) — Administrators can perform their usual operations including all data dictionary restructuring operations.

    If the Server Group Member check box is selected, this setting is ignored. Server groups can be configured in the BMC Remedy AR System Server Group Operation Ranking form to make sure that only one server performs these operations. See Configuring server groups.

    Disable Escalations Enables you to stop escalations running on the server. You can disable one server operating with one database, but in the case of multiple servers attached to the same database, use this setting to disable all servers except one to prevent conflicts. By default, this option is not selected. If the Server Group Member check box is selected, this setting is ignored. Server groups can be configured in the BMC Remedy AR System Server Group Operation Ranking form to make sure that only one server performs escalations. See Configuring server groups.
    Disable AlertsEnables you to prevent alert messages from being sent to users when an alert event is entered in to the system. No threads are run in the Alert Queue. This setting is acknowledged only at startup, so any changes do not take effect until the server is restarted. By default, this option is not selected.
    Verify Alert Users

    Indicates whether the server needs to check its list of registered alert clients to determine if they are listening and ready to receive alert messages. This setting is acknowledged only at server startup, so any changes do not take effect until the server is restarted. Selecting this option can result in a large amount of network activity at server startup. If the check box is

    • Selected — The server verifies the list of clients. If the clients are not listening, they are removed from the list of registered clients.
    • Cleared (default) — The server does not perform the verification.

    Regardless of the setting, if a subsequent alert message is sent to a client that is not listening, the client is removed from the list of registered clients.

    Enable Multiple Assign GroupsEnables multiple roles, groups, and user names to be stored in the row-level security Assignee Group field (ID 112) and in dynamic group fields (ID 60000-60999     ). This enables multiple users, or users from multiple groups, to access the same entry (as in the sample qualification, 'Assignee Group' = ";50;51;-90;'Mary Manager';" ). If the check box is not selected (the default), only one role, group, or user name can be stored.
    Disallow Non Unicode ClientsWhen selected, restricts server access to Unicode-safe clients. This option applies to all non-Unicode clients. This check box is visible only for AR System 7.0.00 servers or later. If the server uses a non-Unicode database, the check box is disabled.
     Record Object Relationships

    Determines whether the AR System server records the relationships between workflow objects. If the check box is

    • Selected — The server creates entries in a database table to track the relationships between many types of workflow objects.
    • Cleared(default) — The server does not record relationships.

    Note: If using a server group, all servers within the same server group must have the same setting for this option. If they do not, the servers in the group inconsistently populate and un-populate the object relationship database should they be the highest ranked server for the Administration operation when they are restarted. Only the highest ranked server for the Administration operation in the server group will perform the required object relationship actions when restarted.

    When the server is recording relationships, it updates the relationship data whenever an object is created, modified, or deleted. You might notice that installing an application or importing a large number of objects takes longer because of additional database operations.

      • When you select the check box, it records the relationships of all server objects before it accepts connections from clients. Therefore, the first time you set the value to T, you cannot connect to the server by using any client temporarily. The more the number of objects defined on the server, the more time it takes to connect to the server. With a large number of objects, such as with an ITSM application installed, and depending on the performance of the database, this could take up to an hour. When you can reconnect to the server, the recording of object relationship data is complete.
      • When you clear the check box, it removes all the recorded relationships from the database. This option must be selected on a development server to enable the following features of BMC Remedy Developer Studio:
    • Analyzer
    • Search
    • Show Relationships

    For more information about Analyzer, see Using Analyzer to find problems in your applications. For more information about Search and Show Relationships, see Relationships tab. Also, BMC Remedy Developer Studio uses that object relationship data, if available, to improve performance of some features, including object lists, related working lists, and exporting related objects. To view these relationships directly, use the BMC Remedy AR System Object Relationships form.

    Max Attach SizeSpecifies the maximum size of the attachment in bytes. The default is 0, which allows users to attach files of any size.
    Use Prompt Bar For

    Specifies whether system messages appear in the prompt bar or a pop-up box. The options are:

    • Notes and Warnings (default) — Notes and warnings appear in the prompt bar, but Errors appear in a pop-up box.
    • All System Messages — All system messages appear in the prompt bar.
    • None, Show in Popup — No messages appear in a prompt bar. Instead, all messages appear in a pop-up box.
    Required Field Identifier

    Specifies the character to add to the label of a field whose entry mode is Required.

    • Prefix on Label — Add the character to the beginning of the label.
    • Suffix on Label (default) ---  Add the character to the end of the label.
    • Identifier — The character to add to the label. The default is an asterisk.

    For information about field entry modes, see Field Properties.

    Display Property Caching 

    This option can be set to restrict the number of form display properties the server loads into memory at startup. The result of a restricted option (Cache Only Server Display Properties) is less memory use at start-up, and more memory available for the server process to grow. Form display properties are used for the background image of form views and the display properties of each form field. If an unloaded display property is needed, the server loads it on demand instead of caching it up front. Use the radio button to select one of these options: Restart the server after changing this setting.

    • Cache Only Server Display Properties— Only display properties associated with server workflow are cached. This setting does not decrease start-up time because the server still must read all properties for load selection. Reduced memory use impacts performance when data must be read from the database. It might also adversely affect server performance, database performance, or both when used with mid tier caching.

      Note: This option is not useful in a 64-bit environment. Most 64-bit environments do not impose memory limitations and setting the option could unnecessarily impact performance.

    • Cache All Display Properties (default) — All display properties are loaded into the cache. This increases the memory requirement for the cache but can improve the performance of the server when a form is first opened by the client.

      Note: To configure settings for individual forms, use the check boxes on the Basic page of the Form Properties dialog box. See Setting form properties.

    License TrackingDetermines whether information is recorded in the AR System Current License Usage and AR System Historical License Usage forms. By default, this option is not selected (information is not recorded in the forms). For information about tracking license usage, see Recording and tracking license usage.
    Disable ARSignalsCauses the system to disable ARSignals. By default, this check box is not selected.
    Disable Audit Only Changed FieldsCauses the system to record all fields when auditing a record. By default, this check box is not selected, indicating that only those fields whose values have changed during a transaction are audited.

Was this page helpful? Yes No Submitting... Thank you


  1. Leonard Warren

    Do we know what the API Number is for AR System 9.0 and 9.1?  I would imagine it is 21 and 22 respectively.

    Aug 08, 2016 01:34
    1. Prachi Kalyani

      Hello Leonard,

      I will verify this and get back to you soon.



      Aug 10, 2016 08:53
    1. Prachi Kalyani

      I have updated the topic with the information.



      Aug 17, 2016 02:06
      1. Leonard Warren


        Aug 17, 2016 06:10
  2. Leonard Warren

    The description provided for Development Cache Mode is confusing and does not provide the explanation of what it truly does.

    Your description has - "The check box is not selected by default." I agree. Then there is the note - "Note: You should not change the default value."  What value?  Checked or unchecked?  If I am not to change it, then why is it here?

    You have a definition under the Configuring a Server's Cache Mode Settings as follow WHEN IT IS CHECKED, "In this mode, administrative operations do not cause a copy of the cache to be made; instead, they lock other users out of the shared cache and wait for users accessing that cache to complete their operations before performing changes. Escalation and Archive threads must also complete their operations before Admin thread changes can be completed. Therefore, potentially long running tasks -such as escalations, BMC Atrium Integration Engine jobs, and queries - are incompatible with Admin thread changes in this mode and can lead to long delays."

    At least define what it is when it is checked or unchecked or provide a link to the page that expands on both options.

    Aug 08, 2016 01:42
    1. Prachi Kalyani

      Hello Leonard,

      If the check box is not selected (the default), the server is in production cache mode. In this mode, administrative operations cause the server to create an administrative copy of its cache so that other users can continue using the shared cache while administrative operations are performed.

      Ensure that you always use the default value (Production cache mode) to perform your server operations. The users should not switch to Development Cache Mode.

      I have updated the topic with this information.




      Aug 17, 2016 01:38
      1. Leonard Warren



        Thanks - Keep in mind that BMC recommends Development Cache Mode for Development and Test Environments but Production Cache Mode for Production Environments.



        Aug 17, 2016 06:09
  3. Leonard Warren

    Missing an entry in the table for Archive Interval (hours). Does this setting get changed by the AR System Archive Manager setting when applied (tried to post an image but it asked me to get permissions to do so but does not say to get permissions from whom nor how.

    Aug 08, 2016 01:46
  4. Leonard Warren

    For the field identifier definition, suggest adding in a statement as to why the Asterisk is being used.  My understanding is that this covers the 508 Compliance (Compliance standards are set by Section 508 of the Rehabilitation Act of 1973 that requires federal agencies to provide software and website accessibility to people with disabilities.) requirements levied on software companies.  What happens if I remove or change this designator would mean that I am out of compliance on my custom forms and custom fields.

    Aug 08, 2016 01:53
    1. Prachi Kalyani

      Hello Leonard,

      The Required Field Identifier is used to specify which character will be used to denote that any field on the form is mandatory.

      For example, on a form Name field as should be marked as a mandatory field and to denote this we mark this field with * or #. In Required Field Identifier we enter the value *, which displays the Name field as below suggesting that the field is mandatory:


      Hope this helps!



      Aug 10, 2016 02:55
      1. Leonard Warren


        Thanks for the response but it does not help.

        Since at least 1998 (when I started with Remedy Corporation), it has always been defined that bold labels indicates the field is mandatory (or required) and non-bold labels indicate optional fields.

         Then the incorporation of the asterisks ( * ) came along and was used to define the 508 Compliance requirements and were added to the primary OOTB application forms on the majority of the required fields.  Documentation indicated that this represented the field being required, when in actuality it did not - the boldness did - as the majority of the forms in the AR System Server did not have the asterisks next to the bold label.  In addition, in order for 508 Compliance to work, the asterisk had to be placed in front of any other symbol - as in *+ so the coding to read the field to the translation software would work for those who are legally blind.

        Now we have this Required Field Identifier being added to through in a mix of confusion.  I am assuming the purpose of the field was to automatically add in the asterisk to any custom required field to make it display to the end user and to make it available to the 508 software. 

        My concern is if I change this field from asterisk to a pound symbol, then I have just broken the 508 Compliance requirement for my custom fields, thus not allowing those with difficulty in seeing be able to know that my custom field or fields on an OOTB BMC application form is not being populated when they try to fill out the form.  This will cause errors for those individuals.

        Also, there is nothing stopping me from putting an asterisk on an optional field; however, based on the given definition, I am indicating that it is a mandatory field when there may not be any workflow to enforce the mandatory requirement.

        So my question is about the definition of this field.  It appears that it should be left as an asterisk to support 508 compliance requirements and not to indicate that this field is bold. Is this the case? 

        Aug 10, 2016 06:32
        1. Prachi Kalyani

          I will get a confirmation on this from our technical team and update you.



          Aug 10, 2016 08:54
          1. Leonard Warren


            Aug 10, 2016 09:06
  5. Colin Rolls

    the Users Prompted For Login section needs more details, ie:

    By Preference  - where is this preference? explain AR System User Preference and how/who can set.

    Once Only - define what is meant by 'session' (closing browser window. timeout etc)

    Nov 28, 2016 09:31
    1. Leonard Warren

      This was for the BMC Remedy User Client tool to require the End User to always log in or log in once.

      The preference setting allowed for the End User to log into BMC Remedy User Client from any machine as their settings were stored in the AR System User Preference Form.  Today, every one that has a record in the User form gets a matching AR System User Preference record. 

      Thus, you do not have to worry or deal with By Preference or Once Only as this is no longer necessary.  The AR System User Preference form is required for each user to access BMC Remedy using a browser so it can control how they interact with the AR System based on those settings.


      Hope this helps? Lenny

      Nov 28, 2016 11:09
  6. Leonard Warren

    It is odd how I get a notification of text being removed from an August 2016 posting of Re: Setting Administrative Options - (The text of this comment has been removed because it can be viewed only by BMC employees).

    This happens too often that it gets discouraging to even bother posting anything in the documents and just post it in the Communities.  I guess that is what I can do going forward as it is an endless battle to try and help or get the right answers in the documents of late.

    Jan 24, 2017 02:16
  7. Milan Franzkowski

    Max Entries Returned by GetList

    ...A value of 0 (default) specifies no limit....


    This is not correct anymore. As of ARS 9 the default is 2000.

    Btw. why is 2000 the max as this one states - ?

    Unfortunately there is no explanation why values higher than 2000 are "bad".

    We got a problem in an SRD because of that, a menu is supposed to return more than 2000 entries but is restricted by this. Setting the ar.conf option for search menus (Max-Entries-Per-Search-Menu) doesn't work in SRM...

    Apr 12, 2017 09:27
    1. Nidhi Das

      Hello Milan,

      Thank you for pointing out this issue. I will discuss this with the concerned SME and will write back to you.


      Apr 13, 2017 01:03
    1. Leonard Warren

      Hello Milan

      The limitation could be one of several reasons.

      The Mid-Tier Web Reporting Console defaults to 2000 records.

      An unlicensed AR System Server or an Expired licensed AR System Server is limited to 2000 records.

      Other than those two options not sure.

      You can change the setting from 2000 to something higher. My current client has their production set to 55000. Most others set it to 10000. Or you can set it to 0 and update all the AR System User Preference entries with a limitation of 2000 to limit the users.

      Jan 09, 2018 05:13
  8. Andreas Mitterdorfer

    Please can you document the design change for 9.1.04, see Also please document or crossreference to the documentation, how to set Disable Escalations, Disable Admin Operations, etc. in a server group.

    Jan 11, 2018 03:14
    1. Leonard Warren

      Andreas - The ranking process is located in a different place in the documentation scheme of things. Ranking of the servers is only useful if you have Server Group environment. Here, you do nothing with disabling the Escalations, Admin Operations etc if they are not to be used as the rankings will override the setting anyway. So do a search on Server Ranking or try this link to review how to set up the ranking process-

      Jan 11, 2018 06:34
      1. Anagha Deshpande

        Thanks, Leonard.

        Jan 14, 2018 09:18