This topic provides information that supplements the Remedy AR System documentation. It contains the following sections:
Frequently asked questions
This section provides answers to frequently asked questions (FAQs) about Remedy AR System.
Remedy Mid Tier
This section provides answers to frequently asked questions about Remedy Mid Tier.
You can use the JSP servlets to make the mid tier scalable. For more information, see Remedy Mid Tier scalability.
For mid tier caching recommendations, see About Mid Tier caching.
Remedy AR System licenses
This section provides answers to frequently asked questions about Remedy AR System licenses.
With the new bundled license option, you can configure license limits, assign licenses to users, and control and report license consumption in alignment with how user licenses were purchased. You do not need to manually map the new pricing models to the old pricing models and then apply the licenses in the system.
The License usage report gets updated in every 45 minutes. The Admin Manage User licenses screen displays two new options, bundled - current users and bundled - registered users, to display the consumption of bundled licenses along with the existing granular license consumption options.
Internet Explorer Compatibility View warning
This section provides answers to frequently asked questions about the following compatibility view warning
IE is running in Compatibility View. Please remove Mid-tier URL from either IE Compatibility View Settings or Registry location (AR WARN:9429)
This message indicates to the end user that the Internet Explorer has Compatibility View enabled through one of the following mechanisms:
- Enabled by the end user in the Internet Explorer using the Tools > Compatibility View Settings
- Enabled by the System Administrator, usually using a registry entry like HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\BrowserEmulation\PolicyList
- Enabled by the System Administrator, using the Microsoft Windows Group Policy Editor.
(This Warning might also appear as: Internet Explorer is using Compatibility View which may cause degraded user experience. Try removing Midtier URLs from the browser's Compatibility View Settings, or contact your administrator (ARWARN 9429) )
The Admin will have to find out the mechanism with which Compatibility View has been enabled and respond appropriately. This is not an error but a warning, so end-users can continue using the product while the Admin finds the best way to disable Compatibility View for mid tier. This is not a critical problem.
Compatibility View forces Internet Explorer to emulate an older, unsupported version of the browser (IE7), so that sites designed for the older version render correctly. However, such a browser configuration is not necessary for web-applications like Remedy Mid Tier.
The degraded experience might not always be evident, but sometimes may show up as:
- Script errors
- UI distortion
- Client-side performance issues
Yes. The admins can choose to add arsystem.display_IE_compatibility_view_alert=false to <MidtierInstallDirectory>/WEB-INF/classes/config.properties to turn off the alerts temporarily. However the longer this alert is suppressed, the higher the risk of client-side problems for the end-users. It might be necessary to apply the latest cumulative hotfix for mid tier before this property is usable.
Microsoft recommends that admins identify the applications that require Compatibility View, and add the individual URLs http://windows.microsoft.com/en-IN/internet-explorer/products/ie-9/features/compatibility-view
To achieve this, the Group Policy Editor is also expected to be usable http://msdn.microsoft.com/en-us/library/dn321457.aspx
The end users could run into client-related problems that require assistance from BMC Customer Support. BMC Customer Support may request Admins to disable Compatibility View for affected users. Rather than having to find solutions at this point, the admins are advised to proactively disable Compatibility View when end-users see the Warning.
This issue is specifically noticed with Internet Explorer 11 browser. The rest of the browsers works fine.
Support for Google Chrome version 80
Remedy Single Sign-On relies on cookies to enable your users to seamlessly access all integrated applications. As browsers implement changes to their default SameSite attributes, cross-site cookies will not be sent by default. As a result, your users will be prevented from accessing your applications.
To continue to use Remedy Single Sign-On with newer browser versions, you must do the following:
- Use the secure HTTP (https) protocol for all of your applications.
- Upgrade to Remedy Single Sign-On 20.02.
- Set the following configuration options in Remedy Single Sign-On:
Enable Secure Cookie
Use Cross Site Cookie
For instructions, see .
Note: If you subscribe to BMC Helix (SaaS), no action is required. BMC will update your configuration.
In Remedy Developer Studio, when the Show URL property is enabled for a character field, a thick black border is displayed around some elements.
If you do not want to see the border, disable the Web Platform Controls updated UI setting in Google Chrome. For information about disabling the Web Platform Controls updated UI setting, see .
For information about PDF, see PDFs and videos.