bmc remedy itsm 8.2 fixes

BMC Remedy ITSM Suite installer issuesDefect ID Description Affected

versionsFixed in

SW00465047

After an upgrade or a new non-root Installations, some files had permission issues, for example: . /etc/profile, /etc/bmc.profile, /etc/.login, /etc/bmc.cshrc

8.1.008.1.01

8.1.02

Microsoft Internet Explorer versions 10 and 11 issues

Defect ID Application

Issue Affected versions

Correctedin

SW00463094

Calendar The following issues were identified with the Calendar component when using Microsoft Internet Explorer version 11:

The Filters and Queries bar overlaps the records displayed on the Calendar.

Sub-menus for the pre-defined queries listed under Filters and Queries are not displayed.

The tabs on the Details flyout menu are not displayed.

Workaround

In the Mid-tier configuration file, config.properties, change the value of arsystem.emit_X_UA_compatible_mode variable from Edge to 10.

8.1.018.1.01.001

SW00463148

BMC Knowledge Management

Performance issues have been identified when opening the form to create a new Knowledge Article using Microsoft Internet Explorer 11 on a Microsoft Windows 7 system.

8.1.018.1.01.001



Correctedin

Workaround

In the Mid-tier configuration file, config.properties, change the value of arsystem.emit_X_UA_compatible_mode variable from Edge to 10.

SW00465528

All applications

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

ARERR [9506] Unable to display form

WorkaroundChange the browser compatibility settings of the Microsoft Internet Explorer 10 manually. In Internet Explorer, go to Tools -> Compatibility view settings, and deselect the Display intranet sites in compatibility view option.

8.1.018.1.01.001

SW00465529

BMC Knowledge Management

The following issues were identified with the RTF field when using Microsoft Internet Explorer versions 10 or 11:

You cannot modify the field when you select all the content entered in the field.

You cannot navigate the field using the keyboard arrow keys if you add hyperlinked content to the field.

Content alignment does not function as expected.

Workaround

Ensure that content is not selected in the field when you want to modify the

8.1.018.1.01.001



Correctedin

content.

Use the mouse to navigate to a specific location in the field.

Ignore the content alignment settings.

Data Management issuesDefect ID Issue Affected

versionsCorrected in

SW00464943

After loading People records with permission groups, the Assignee Group values on theCTM: People Permission Groups form were populated with the 'Remedy Application Service' value.

8.1.01 8.1.02

SW00465272

The Data Wizard did not update the RQC:SummaryDefinition categorizations.

8.1.008.1.01

8.1.02

SW00464566

The Organization and Deptartment Data that was loaded using Data Management was populated to the wrong company when the Create as new job function was used.

8.1.008.1.01

8.1.02

SW00463606

When importing transactional data for incident management, the customer's Post Code was blank.

8.1.008.1.01

8.1.02

SW00465836

When using Data Management, the ClassId on the AST:Attributes form was not populated when that form used the DMT AST:LoadAttributes form.

8.1.00 8.1.02

SW00466562

When using the Data Wizard console, the CHG:Template Infrastructure Change Manager (id:1000000015) field was not updated by the Support Group Update operation.

8.1.01 8.1.02

SW00464716

You were able to clear the DMT AST:LoadWorkLog validation errors.

8.1.008.1.01

8.1.02

Foundation issues and common issues

Defect ID

Application or Foundation area

Issue Affectedversions

Corrected in

SW00460352

Requester console

You can't create a service request from the Requester console for a user when thereis another user in the system who has the same name.

There is no Workaround available for this known issue.

8.1.01 8.1.02

SW00464330

Notification Engine

NTE:Notifier records are not being deleted, which causes millions of records to accumulate in NTE:Notifier

8.1.00 8.1.02

SW00465272

Requester console

The Data Wizard does not update the RQC:SummaryDefinition categorizations part of the Remedy Requester console.

8.1.00 8.1.02

SW00465540

Overview console

The Overview console does note recognize the role 'All' (Owner or Assigned Group) when selecting 'Show'="Assigned To My Selected Groups".

8.1.00 8.1.02

SW00465760

Rule Based Email

In Rule Based Email, the incident template assignee is not pushed out to the incident ticket when the ticket is created using email.

8.1.00 8.1.02

SW00467216

People The data in the Notification language field was not being saved on the CTM:People form.

8.1.00 8.1.02

SW00468772

Maintenance Tool

Maintenance tool does not launch on Microsoft Windows 2012 server.

Workaround

Set the JAVA_HOME variable and launch the Maintenance Tool.

8.1.02 8.1.02

SW00464802

People The Assignment tab of the People form was not visible in the French locale.

8.1.00 8.1.02

SW00465540

Overview console

The Overview console did not consider the role 'All' (Owner or Assigned Group) when it was

8.1.00 8.1.02

Defect ID



Corrected in

queried using: 'Show'="Assigned To My Selected Groups".

SW00465630

IT Home page

The difference in the way that the IT Home Page handles service requests that are owned by, or assigned to a partiuclar person or group is now documented. The way that the IT Home page handles those types of service requests is different from the way those requests are handled in other consoles.

8.1.00 8.1.02

SW00449939

Approvals More concise documentation is needed for the Assignment Availability field on the Approval Mapping form.

8.0.00 8.1.00 8.1.01

8.1.02

SW00450658

Documentation

Remove the reference to the "Facilitator" role in BMC Remedy ITSM documentation.

7.6.038.0.008.1.008.1.01

8.1.02

SW00454208

Task In the Task form, the status reason , "Cancelled" was misspelled.

7.6.038.0.008.1.008.1.01

8.1.02

SW00461599

People When a Company / Organization / Department was deleted, too many relationship records were removed from the AST:AssetPeople form.

7.6.04.027.6.038.0.008.1.008.1.01

8.1.02

SW00465514

Multi tenancy

The multi tenancy issue related to the hot fix for defect SW00410272 has been corrected. The hot fix was causing the assignee groups on a change request public, which in turn made the change requests visible throughout to other companies.

7.6.04 8.1.02

SW00465659

Foundation

On SYS:Menu items, the German default user view had overlapping fields.

8.1.01 8.1.02

Defect ID



Corrected in

SW00465760

Rule Based Email

The incident template assignee was not added to the incident request if it was created using email.

8.1.008.1.01

8.1.02

SW00465760

Rule Based Email

The incident template assignee was not added to the incident request if it was created using email.

8.1.008.1.01

8.1.02

SW00466217

Foundation

If you opened the CTM:CFG-ApplicationPreferences form directly, and searched for "System Default", the result did not display z1D_INCStatusQuery (id:301604100), SLA Resolution Status02(id:1000003015) and z1D_IncidentManagementRole (id:302257800) correctly.

8.1.01 8.1.02

SW00466223

Notification Engine

Some tables were missing columns in the NTE:CFG-Notification Events form.

8.1.01 8.1.02

SW00466227

Notification Engine

As it was installed out-of-the-box, the NTE:CFG-Notification Events form contained five implausible records.

8.1.01 8.1.02

SW00466981

Task Management

The two Task Management system filters introduced with BMC Remedy ITSM 8.1.01 generated an ARERR 48829 error when the requester submitted or modified a task and the default Support Group company was different from the company associated with the requester's People record.

8.1.01 8.1.02

SW00450859

Documentation

For information found athttps://docs.bmc.com/docs/display/public/itsm80/Changing+existing+data , links have been provided to relevant and related topics to provide information about changing and updating foundation data with the data wizard.

https://docs.bmc.com/docs/display/itsm81/Updating+existing+data

8.0.00 8.1.02

Defect ID



Corrected in

https://docs.bmc.com/docs/display/itsm80/Changing+existing+data

SW00465667

Communication

The NTE:NTS:Email_200_SystemNT_with_EmailTemplate filter had the phrase: This will not be used, in the Text field.

8.0.00 8.1.02

SW00470076

Consoles The active link SHARE:BRE_QualB-FieldsFromSetSchem2 pointed incorrectly to '*' instead of the '@' server when executing a SQL action. This caused an ARERR 90 ERROR condition to occur.

8.1.01 8.1.02

BMC Asset Management issues

Click the Defect ID column heading to sort this table or to change the sort direction.

Defect ID Description Affected versions

Corrected in

SW00459527

When the locale was set to Portuguese, some of the field values were not translated.

8.1.00 8.1.02

SW00460262

The CI record was corrupted when a user without appropriate permissions to modify the CI attempted to modify it.

7.6.04, 8.0.00, 8.1.00, 8.1.01

8.1.02

SW00460522

When moving a CI to the In Inventory status, users could select inventory locations that are marked to be deleted, retired, or archived. This behavior was incorrect since CIs should not be moved to locations that are no longer available.

8.1.01 8.1.02

SW00463603

When you successfully related a Known Error to a CI, the confirmation message displayed the Instance ID of the configuration item.

8.1.00 8.1.02

SW00463630

An error was displayed when you attempted to add a CI relationship using the + button on the Relationships tab.

8.1.00 8.1.02

SW00463899

If you uploaded CI data using a Transactional CI spreadsheet for each company, and a CI with the same name exists for more than one company, the CI record created during the initial upload, is overwritten with data from subsequent uploads.

8.1.00, 8.1.01

8.1.02

SW00464143

When you created a people record and saved it, BMC.Asset record was not created since the sandbox was not automatically triggered.

8.1.00 8.1.02

SW00464224

Application preferences were ignored when displaying CI records on the Asset Management console.

8.1.00 8.1.02

SW00464498

Layout issues, and mismatched field values were displayed on the purchase order print report.

8.1.00, 8.1.01

8.1.02

SW00464530

When creating a new CI record, if you added and then modified the Work Info field values before saving the record, the Work Info details were not saved to the CI record after you saved the record.

In addition to this, when you attempted to create a new CI record, the Work Info field values you defined in the earlier record were still present on the blank CI.

8.1.01 8.1.02

SW00464949

If you clicked Save multiple times after adding an inventory location for CI, the value of the Quantity in stock was increased with each click.

8.1.00 8.1.02

SW00465710

When opened from an incident the CI Unavailability records were displayed in Read only mode, as opposed to the Edit mode when opened from the Overview Console.

8.1.00 8.1.02

SW00466438

When audit was enabled, instead of displaying the name of the person who modified the record last, the Lifecycle Audit for CI shows the name of user who submitted the record, even if they were not the last person to modify it.

8.1.00 8.1.02

SW00466685

When Asset data was loaded using Data Management, the login ID for people related with a Used By relationship was blank.

8.1.00 8.1.02

BMC Change Management issuesClick the Defect ID column heading to sort this table or to change the sort direction.

Defect ID Description Affectedversions

Correctedin

SW00459247

Tier 1 categorization values are incorrectly populated for related Known Errors created from a Change request.

8.1.00 8.1.02

SW00467928

Tier 2 and Tier 3 Operational and Product Categorizations values defined for a change request were cleared if you used a change template that did not have these values defined.

8.1.00 8.1.02

BMC Service Desk issues.


Corrected in

SW00433442 When you cleared the Contact field in an Incident ticket that had a related Service Request, then saved the ticket, the following error occured: Required field cannot be blank. : SRM:Request : Last Name (ARERR 326)

7.6.047.6.04.028.1.008.1.01

8.1.02

SW00449392 You were unable to update an incident ticket that was created from the Incident console Createoption.

8.0.008.1.008.1.01

8.1.02

SW00451360 The HelpDesk_QueryList_Service operation on the HPD_IncidentInterface_WS web service had incorrect data types.

8.1.00 8.1.02

SW00453685 The Company field selection was improperly set to Global in the Select Operational link and in the Categorizations link when you created a new Incident ticket.

7.6.047.6.04.028.0.008.1.008.1.01

8.1.02

SW00454219 Indexes were added to the Overview console, to improve its performance.

8.0.008.1.008.1.01

8.1.02

SW00459095 When adding Impacted Area information to a problem investigation, you received the following error message: Message [48756] Please select a valid Site from the 'Site' menu. if Site Group is NULL

8.1.008.1.01

8.1.02

SW00459867 The following error message was incorrectly appearing in the Problem Investigation form: "The Problem Coordinator search did not find an Assignee. Either the Problem Coordinator is currently unavailable for assignment or there are no Problem Coordinator with a Full Name of <name searched for>. ARERR 45928"

8.1.00 8.1.02

SW00459930 The lock-down banner and lock-down work flow was not working in the Help Desk (Incident) form.

8.1.008.1.01

8.1.02

SW00460909 An incorrect error message was being displayed in the Spanish locale.

8.1.00 8.1.02

SW00461052 The integration between the Vendor field and Workinfo entries in Incident Management now behave as they do in Problem Management.

8.1.00 8.1.02

SW00461447 The priority was not set correctly on tasks if you created them from a non-English version of the Problem investigation form.

8.1.008.1.01

8.1.02

SW00462048 When you selected All in the Incident console Show field, you received an ARERR 552 error message.

8.0.00 8.1.02

SW00462697 In all locales, a column title in the Incidents table was translated to HPD_CI, instead of a translation of the English column title.

8.1.00 8.1.02

SW00462716 The PBM:CFG-Rules "Auto Close Completed" (id: 303597600) is not being set on new problem investigation records. Consequently, problems fail to auto-close at the correct time.

8.1.00 8.1.02

SW00463955 Only administrators could see notifications sent by reminders.

8.1.00 8.1.02

SW00464159 In Incident Management: multi-tenancy 7.6.04.02 8.1.02

environments, a user with restricted access could search for and view information about people outside of the user's company.

8.0.008.1.008.1.01

SW00464924 When Relating a CI to incident tickets, the Impacted Areas associated to the CI were not being associated to the ticket.

8.1.00 8.1.02

SW00465315 Vendor field auditing was not enabled on the Help Desk form (HPD:Help Desk).

8.1.00 8.1.02

SW00465487 On the HPD:Help Desk form, the status of Closed was in English in German localizations of the form.

8.1.01 8.1.02

SW00465906 The internal work log entries were visible to users. 8.1.00 8.1.02

SW00465913 If you reverted a localized version of the Application Preferences window to English, many of the headings in the window were duplicated.

8.1.01 8.1.02

SW00466140 The Incident Interface filter (HPD:HII:CheckReqdFields_050_E) was executed prematurely.

8.1.00 8.1.02

SW00466634 You could not related CI Unavailability to an Incident ticket if the CI included an entry in the Status Reason field.

7.6.047.6.04.028.0.008.1.008.1.01

8.1.02

SW00467016 On the HPD:Help Desk form, the following fields were set correctly by the Assign to me function if a previous assignee had been assigned: z1D_Assignee_Email, z1D_Assignee_Phone and z1D_Assignee_Site. The hover text for Assignee provided incorrect information.

8.1.00 8.1.02

SW00467025 The Categorization tab was missing from the Incident form when you were searching Incidents.

8.1.01 8.1.02

SW00467174 When choosing an Incident template, the application now provides more information about the template to help you select the correct one.

8.1.01 8.1.02

SW00467309 When creating an Incident ticket using a template that you selected from the Template Selection dialog box, you received the following error message: ARERR 1291041

8.1.01 8.1.02

SW00467644 The position of The Locked field in the Work Detail tab is was aligned.

8.1.01 8.1.02

SW00467702 You would encounter issues creating a Known Error record from a Problem Management ticket if you used double quotation marks in the Work Around and the Resolution fields.

8.0.00 8.1.02

SW00468222 When defining company level access template for a company, if the user belongs to multiple support groups of the same company, multiple records are listed on the template selection dialog box for each support group.

8.1.02 8.1.02

SW00469176 In Incident Management, the CI was being overwriten in the Relationship tab when you created a new CI on Atrium console and promoted it.

7.6.04.028.0.008.1.008.1.01

8.1.02

Other issuesKnown and corrected issues for areas other than installation and upgrade

Click any column heading to sort this table or change sort direction.


Corrected in

SW00470503

The following error messages are displayed in the AR System error log file after every five minutes:

390603 : Der SQL-Datenbank-Vorgang ist fehlgeschlagen.ORA-00936: Ausdruck fehlt (ARERR 552)

ARERR 552 "Missing expression" in Filter INT:HPDSLM:MeasurementStatusUpdate-SLMStatus-BreachedUpdate

8.1.00 8.1.02

SW00470641

When you create some service targets to be used in an agreement, create an agreement without any milestones, and click Build in the SLM Console to build the agreement, the following error message is displayed:

Require field cannot be blank 490000400 (ARERR 307)

8.1.00 8.1.02

SW0047100 When you randomly submit several records to attach 8.1.01 8.1.02

7 them to the same request-based service target and meet the Stop When condition so that some service targets are breached and some service targets are met, the LastSVTMeasurement field for all measurement records for a given service target is updated to "Yes" when you close the measurement for that service target.

SW00472524

When you attach a service target to the HPD:Help Desk, CHG:Infrastructure Change,SRM:Request, or the WOI:WorkOrder data sources and if the service target due date is breached, due to a direct SQL command from the filter corresponding to the data source involved, only the application record SLM Status field is updated to a breached status. The Last Modified By or Last Modified Date fields are not updated.

8.1.01

BMC Service Request Management issuesClick the Defect ID column heading to sort this table or to change the sort direction.


Corrected in

SW00416454 Activity Log entries and attachments in a service request are only passed to the first-level fulfillment request generated from the service request. For example, if a service request process creates a series or work orders, only the first work order will contain attachments and Work Info entries from the service request.

Workaround: From the second or third-level related work order, change request, or incident, click theView Service Request link. View attached files and Activity Log entries on the service request'sDetails tab.

8.1.028.1.018.1.008.0.007.6.047.6.037.6.00

SW00424934 When you submit an issue from a Knowledge Base article in the Request Entry console, the URL to the article is not active in the work notes of the fulfillment record.

8.1.028.1.018.1.008.0.007.6.04

Workaround: Copy and paste the URL into the address bar of a browser to view the article.

7.6.037.6.00

SW00402329 When you install BMC Service Request Management on a BMC Remedy IT Service Management stack, inactive summary definitions that were offline are deployed.

Workaround: Take the inactive summary definition offline after installation is complete.

8.1.028.1.018.1.008.0.007.6.04

SW00424695 When you perform an advanced search to locate an incident or configuration item (CI) to relate to a work order, the Customer Company does not appear on the Date Range and Location tab when you click Current Location.

Workaround:

1. Search for a work order in the Work Order form.

2. Click the Relationships tab.

3. In the Create Relationship area, choose Incident or Configuration Item from the Search list.

4. Click the Search (magnifying glass) icon.

5. Click Use Advanced Search.

6. Click the Date Range and Location tab.

7. In the Location area, manually choose values from the Customer Company, Region, Site Group, and Site+ lists.

8.1.028.1.018.1.008.0.00

SW00425903 An attempt to perform a bulk export of SRDs from the Import Export console fails with an error message stating that the script is either busy or has stopped responding.

Workaround: You can ignore this error message. Click Continue to proceed with running the script, or select the Do not ask me again option on the message box and then click No.

8.1.028.1.018.1.008.0.00

SW00426875 When an SRD name includes parentheses, and you include parentheses in a search, the system exhibits one of the following behaviors:

The search is unsuccessful

8.1.028.1.018.1.008.0.00

The search is successful, but includes an error message stating that the full text search (FTS) service could not complete the requested operation.

Workaround: Do not include parentheses when searching for an SRD by its name, unless you are using a complex query.

SW00428518 If you use Product Ordering to request a hardware CI that is in inventory, and the change request is cancelled, the CI is not put back into inventory.

Workaround: Place the CI back into inventory manually, as explained in Placing non-bulk CIs in inventory.

8.1.028.1.018.1.008.0.00

SW00447569 When you try to do an export from the Import Export Console, no output file is created on the server, even though there are no errors.

Workaround: Make sure that Java is accessible to the exporter:

Verify that java.exe is located in C:/Program Files/Java/jre6/bin (Windows) or /usr/java7_64/jre/bin (UNIX).

Configure the JAVA_HOME environment variable to the full path to java.exe, for example, JAVA_HOME = C:/Program Files/Java/jre6/bin (Windows) or $JAVA_HOME = /usr/java7_64/jre/bin (UNIX).

8.1.028.1.018.1.008.0.00

SW00444032 In the Work Order Console, criteria you specify in More Filters for the Requested For user is ignored. Results shown in the Work Orders and Tasks tables are not filtered for the Requested For user(s). In addition, when you click Clear All in the More Filter Criteria dialog box, the Requested For information is not cleared.

8.1.028.1.018.1.00

SW00463717 The Request Again link appears for Quick Launch service requests, even though these service requests do not make use of Request Again functionality.

Workaround: To request again, locate a quick launch request in Popular Requests or by browsing categories, select it, and click Submit.

8.1.028.1.018.1.00

SW00464157 Query menus do not display all matching records from their underlying forms, or not all navigational categories and service request definitions (SRDs) display on the Browse page of the Request Entry console.

Workaround: Make sure that the Max Entries Returned By GetList setting on the Configuration tab in Server Information is configured to accommodate the number of items to be displayed. For more information, see About query menus, Configuring navigational categories, and Setting administrative options (BMC Remedy Action Request System documentation).

8.1.028.1.018.1.00

SW00471695 For users with Login IDs that include the string \URL, error messages display when the user browses categories.

8.1.028.1.018.1.00

8.1.02.001

SW00473795 If an SRD is configured with actions that include the CUSTOMER keyword in the qualification, CUSTOMER is resolved by using the Requested By information instead of the Requested For information. In this situation, the actions do not function as expected for On Behalf Of requests.

8.1.028.1.018.1.00

8.1.02.001

SW00460995 When you submit a Product Ordering service request, the following error is reported:

Please enter valid Manager Name. (ARERR

48905)

Workaround: For more information about this issue, refer to knowledge article KA410160, available from the BMC Support Knowledge Base.

8.1.028.1.01

SW00462720 When you use the Data Wizard to update a user login ID, favorites for that user no longer appear in the Request Entry console.

Workaround:

1. In the SRS:ServiceRequest_MyFavorites form, search for all entries that contain the old login ID in the Submitter field.

2. Modify each entry in the search results to use the new login ID in the Submitter field.

8.1.028.1.01

SW00470546 Query menus don’t work properly if the value in the 8.1.02 8.1.02.001

qualification contains a $ character. 8.1.01

SW00471468 You can create a duplicate navigational category at the same level in a branch, and when you try to modify or delete the duplicate, the system returns an error that a category with the same name already exists.

8.1.028.1.01

8.1.02.001

SW00471674 In the Browse view in the Request Entry console, the system hangs if you click the icon for a navigational category in the All Categories list.

8.1.028.1.01

8.1.02.001

SW00472086 Query menus don’t work properly if the value in the qualification contains a \ character.

8.1.028.1.01

8.1.02.001

SW00472088 A menu under a condition doesn’t refresh when the condition is selected.

8.1.028.1.01

8.1.02.001

SW00473068 For users with no User Preference record, no questions display in the Provide Information screen.

8.1.028.1.01

8.1.02.001

SW00473354 If you delete a menu choice for a conditional question, and then delete the related condition and sub-questions, other conditional sub-questions appear in the wrong order in the Provide Information form.

8.1.028.1.01

8.1.02.001

SW00473790

SW00474592

If you remove and add questions in a service request definition (SRD), the question text does not align with the correct set of response options.

8.1.028.1.01

8.1.02.001

SW00473791 If there are more than ten second-level navigational categories, the chevron icons disappear when a user browses categories.

8.1.028.1.01

8.1.02.001

SW00473794 If an SRD has two or more questions with the same question text, only one of the questions is visible in the Question field in the Query Builder when you try to create a query menu question.

8.1.028.1.01

8.1.02.001

SW00474517 When you try to create an On Behalf Of request and you select a Requested For user that you are not authorized to act on behalf of, ARERR 46422 displays: You are not authorized to act on behalf of username. Also, Submit and other buttons might become disabled, which prevents you from taking any further action on the request.

8.1.028.1.01

8.1.02.001

SW00465678 The BMC Remedy User Error message that appears in the Provide Information screen when you enter invalid information in questions is not descriptive of the problem. Also, in localized versions of the application, the error message appears in English.

8.1.02

SW00472690 When you run an Update operation in the Data Wizard for Product Categorization or Product Model/Version, the status of the WOI:WorkOrderInterface_Create form continues to show as Pending in the Data Wizard Status window.

8.1.02 8.1.02.001

SW00463764 Notifications that are sent when a service request is submitted do not contain values from mapped SR fields.

8.1.018.1.008.0.007.6.04

8.1.02

SW00464295 When a query menu depends upon the value in a text field, you cannot enter wildcards in that text field.

8.1.018.1.008.0.007.6.04

8.1.02

SW00466784 In localized versions of the application, the Relationships tab on the Work Order form contains descriptive data that is not localized.

8.1.018.1.008.0.007.6.04

8.1.02

SW00468147 Internally represented responses for Date and Time field type values are not converted correctly.

8.1.018.1.008.0.007.6.04

8.1.02

SW00423092 When submitting a one-time request on behalf of another user, when the submitter responds to questions on the Provide Information form, if the SRD is configured to use the CUSTOMER logon ID for autofilling responses, the system uses the submitter's information to autofill answers to questions in the SRD, instead of using the On Behalf Of user's information.

8.1.018.1.008.0.00

8.1.02

SW00466063 In non-English locales, tooltips in the Favorites menu in the Request Entry console display "SRD Title" in front of the service request definition (SRD) name.

8.1.018.1.008.0.00

8.1.02

SW00466510 In localized versions of the application, on the 8.1.01 8.1.02

Process View tab in request details, the Status and Status Reason values are not translated.

8.1.008.0.00

SW00466511 In localized versions of the application, service requests are created with navigational categories and other data in the wrong locale.

8.1.018.1.008.0.00

8.1.02

SW00460007 In the Internet Explorer 8 (IE 8) browser, drop down values in menu fields in the Provide Information screen might not display correctly when you click the scroll bar.

8.1.018.1.00

8.1.02

SW00461833 Users with the Service Request User permission cannot view suggestions from the Service Request Coordinator Console.

8.1.018.1.00

8.1.02

SW00462980 There are performance problems when the same service request is submitted by multiple users within the same time frame.

8.1.018.1.00

8.1.02

SW00464148 Query menu questions do not work as expected when the qualification includes wildcards and logical operators.

8.1.018.1.00

8.1.02

SW00465096 A dynamic query menu question that depends upon a condition shows no menu items the first time you select the parent condition.

8.1.018.1.00

8.1.02

SW00465166 In environments where there are a large number of requests, there are performance issues when users try to view request details.

8.1.018.1.00

8.1.02

SW00465445 If you make a service request definition (SRD) offline while a user is logged on, the user can still submit requests from the SRD under Popular Requests.

8.1.018.1.00

8.1.02

SW00466506 If the Question Text for a menu question contains more than 254 characters, the question and response do not display on the Additional Details tab in request details.

8.1.018.1.00

8.1.02

SW00466738 Notifications for service request activity log updates do not include the contents of the activity log entries.

8.1.018.1.00

8.1.02

SW00467264 If the same question is referenced more than once in a query menu qualification, an empty items list is always returned.

8.1.018.1.00

8.1.02

SW00467345 When users without correct permissions try to access work orders from the Overview Console, the access attempts are not properly rejected and the system opens a duplicate Overview Console.

8.1.018.1.00

8.1.02

SW00467515 Users that no longer have entitlement to a service are able to complete and submit service requests in the cart or saved as draft.

8.1.018.1.00

8.1.02

SW00469374 For users with Login IDs that include the string \009, error messages display when the user browses categories, and questions and responses are not saved correctly.

8.1.018.1.00

8.1.02

SW00470403 There is no field focus when the Provide Information screen opens, making it difficult to read with the JAWS accessibility tool.

8.1.018.1.00

8.1.02

SW00465744 No questions appear in the Provide Information screen in the Request Entry console if the service request definition (SRD) contains a query menu question with no Query Filter value.

8.1.01 8.1.02

SW00465750 When multiple Requested For users have the same first and last name, when a request is submitted on behalf of one of those users, the request is associated with the wrong user.

8.1.01 8.1.02

SW00466060 If you clear the Requested By contact fields, a People match error occurs (ARERR 1690110).

8.1.01 8.1.02

SW00466402 You cannot modify an Approval Chain if the selection criteria has already been defined.

8.1.01 8.1.02

SW00467165 If you have three levels of query menu questions, the query menu answers disappear when you select the third question in the Provide Information screen.

8.1.01 8.1.02

SW00467198 In the localized version of the application, some of the text in the Approval History in request details is not translated.

8.1.01 8.1.02

SW00467473 For service request definitions (SRDs) with complex processes, the status of service requests is not set to Cancelled when backend fulfillment requests are cancelled.

8.1.01 8.1.02

SW00467940 There are performance problems when you manually 8.1.01 8.1.02

assign and then save an incident.

SW00467957 When you run a Data Wizard operation to update the Login ID, it appears that some processes do not complete.

8.1.01 8.1.02

SW00468312 If the Clear OBO Question Responses request preference is set to Yes, you cannot save a request on behalf of another user in the Internet Explorer (IE) browser.

8.1.01 8.1.02

SW00469833 You cannot export service request definitions (SRDs) that are related to change templates that have a Class value of Standard.

8.1.01 8.1.02

SW00471296 You cannot import a service request definition (SRD) when the SRD description has more than 255 characters.

8.1.01 8.1.02

SW00471297 If you import a service request definition (SRD) by using the Merge Data import option, actions are not imported.

8.1.01 8.1.02

SW00475678 If an approver sends a question about a pending request and then the requester cancels the request, the request still appears under the Requests needing attention list.

8.1.01 8.1.02.001

bmc remedy itsm 8.2 fixes

Documents