This topic relates to vFire Core 9.2.3, released in September 2015. You may also wish to view other new features, or the release notes in full.
Fixed Issues in vFire Core 9.2.3
The following table lists problems fixed in this release:
| Issue Number (internal ref in brackets) | Functional Area | Short Description | Fixed in Version |
|---|---|---|---|
| 9086
(5023) |
IPK | The incorrect call screen was applied when switching a call's IPK Stream if the call's Type was not linked to the new combination of IPK Stream and IPK Status in the System Admin settings for 'Link Type/Stream/Status to Call Screen Set' . Issue fixed. | 9.2.3 |
| 9653
(6268) |
CMDB | On the call details screen, selecting 'Impact' from the Location QD dropdown generated a SQL error. Issue fixed. | 9.2.3 |
| 9653
(6269) |
Messaging error in the Windows application event logs: " Query: MSGQUEUE INSERT Message: Cannot insert the value NULL into column 'MAP_REF', table 'VSMPROD.dbo.HD_MSGQUEUE'; column does not allow nulls. INSERT fails." Issue fixed. | 9.2.3 | |
| 9829
(4428) |
API | New API workflow Async transactions have been implemented and can be accessed via SOAP UI. | 9.2.3 |
| 10132
(6373) (6889) (4081) |
Security | Officers who do not have CMDB Security Roles with the 'Financial View' option selected, no longer see fields from the Financial section of the CMDB Details screen in the Available Columns section of the Column Configs window for CMDB searches. | 9.2.3 |
| 10132
(6684) |
Security | A security warning will now appear if officers attempt to open a linked entity record (such as a Person record) from a call or request details screen if the entity record is in a partition the officer does not have access to. | 9.2.3 |
| 10132
(6899) |
Security | Columns on Search or Outstanding windows that reference entity data the officer does not have permission to see (due to CMDB Security Role permissions, or partition access), will now display a blank value. | 9.2.3 |
| 10357
(4824) |
IPK | Negative call numbers are no longer created in the database when IPK Rules are triggered by incoming emails. | 9.2.3 |
| 10399
(5663) |
Unspecified | Call, Request and Task Outstanding windows were displaying incorrect values, including commas, if the column referenced extension fields linked to multiple types of entity screens; for example, field X is linked to a call and a request screen. Issue fixed. | 9.2.3 |
| 10454
(4342) |
Database | Extension fields added to a screen as 'linked fields' in Designer will no longer appear under that screen set in the Available Columns list in the Column Configuration window for Search/Outstanding windows. However they can still be added via entity drill down. | 9.2.3 |
| 10704
(5026) |
Designer | Values can now be pasted into text fields that have a mask applied. | 9.2.3 |
| 10732
(6052) |
Designer | In Designer, when creating a new dropdown field, the 'Assign an existing list' menu offered the option "Custom Search Query". This option has been removed. | 9.2.3 |
| 11046
(5489) |
Wrapper & Controls | Pasting HTML content into the 'Actions & Solutions' text area field no longer corrupts the history window of the call, request, or task into which it was pasted. | 9.2.3 |
| 11254
(5021) |
Wrapper & Controls | Setting the default search criteria on the Customer QD on a call details window now also changes the Customer QD setting on the call search window. | 9.2.3 |
| 11260
(5027) |
Workflow | Delay Task time was incorrectly calculated when "Calculate time using working hours" was selected and a there was a value in the Day field. The Day input field is now hidden when "Calculate time using working hours" is selected. | 9.2.3 |
| 11448
(6279) |
Wrapper & Controls | Selecting and dragging text in a text area field resulted in a screen artifact, or black box, being left on the screen. Issue fixed. | 9.2.3 |
| 11573
(5174) |
Portal | Custom screens were reverting to the default screen upon receiving the mandatory field prompt when submitting a call or request in the customer portal. Issue fixed. | 9.2.3 |
| 11880
(4932) |
IPK | Canceling out of a cloned call before it is saved, deferred, or forwarded now correctly removes the call from the system. | 9.2.3 |
| 12273
(5151) |
Unspecified | System files, such as .sql, .scp, .xml, .html, .js now display properly when opened using Notepad, Wordpad, or Notepad++ | 9.2.3 |
| 12732
(5666) |
Wrapper & Controls | The accents on characters such as è,é,ê,î,ô,û, were not displaying when typed into HTML text area fields. Issue fixed. | 9.2.3 |
| 12791
(5455) |
Wrapper & Controls | Read Only text fields are no longer editable on Person and CMDB windows. | 9.2.3 |
| 12912
(5664) |
Designer | Within Designer, field properties were not available for the field 'Attach File'. Issue fixed. | 9.2.3 |
| 13059
(5661) |
Workflow | Behavior for Activation Task rule options "All parent tasks closed, with at least one complete" and "All parent tasks complete" has been fixed. | 9.2.3 |
| 13062
(5677) |
Upgrade | Duplicate saved searches were resulting in errors in the event log. Issue fixed. | 9.2.3 |
| 13428
(5748) |
Partitioning | Partitioned fields such as Priority, Risk, Impact, Urgency, etc, no longer include the default value from the default partition when the field is viewed from a call, request, or task in the non-default partition. | 9.2.3 |
| 13480
(5782) |
Reporting | In Report Designer, the maxLength Parameter value attribute for the CI_ASSET_REF field (which is found in CMDB reports) now derives its value from the database. In most cases this will be 255 chars for SQL and 40 chars for Oracle. | 9.2.3 |
| 13729
(5853) |
Config Port | When running a Config Port, the PROFILE_REF value in SU_FIELD is now being properly updated for Custom Profile dropdown boxes, resulting in the correct profile list values now being displayed in the target system after import. | 9.2.3 |
| 13738
(5854) |
Workflow | Tasks now open either in Review mode or Action mode correctly, depending on the Workflow role settings of the officer. | 9.2.3 |
| 13849
(6227) |
Designer | Fields that are mandatory due to conditional rules were displaying double and triple asterisks beside the field name (** and *** respectively). A single asterisk is now displayed. | 9.2.3 |
| 13935
(6065) |
Portal | Improvements to the ordering of search results in the Portal, for better consistency and usability, e.g.: Calls by Call number and Organizations by Org Name. | 9.2.3 |
| 13994
(6163) |
CMDB | In Designer, on Service Action screens, the fields "Initial Cost" and "Ongoing Cost" can no longer be added to the screen twice. | 9.2.3 |
| 14043
(6056) |
Upgrade | Queries intended for pre- 9.1.0 systems in patch-repair-data.scp will no longer run on post-9.1.0 systems. | 9.2.3 |
| 14071
(6066) |
Workflow | Fixed an issue in Conditional Branching Task "Rules Builder" when using = or <> operators and leaving the Value field blank; the blank value is now retained on Save. | 9.2.3 |
| 14192
(6181) |
Searches | When selecting the Graph option on search results that have exceeded the row browse limit, Officers now receive different options depending on whether "Override Browse Limits" is enabled or not enabled in their General Access Security Role. When not enabled, a warning is displayed "You do not have permission to query all records" with no option to override. When enabled, a prompt is displayed "Downloaded Records Limit reached. Do you wish to Requery to obtain all Data? (This could take a while)" with a Yes / No option. | 9.2.3 |
| 14401
(6316) |
Integration | Delegation settings are now preserved after an Active Directory integration scan. | 9.2.3 |
| 14451
(6492) |
Install & Upgrade | Upgrading from version 8 to version 9 no longer generates an error related to the Primary Key on AR_AUDIT_TRAIL. | 9.2.3 |
| 14494
(6320) |
Config Port | Resolved an error occurring during Config Portability Import: "System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary." | 9.2.3 |
| 14500
(6368) |
Designer | In Designer, an issue prevented screens from rendering with the error "Unable to get value of the property 'fieldid': object is null or undefined". Issue fixed. | 9.2.3 |
| 14525
(6264) |
Designer | In Designer, certain fields could not be deleted with the contextual 'Delete' option. Issue fixed. | 9.2.3 |
| 15047
(6662) |
Partitioning | Requests will now be correctly logged in the Customer's partition, or Logging Officer's partition (as appropriate) when the system is configured with the following settings: 'Pre-create Requests' enabled, requests partitioned, and workflow templates not partitioned. | 9.2.3 |
| 15047(6745) | Partitioning | Calls and requests logged in the Customer Portal will now be correctly created in the partition specified in the URL used for login, unless system partition settings are configured otherwise; such as, to use the partition of the officer, the template, or the customer. | 9.2.3 |
| 15056
(6402) |
Install & Upgrade | When using the vFire Core Setup Kit and selecting the Custom Setup option in InstallShield Wizard, "vFire Core" is now correctly displayed in the label instead of "[ProductName]". | 9.2.3 |
| 15156
(6572) |
Unspecified | Customers who have been designated as Delegates can now complete customer approval tasks by email with no errors. | 9.2.3 |
| 15317
(5265) |
Install & Upgrade | Resolved foreign key errors in v8 to v923 upgrades for the following tables: SU_SAVED_SEARCHES, SU_PROFILE_TYPE, SU_FIELD, SU_VIEW_TRANSACTION, CR_TASK_TYPE_FILTER, CR_HISTORY_TYPE_FILTER. | 9.2.3 |
| 15457 13676(6703) (6094) |
Search | Improved performance of text searching when performing call, request, task and knowledge searches. | 9.2.3 |
| 15962(6838) | CMDB, IPK | The default value configured in System Admin for Call and CMDB Custom Profiles was overriding the value set in Call Templates and CMDB Templates. When creating a call or CMDB item from template, the new call or CMDB item now uses the custom profile value set in the template. | 9.2.3 |
| 16366(6970) | Install & Upgrade | Upgrading from v8 to v9.2 was corrupting existing workflow templates, requests, and tasks, resulting in the error "Unable to find Task #xxxxx in the database". Issue fixed. | 9.2.3 |
| 10935
13635 (4775) |
Security | Changes have been made to the Workflow Management security role to provide more granular control over permissions to complete Approval tasks, take over tasks, and the Request Manager ability to modify tasks within their requests. With these changes, the ability to take over tasks does not automatically grant the ability to complete Approval tasks. For more information refer to Workflow Security Role Improvements. | 9.2.3 |
| 14165
14171 (6079) |
Workflow | When doing a workflow template import, the Workflow Import Resolve Values window now correctly displays the Request Type Tiers and Workflow Groups. | 9.2.3 |
| 15153
14676 (6634) |
Workflow | Users with both the Officer and Customer checkboxes selected in their Person Details were unable to approve or reject Customer Approval tasks unless Approval permissions were enabled in their officer Workflow security role. Issue fixed. | 9.2.3 |
| 16242
15672 (6075) |
Workflow | Request schedules with a status of Pending did not appear in the Request Scheduling window if search criteria is configured with the Pending checkbox enabled. Issue fixed. | 9.2.3 |
| 15207
14526 15044 13424 (6285) |
Install & Upgrade | After running the upgrade, some fields on some screens become corrupted or disappear from the screen. Issue fixed. | 9.2.3 |
| n/a
(3048) |
Portal | In the Service Catalog Portal, when launching a search from a QD field on a form, and then selecting a record from the search results the following error occurred: "Unable to cast object of type ´Infra.Rules.LiteProvidedPageHandler...". Issue fixed. | 9.2.3 |
| n/a
(3050) |
Portal | Settings from the CMDB security role are now correctly applied when logging into the HTML Portal, ensuring that CMDB searches are only available when the Officer has appropriate CMDB security role permissions. | 9.2.3 |
| n/a
(3051) |
PDA | The PDA interface will now display the correct priorities when Impact-Urgency Priority Derivation is enabled in System Administration. | 9.2.3 |
| n/a
(3081) |
API | With single sign-on enabled, the vFire Core API for vRO (vCO) connector generates the error "User ID XXXX cannot login using NOAUTH". Issue fixed. | 9.2.3 |
| n/a
(5883) |
In the system admin Incoming Email Server Settings window, the "Default Customer" QD field was returning only person records that have the Officer checkbox enabled. This is fixed so that customer records can be selected in the quick search. | 9.2.3 | |
| n/a
(6081) |
Admin, Console | When importing workflow templates that contain Create Request tasks, the Workflow Import Resolve Values window now prompts for the selection of a Current Manager / Receiving Officer if an exact match does not exist in the target system. | 9.2.3 |
| n/a
(6233) |
Unspecified | MDAC is no longer a prerequisite for vFire Core. | 9.2.3 |
| n/a
(6234) |
Search | Resolved an issue on Oracle systems which was generating an error when performing a text search for Calls, Requests, Tasks, or Knowledge: "Infra.Rules.QueryCommand.Execute ERROR: (VMware Service Manager Web Application System #System) (Query: TEXT SEARCH INSERT WORDS for System #System)" | 9.2.3 |
| n/a
(6265) |
When the System Admin Email option "Log New Call on Invalid Number" is disabled, and an incoming email is received containing an invalid call/request/task number, a warning message will now be written to the System Admin Activity Logs. | 9.2.3 | |
| n/a
(6323) |
Install & Upgrade | Resolved an issue that was causing an error in the log files during system upgrade: "UpdateTags : Failed updating elements : Error '=' is an unexpected token. The expected token is ';'." | 9.2.3 |
| n/a
(6324) |
IPK | The "Default" call template is now displayed and available to select from the vFire Customer Portal. The "VCO Default" call template is now hidden from the customer portal. | 9.2.3 |
| n/a
(6389) |
PDA | The PDA interface now correctly displays Type Tiers in calls. (The issue was specific to unpartitioned systems.) | 9.2.3 |
| n/a
(6445) |
Admin | When adding the first new Workflow Group to a newly created system and database, the group was not retained on Save. Issue fixed. | 9.2.3 |
| n/a
(6448) |
Designer | When dragging and dropping a QD field on a screen in Designer, the right side of the field appeared cut off. Issue fixed. | 9.2.3 |
| n/a
(6599) |
Search | The "Requery Data?" window (also known as the "Override Browse Limit" window) continued to pop up after selecting the Yes or No option. This was happening upon logging back into the system if you had logged out while in the Graph view of a Request Search that had reached its browse limit. Issue fixed. | 9.2.3 |
| n/a
(6686) |
Install & Upgrade | During system upgrade, when trying to modify HTML Elements that do not exist, a 'fail' entry was written to the upgrade log file; example: "MoveElement failed. Could not find element." Also "RemoveDuplicate failed" and "AddElement failed". The wording has been changed to indicate this is not a problem, example: "MoveElement - Could not find element." | 9.2.3 |
| n/a
(6722) |
Install & Upgrade | When upgrading a system, Saved Searches are now upgraded properly and work as expected in the upgraded system. | 9.2.3 |
| n/a
(6757) |
Partitioning | Calls and requests are now correctly logged to the Logging Officer's partition when the system is configured with the following settings in System Admin > Partition Settings: Calls/Requests partitioned, Templates not partitioned, Customer not partitioned, 'Use Linked Officer's Partition' selected. | 9.2.3 |
| n/a
(6758) |
Unspecified | Cosmetic improvement to contents of SQL files to make them more user-friendly while editing. | 9.2.3 |
| n/a
(6811) |
PDA, HTML | In the PDA and HTML interfaces, viewing the Customer Details window no longer generates an error. | 9.2.3 |
| n/a
(6839) |
PDA, HTML | In the PDA and HTML interfaces, when viewing an item in review mode and selecting the Details button on a QD field, the Officer was being logged out. Also, the Details option was selectable on empty QD fields. Both these issues are fixed. | 9.2.3 |
| n/a
(6841) |
Security | A script error message was appearing when trying to access the details of a Configuration Item from the CMDB Search window when the actioning Officer's CMDB Security Role did not grant permissions to that CMDB Item Type. Issue fixed. | 9.2.3 |
| n/a
(6848) |
Unspecified | Message prompts when trying to use Bulk Close on already closed Calls/Requests/Tasks are now consistent . For example: "Request(s) xx, yy will not be processed as they are already closed" | 9.2.3 |
| n/a
(6854) |
Workflow | When using the Bulk Close function on an Approval, and entering text into the Action field of the resulting Sign Off window, that text was being written to the history of dependent tasks if they were later also bulk closed. Issue fixed. | 9.2.3 |
| n/a
(6855) (6848) |
Unspecified | Warning messages that popup when using the Bulk Close function on requests, tasks, and calls have been made more consistent and now better reflect the situation. For example, if attempting to close a request another officer is editing, the following prompt will popup: "The Request(s) xx,yy are currently locked." (with OK button) | 9.2.3 |
| n/a
(6910) |
Email, Workflow | Officers can no longer complete other's Approval tasks via email unless their Workflow Management Role has both "Take Over Approvals" and "Complete Other's Approvals" options enabled. For additional information refer to Workflow Security Role Improvements. | 9.2.3 |
| n/a
(6937) |
Security | Officers that do not have "Take Over Approvals" enabled in their Workflow Management Role can no longer take over Customer Approval tasks that were not assigned to them. | 9.2.3 |
| n/a
(6972) |
Portal | In the Customer Portal, the Customer Approval Task Details window showed only one linked Request CI and/or Request Service. This has been fixed so that if multiple Services and CIs have been linked to the request, all will appear in the Portal for the Customer Approval. This fix also extends to Customer Approval emails. | 9.2.3 |
| n/a
(6973) |
When closing a call with linked Child calls and, at the "Close Child Calls" window, the "Email Customer" or "Email Closure Group / Officer" checkboxes were ticked, emails were not sent to the child call's customer/closure officer/closure group. This is now fixed so that emails are sent to the customer/closure officer/closure group of both Parent and Child calls. | 9.2.3 |