9.1.00,

9.0.00,

8.1.02

9.1.00,

9.0.00,

8.1.00,

8.0.00

The following are the Rich Text Formatting (RTF) fields open issues for the release:

• SW00417023: The spell check feature does not work correctly on double byte characters.
  For example, if you add some Chinese words in RTF field, the correct words are also highlighted.
  Note: If you provide space in between the words, the spell check works.
  But, the sentence in Chinese must not contain space between words.
• SW00417266: The spell check feature does not work correctly on Russian locale.
  If you add some Russian words in RTF field, the correct words are highlighted and also
  does not display words in the suggestion list with the correct spelling.
• SW00424712: If you open RTF editor on Internet Explorer 8 and press Enter while typing
  text in the table or the Expand section, the cursor does not appear or move to the next line.
• SW00425010/SW00423983: If you click the strikethrough or underline options to
  apply text formatting in the Expand section and again click the options to remove formatting,
  the options does not work correctly on Firefox or Safari.
  • On Firefox, to remove the formatting you must highlight the text again and
    include empty line on top and bottom of the text.
  • On Safari, the strikethrough option applies underline formatting and the underline option
    applies strikethrough formatting to the text.
• SW00425333: On Firefox, after you delete an Expand section by selecting the small delete icon
  on the border of expand section, if you add a new Expand section, the section is not added.
• None: Double click on the suggestion list in Spell Checker causes unexpected results.
  You must always perform single click to select a word from the suggestion list.

9.1.00,

9.0.00,

8.1.00,

8.0.00

The following are the Rich Text Formatting (RTF) fields open issues for the release:

• SW00414089: When you select the text in the RTF editor and press the Delete key,
  an empty box appears in the editor.
• SW00411835: After adding an Expand section and typing some text in the RTF editor,
  if you expand and close the section on Internet Explorer 9, the text appears twice for some time
  and then the field refreshes. Also, if you expand the section again, the text might not display for some time.
• SW00410112: When you open a form with an RTF field in Internet Explorer 8 and create a table,
  if you then use the mouse to select the table, the table is not highlighted to identify the selection.
  On Firefox, the table border changes to light blue to indicate the selection.
• SW00414748: After you click the Spell Checker option on the RTF editor,
  if you move the RTF editor to the browser borders, the Spell Checker window moves or appears outside the browser.
• SW00414538: When you enable the Show/Hide Hidden Elements option in an RTF field in Safari 5.0.5
  and close the RTF editor, the option is not enabled when you re-open the editor.
• SW00414535: The Spell Checker option is enabled even when there is no text in the RTF editor.
• SW00402639: Even though the font size is 14, on Internet Explorer 8 the text appears with
  font size 10 in the Expand section Header and the text area.
• SW00412246: The Line spaces appear small in the RTF fields and the line space between the lines
  differs in the RTF field and RTF editor. Also, the spaces between the text and line display differently
  in edit mode and display mode.
• SW00415767: The spell checker removes some special characters on Internet Explorer 8.
• SW00411837: You cannot cut, copy, and paste the RTF field Expand section easily on Internet Explorer 9.
• SW00411557: You must copy the RTF field Expand section precisely on Firefox to
  copy and paste the section, otherwise the section is not pasted correctly.
• SW00416496: In Firefox browsers, the spell checker does always not highlight all instances of misspelled words.
  Also, when you click the Spell Checker option for the second time, sometimes the Spell Checker window
  does not display a message about no misspelled words found.
  (These issues only occur when you copy and paste from an outside editor such as Word.)
• SW00414056: Sometimes the cursor is automatically set to the second line when you open an
  RTF editor or set focus to an RTF field.
• SW00418290: The spell checker deletes the leading white space above the
  Expand section in Internet Explorer.
• SW00419728: When you copy the text from an RTF field and pasted in an another RTF field,
  the font size appears different. Also, the font size differs in the Display mode and Edit mode.
  The font size is smaller in the Display mode.

9.1.00,

9.0.00,

8.1.00,

8.0.00

9.1.00,

9.0.00,

8.1.00,

8.0.00,

7.6.04,

7.6.03

9.1.00,

9.0.00,

8.1.00,

8.0.00,

7.6.04

9.1.00,

9.0.00,

8.1.00,

8.0.00,

7.6.04,

7.6.03

9.1.00,

9.0.00,

8.1.00,

8.0.00,

7.6.04,

7.6.03

BMC Remedy AR System 9.1.00 does not support reports that have"&" in the report name. This is a knows issue and presently there are no plans to fix the same.

The following error is displayed when you process reports that have"&" in the report name. AR ERROR [9246] Cannot find report reportName of type reportType for form formName on server serverName. Please see your administrator.

9.1.00,

9.0.00,

8.1.00

9.1.00,

9.0.00,

8.1.00,

8.0.00,

7.6.04,

7.6.03

During migration or comparison, the migrator searches for AP:Tooltip_Information_Archive form on the source server and destination server using the AR_Archive_Forms.xml file. As the BMC Remedy AR System server stores the form with name AP:ToolTip_Information_Archive, the migrator returns the following error:

Form does not exist on server. 

Workaround:

• Open the AR_Archive_Forms.xml file located at <MigratorInstallationPath>\DeltaDataMigration\Packages\ARCore\<VERSION>.
• Edit the source form name and destination form name from AP:Tooltip_Information_Archive to AP:ToolTip_Information_Archive.

9.1.00,

9.0.01,

9.0.00

The BMC Remedy Migrator Command Line Interface (CLI) takes a long time to generate
the .migrator file on the BMC Remedy IT Service Management (ITSM) stack.
The size of the .migrator file cannot exceed 2 GB.

Workaround: Instead of creating the .migrator file for the whole stack,
create it in chunks based on object types.

9.1.00,

9.0.00,

8.1.00,

7.6.04,

7.5.00

9.1.00,

9.0.00,

8.1.00,

8.0.01

The following error is displayed and the BMC Remedy Migrator fails when you use AR System server 9.x or earlier:

2004 error with Serverlower to 9.x.

9.1.00,

9.0.00

9.1.00,

9.0.00,

8.1.01

The following issues were identified with the Remedy Knowledge Management Application (RKM)
and BMC Remedy Service Request Management forms when using JAWS:

• When you open a knowledge entry from the Request Entry form, the dialog box that
  appears is different and does not read the knowledge entry data correctly.
• On Service Request forms, all the answer fields are identified as edit fields regardless of their type.
• When you cancel a Service Request form, the confirmation dialog box shows unwanted string
  of text before displaying the message Are you sure.

9.1.00,

9.0.00,

8.1.00

The following error is displayed in Microsoft Internet Explorer 9 or 10 when the
value of arsystem.emit_X_UA_compatible_mode variable is set to 10 in the Mid-tier configuration file:

ARERR [9506] Unable to display form 

Workaround:

9.1.00,

9.0.00,

8.1.01

9.1.00,

9.0.00,

8.1.00,

8.0.00

9.1.00,

9.0.00,

8.1.00,

8.0.00, 

7.6.04, 

7.6.03

9.1.00,

9.0.00, 

8.1.00,

8.0.00,

7.6.04 

When you open the customizable home page in an inline view field,
the images to expand or collapse the panels, and to add or remove panels do not display correctly.

Workaround:

1. Open the AR System Customizable Home Page in BMC Remedy Developer Studio.
2. Select the Default Administrator View tab and open the Properties window.
3. Go to the Web Header Content property and click the ellipses button.
   You see the CSS style rules that reference the class img.btnimg enclosed in the <STYLE> tag.
4. Open the form with a view field on which you have embedded the home page.
   For example, Form X.
5. Verify the <STYLE> tag in the Web Header Content property for Form X.
   The CSS rules pertaining to the image buttons must be the same as in AR System Customizable Home Page.
6. If the style is different, and you are in Best Practice Customization Mode,
   create an overlay of the form (Form X). For more information about how to create an overlay, see Developing an application.
7. Copy the style from the home page form and paste it into the Web Header Content property
   on the form (or the form overlay, as appropriate).
8. If you have other views, or outer parent forms, repeat step 4 through step 7.
   For example,assume that you have Form Y with a view field. You embed AR System Customizable Home Page
   on Form Y's view field. The Form Y style for image buttons must match with the home page style.

9.1.00,

9.0.00,

8.1.00, 

8.0.00,

7.6.04

9.1.00,

9.0.00,

8.1.00,

8.0.00

9.1.00,

9.0.00,

8.1.00,

8.0.01

9.1.00,

9.0.00,

8.1.00, 

8.0.01

The Sync Cache operation does not rebuild the image if you make any changes to the image.
Also deleting the image during Sync Cache operation, results in a heavy performance hit in mid tier.

Workaround:

Change the image name, update the form where the image is saved and
then perform the Sync Cache operation to reflect the changes on mid tier.

9.1.00,

9.0.00

When you create a new incident by using the Incident Management Console,
if you select a value from a drop-down list or enter multiple characters in a character field,
the new screen rendition is delayed. This delay happens when the chat status in Incident Management Console is Online.
If you change the chat status to Offline, there is no delay in screen rendition.

This issue is observed in Mozilla Firefox 23, Internet Explorer 8 or other browsers.

9.1.00,

9.0.00, 8.1.00

9.1.00,

9.0.01

Security vulnerabilities are detected in HTTP header's value after a fresh install or upgrade of BMC RemedyMid Tier.

For details, refer to Settings in the config.properties file. 

The length validation for a Character field is different in the following two scenarios:

1. When you Right Click and select the Paste option to paste data in Character field.
2. When you press CTRL + V to paste data in the Character field.

When a No Vision user uses JAWS for navigating to a Flashboard using a mouse, the user gets repeated readout of data due to the tooltip.

This is the expected behavior. No Vision usage requires traversing the Flashboard using the tab key and not the mouse.

9.1.00.001

9.1.00

9.1.00.001

9.1.00

The following error is displayed when the Atrium SSO session timeouts, the Mid Tier redirects to logout.jsp:

Atrium SSO session is invalid/timeout.

An incorrect date is displayed after you change the user's time zone on the User Preference form. The date is displayed as follows:

When you enable Preload for all the AR System servers and disable the Cache Persistence, the config_cache.jsp page throws the following error intermittently:

IllegalStateException.

The following error occurs on Mid Tier when you use the FTP protocol for passing Username and Password and run the PERFORM-ACTION-OPEN-URL action:

Cannot decode URL. The URL supplied is invalid. Please see your administrator.  

A report is not created and an exception occurs when you create a Web Report on HPD:Help Desk with the qualification as follows:

 Field = Uxxx or Field = uxxx.

The AR System Server does not import the value for Create Date field in the following scenarios:

• When you specify data for the Create Date field in the .arx file.
• When you select Replace Old Record With New Record option.

The AR System Server assigns current server timestamp as a value to Create Date field.

9.1.00.01

An imported record reflects the current system date and time instead of the actual date and time of the record under all of the following conditions:
You export an existing record to an .arx file.

• The existing record is from any regular form that has a Create Date field.
• You re-import that record into the same form by using the Data Import Tool.
• You select Handle Duplicates By Replace Old Record with New Record option.

9.1

9.1.00.01

If you manually deploy version 9.1 flashboards on the same computer and in the same path
and folder where you have an earlier version of the flashboards binaries already deployed to
support remote flashboards, the BMC Remedy Flashboards 9.1 installation fails.

Workaround:
Perform either one of the following actions:

• Stop the earlier flashboards service before installing BMC Remedy Flashboards version 9.1.
• Install BMC Remedy Flashboards version 9.1 in a different location.

9.1.00,

9.0.00,

8.1.00,

8.0.01

9.1.00,

9.0.00

9.1.00,

9.0.01,

9.0.00

Because the BMC Remedy Email Engine has an open issue for supporting
LDAP user authentication, the approval notification through the email

feature is currently not available for users residing on LDAP directories.

9.1.00,

9.0.00, 

8.1.00, 

8.0.00,

7.6.03

When you open the Developer Studio in Base mode, a banner is displayed in yellow color. If you try to resize this banner, the resizing fails.

Workaround:

• To hide the banner, click Hide.
• To restore the banner to its normal size, reset the perspective or navigate to Window > Show view > Other... > BMC Developer Studio and select Mode Info.  

When you create an association between the main form and its audit form and you have chosen this
to follow this association during archiving, all the related audit entries are also archived with that form.
However, after archiving, when you delete the archived records from the main form,
an audit entry gets added for deletion in the audit form and it is not archived.

Workaround:

you can choose to archive those entries in your audit form which were created due to deletion
on the form by archive user.

1. Define an archive on your audit form.
2. Select Appear in Archive Policy check box.
3. Add the qualification as 'User'='AR_ARCHIVER' & 'Action'='Delete'.
4. Save the form.

9.1.00,

9.0.00

9.1.00,

9.0.00,

8.1.00,

8.0.00

When you try to add approximately 350 forms across BMC Remedy IT Service Management, BMC Service Request Management, and BMC Service Level Management. The following error is displayed:

Save failed for form AST:ComputerSystem
[Exception: ERROR (392): Field/VUI name must be unique for the form -- there is already a field or VUI using this name; AST:ComputerSystem : <399990514> : Management_he]

The L10n Toolkit does not update the labels on Hebrew views if you run archgid.

The following exception occurs when you try to export a document from BMC Remedy Developer Studio:

java.lang.NullPointerException.

9.0.01

9.1

9.1.00.01

9.1

9.1.00.01

9.1

9.1.00.01

9.1

9.1.00.01

When you initialize Remedy for Smart Reporting from the Flyout menu, the following error occurs:

Server is busy serving maximum number of reporting requests, please try after some time.

9.0

9.1

9.1.00.01

9.1

9.1.00.01

9.0

9.1

9.1.00.01

8.1.02

9.0

9.1

9.1.00.01

8.1.01

9.0

9.1

9.1.00.01

9.1

9.1.00.01

9.1

9.1.00.01

9.0

9.1

9.1.00.01

When you launch the Smart Reporting console through the Application Console and you click on the Dashboards tab, the following error occurs:

The Connection was reset.

9.0.01

9.1

9.1.00.01

When you design the out-of-the-box Incident Number Hyperlink field or any Hyperlink fields with http URL, the following error occurs:
The Connection was reset..

9.1

9.1.00.01

When token information is present in the URL, a security vulnerability occurs. This token information can be misused by any attacker.

When you use the predefined function CurrentDate() in a report, the report does not work and the following error occurs:
Ambiguous column name 'CurrentDate.

9.1

9.1.00.01

Smart reporting cross launch(Hyperlink) is not working in 9.1, an error occurs and you are re-directed to the following link:
https://smartrept91-mar.onbmc.com/onboarding/router.jsp?midtierUrl=http://lausd-dev.onbmc.com/arsys/forms/onbmc-s/SHR%3ALandingConsole/Default+Administrator+View/?mode=search%26F304255500=HPD:Help%20Desk%26F1000000076=FormOpenNoAppList%26F303647600=SearchTicketWithQual%26F304255610=%271000000161%27=%22INC000000000653%22&smartitUrl=http:///ux/smart-it/#/search/INC000000000653/

9.0

9.1

9.1.00.01

If a user is logged into an application that is integrated with BMC Remedy SSO, the user can continue to work with the application even if the BMC Remedy SSO session expires.

The user is prompted for re-authentication only when the user's application session also expires.

SW00500279

In the BMC Remedy Single Sign-On Admin console, the user can create unlimited number of realms with the same Realm ID.

Workaround

Delete the duplicate realms one by one from the user interface and re-create them using different realm IDs.

While manually configuring BMC Remedy Single Sign-On, when the user uses a "plain text password" as the DB password, the user is not able to log on.

Workaround

The user must use the rsso-ds.jar utility to generate an AES-encrypted password.

Usage: java -jar [encryption-algorithm] [initial-key]

Example:

Usage: java -jar rsso-ds.jar my_db_password aes my_key_to_encode

The user must then update the password in the database.properties file.

The memory size consumed by BMC Remedy Single Sign-On Tomcat process keeps growing and eventually triggers the Linux OOM killer to kill the process.

Workaround

Close the browser and log on again in a new window.

9.1.00,

9.0.01

If ADFS use self-signed signing certificate and "AutoCertificateRollover" option is enabled, new sign certificate will be generated 20 days prior to expiration of old certificate and ADFS starts to sign responses with new certificate.

This will result in user's log in failure. Response signature isn't verified" error and SAML authentication failure.

Possible fix could have been to re-import Idp metadata but the problem is that Idp metadata contains both new and old certificate and RSSO server extracts old certificate instead of new one.

Workaround

Manually update the signing certificate to a new signing certificate in BMC Remedy SSO. 

• The User ID field in the certificate-based authentication does not behave as expected. If a user selects Custom Attribute in the User ID field while configuring certificate-based authentication, the User ID Attribute field does not become visible.

Workaround:

The user must save the configuration and edit the realm to enter a value in the User ID Attribute field.

• The User ID Attribute field remains available even if the user selects any value other than Custom Attribute in the User ID field.

Workaround:

The user must enter some value in the User ID Attribute field, but BMC Remedy SSO ignores this value and considers the one entered in the User ID field.

9.1

9.1.00.01

9.0.01

9.1

9.1.00.01

When you try to load the following forms on the Landing console, the forms are not displayed as expected because the groups are populated erroneously in the udd.js file:

• HPD:HomePageContent:RL_IncidentConsole
• CHG:HomePageContent:RL_ChangeConsole
• HPD:HomePageContent:RL_IncidentWatchList
• PBM:HomePageContent:RL_ProblemConsole

9.0.01

9.1

9.1.00.01

When you log in to the mid tier and create a deployable application, the application is displayed in the Mid Tier Object List.

8.1.02

9.0

9.1

9.1.00.01

8.01.01

8.01.02

9.0

9.1

9.1.00.01

9.0

9.1

9.1.00.01

9.1

9.1.00.01

8.1.02

9.0

9.1

SW00506700

When BMC Remedy Single-Sign On (RSSO) is installed and configured for BMC Remedy AR System, clicking the Approve, Reject, or Hold options in Approval Central two dialog boxes are displayed: the credential sign in window and the double authentication dialog box.

The following issues have been observed

• The Reopen button on the authentication dialog box multiple times will open multiple sign in dialog boxes.  
  Workaround : Click Reopen on the authentication dialog box only if no sign-in dialog box is already open.
• When using Microsoft Internet Explorer version 11, the authentication window is displayed on top of the sign-in dialog box. 
  Workaroud: Click on the sign-in window to enter your credentials and proceed with the approval process.

• When BMC Remedy Single-Sign On is enabled for BMC Asset Management, approvals initiated by clicking the Approve, Reject, Hold or Adhoc options on the Approval Details form invoked by clicking the Approvals link on the Purchasing Console are not processed. The BMC RSSO authentication dialog box remains open even after entering valid credentials.
  Workaround: Open the Approval Details form from Approval Central (Applications > Quick Links > Approval Central) instead of the Purchase Request form.

9.1.00

9.1.00.001

When you try to create a new record on FB:User Privilege form and click on the New Request button, the following error occurs:

Required field cannot be blank FB:User Privilige Group_Parent (ARERR 307).

9.0

9.1

9.1.00.01

9.1

9.1.00.01

8.1.02

9.0

9.1

9.1.00.01

When you select the schemas.xsd file in the XML Schema section and click the Reload button, BMC Remedy Developer Studio does not load the selected schema type and the following error is displayed:

Unable to process the WSDL Mapping XML Document., 5147, Untitled Web Service.

8.1

9.0

9.1

9.1.00.01

When you create a character field on a form and set an attribute property to $LOWER$, the value does not fall within the limits specified for the field and the following error occurs:

(Field ID - , Pattern - $LOWER$) (ARERR 306).d

9.1

9.1.00.01

When you create custom menus in the Base Stack, the custom menus are shown as deleted in the Objects changed in Base.

9.1

9.1.00.01

9.1

9.1.00.01

When you modify the thread count from the Server Settings in the Assignment Engine Administration Console,
and run any process that invokes the AE_CACHE DoCache command,
the Assignment Engine Cache thread process never finishes. For example,
if you modify the thread count and run the Assignment Engine sanity check, the check fails.

Workaround:
When you change the thread counts in Assignment Engine, shut down and restart the AR System Server.
This process terminates the Assignment Engine server and the armonitor restarts the Assignment Engine server.

9.1.00,

9.0.00,

8.1.01

In Approval Server, if approval engine fails to release the lock when uncaught exception occurs during custom approval process, the Approval Server stops responding and cannot clear the pending application.

9.1.00.001

9.1.00