This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

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

Other enhancements in version 8.0.00

This topic provides information about the following other enhancements and new features in the BMC Remedy AR System 8.0.00 release:

Enabling social collaboration in BMC Remedy AR System

The following social collaboration features enable you to use Twitter and RSS feed clients to receive alerts and feeds, and also provide the option to resolve issues using chat:

  • Alerts through Twitter — As an administrator, you can configure a Twitter account to receive any specific alerts as tweets. For more information about receiving alerts through Twitter and mapping a user to a Twitter account, see Receiving alerts through twitter.
  • RSS feeds — As an administrator, you can define or publish RSS feeds that end users can consume from RSS feed clients. For more information about configuring RSS feeds and subscribing to RSS feeds, see Configuring RSS feeds.
  • Chat option — If you require information about an incident when you are resolving it, you can discuss the issue with one or many people by using the chat option. You can save the chat conversation and continue to work on the issue. For more information about the chat option and the required process, see Configuring chat.

Enabling multiple browser sessions in a distributed mid tier environment

You can now configure a mid tier to launch a browser on another mid tier in a Hub and Spoke implementation or independently, allowing you to link a central mid tier to one or more remote mid tiers to display forms residing on remote AR System server(s). This feature allows users to work on records in a distributed mid tier environment.

For more information, see Multiple browser sessions in a distributed mid tier environment.

Java implementation of BMC Remedy Approval Server, BMC Remedy Assignment Engine, and DSO

The BMC Remedy Approval Server, BMC Remedy Distributed Server Option (DSO), and BMC Remedy Assignment Engine components are now implemented using Java. The Java implementation provides the following benefits:

  • Enhanced performance: BMC Remedy Approval Server and BMC Remedy Assignment Engine now work in a multithreaded environment.
  • Improved troubleshooting and maintenance: All the components now use the Apache log4j tool for logging. Apache log4j supports three logging levels.

Configuration changes for BMC Remedy Assignment Engine and BMC Remedy Approval Server

The following properties have been added in the ar.cfg file (see ar.cfg or ar.conf):

  • BMC Remedy Assignment Engine
    • AE-Worker-Threads — The total number of worker threads that process various assignment requests
    • AE-Poll-Interval — The time interval (in minutes) after which the BMC Remedy Assignment Engine checks for any pending entries for assignment
  • BMC Remedy Approval Server
    • ASJ-Thread-Count — The total number of worker threads that process various approval requests

The following properties have been removed from the ar.cfg file:

  • BMC Remedy Assignment Engine
    • AE-Log-File
    • AE-Log_File_Size
    • AE-Log
    • AE-Trace-File
    • AE-Trace_File_Size
    • AE-Log
  • BMC Remedy Approval Server
    • arapprove.dll

Enhanced import join functionality

In earlier releases, when you performed an import while overwriting an existing join form, you could modify the join only by switching the primary and secondary forms and then changing the join criteria (join qualifier).

You can now modify the join when you import by replacing the form with a new form and changing the field mapping. To accomplish this in earlier releases, you had to delete the join form, which deleted all child forms.

For more information, see Importing a join form using the Replace Objects on the Destination Server option.

Atrium Integrator adapter for BMC Remedy AR System

The Atrium Integrator adapter provides a single method of importing and exporting data to and from BMC Remedy AR System and the BMC Remedy ITSM Suite. It supports the ability to import and export data from multiple types of data sources, including text files, Microsoft Excel files, data in relational databases, data in other AR System server systems, and AR data export files (.arx files).

For more information, see Atrium Integrator adapter for BMC Remedy AR System.

Enhancements to the BMC Remedy AR System templates

Beginning with BMC Remedy AR System 8.0.00, the HTML snippet template also supports styles and scripts.

For more information, see Introducing templates.

Enabling client-managed transactions

A client can perform multiple API calls within a single transaction to ensure that all operations are committed or rolled back together, and to ensure that later API calls in the transaction can see operations that previous calls in the transaction performed in the database.

For more information, see Enabling client-managed transactions.

Exporting BMC Remedy AR System server form data to ARX format

BMC Remedy AR System server includes the AR Export command-line utility to export the contents of a BMC Remedy AR System server form to an .arx file. The utility also exports data from the Unicode format.

For more information, see Exporting data by using the AR Export command-line utility.

Enhancements to the BMC Remedy AR System C API

A new parameter of type ARPropList is added to the ARGetListImage function that retrieves a list of image names from the specified server. For more information, see ARGetListImage.

For information about the C API changes from the BMC Remedy AR System 7.5 release through the 8.0.00 release, see Migrating to the current release of BMC Remedy AR System C API.

Standards mode compliance for rendering HTML pages

Before this release, BMC Remedy Mid Tier generated HTML pages in quirks mode. BMC Remedy Mid Tier now generates HTML pages in standards mode, which provides better control over form display.

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