Action Request System 21.02
- Action Request System 21.05
- Action Request System 21.02
Action Request System (formerly known as Remedy Action Request System) is a part of the single-tenant BMC Helix Innovation Suite that consolidates the capabilities of AR System and .
BMC Helix Innovation Suite helps you to develop, build, deploy, and use applications on cloud (SaaS) and on-premises environments. It also helps you to create and automate many business processes without learning a programming language or complex development tools.
BMC Helix Innovation Suite requires fewer resources and improves integration between components.
Learn what’s new or changed for Action Request System 21.02, including new features, urgent issues, documentation updates, and fixes or patches. Also know about license entitlement information for the release.
To stay informed of changes to this space, place a watch on this page.
The following table lists the enhancements in this release:
|May 4, 2021||21.02.01: Patch 1|
This update includes updates and fixes BMC Helix Innovation Suite.
Additionally, BMC Helix Innovation Suite includes the following enhancement:
|March 17, 2021||21.02 enhancements|
Enhancements available in this release:
As an end user, navigate the AR System interface, create and manage reports, work with approval requests, and view data using Remedy Flashboards.
As an administrator, set up AR System for your company.
As a developer or application programmer, develop or customize a AR System application, navigate the Remedy Developer Studio interface, and move the application to production and distribute the application.
As an administrator, secure the AR System by configuring ports and firewalls, encrypting the system, and setting up passwords.
As a developer or application programmer, integrate the AR System forms with any third-party application by using REST API.
As an administrator or security administrator, set up user accounts and manage and maintain the system after it is installed and configured.
As an administrator, set up integrations with other BMC products or third-party software.
Resolve common issues or errors, review logs, or contact Support.
When you export a custom PDF, you can select the topics to include. For information about how you can export a custom PDF from this space, see Exporting to PDF and other formats.
Ready-made PDFs of this space
The following topics contain videos that supplement or replace the text-based documentation. Some videos reflect an earlier version of the product.
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 Best practices for configuring mid tier cache.
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
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 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. (See .)
To achieve this, the Group Policy Editor is also expected to be usable. (See .)
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.
For information about PDFs, see PDFs and videos.