|
||||
NOTE: There are some manual steps required! See the notes at the bottom.
List of issues resolved in 01-04-2008 LPM 4.0 Rollup: For download link see attachment at the bottom
New CR | Old CR | Description | ||
N/A | CR113600 | After upgrading LPM from version 3.0 to 4.0 an exception in web app when clicking each tab in 'details. | ||
N/A | CR113760 | Problems with active directory in LPM 4.0. Where if the domain being used to get user informaition was part of a forrest it was possible that LPM could not get user information. | ||
N/A | CR113866 | Made it possible to reuse same external system ID. | ||
N/A | CR114034 | Console is slow in German. | ||
N/A | CR114168 | Exception thrown when adding an AD user. | ||
N/A | CR114335 | Multiple contacts are not sent email. | ||
N/A | CR114491 | Internal fields unable to find the correct approval in the tree | ||
N/A | CR114619 | A SQL script that bring multiple rows does not get processed right. Only the first row would be returned. | ||
CR1340 | CR115286 | Sql queries with user names like O'brien are throwing exceptions | ||
CR1746 | CR115651 | Task engine does not run after upgrade. | ||
CR546 | CR115652 | Some users of running instances dont get migrated. | ||
CR652 | CR115695 | Details tab in web only used "show in web" flag on new requests and not existing ones. | ||
N/A | CR115883 | In Russian LPM email listener are saved as a Database listener | ||
CR1360 | CR116105 | If looking up a null valued attribute in AD the system always throws an error. | ||
CR663 | CR116199 | Open/closed filter doesnt work | ||
CR1759 | CR116200 | If a contact is not found during upgrade, audit history doesnt display | ||
CR1770 | CR116597 | {\ | Approval - approved contacts\ | } field is always blank in an email template |
CR568 | CR116916 | Importing workflow from a different server gives error for core credentials | ||
CR746 | CR117564 | LDAP lookups failing | ||
CR583 | CR117665 | Get a Null Reference Exception when Requester value is not in AD | ||
CR1391 | CR117668 | Changes to IsWorkflowCompleted Stored Proc and also a New Index | ||
CR1792 | CR117691 | If the listener SQL query returns duplicate external system IDs in one scrape then the listener will throw an exception | ||
CR1404 | CR118319 | Resolves issues when upgrading from an older version of LPM | ||
CR605 | CR118320 | Fields from the event listener contains special characters | ||
CR777 | CR118534 | Opening multiple consoles from the same machine to different servers causes all consoles to use the last opened console's connections | ||
N/A | CR118724 | When you save settings in the database utility the task engine log breaks | ||
CR619 | CR118873 | Web Console does not properly load when viewing days with hundreds of requests that day | ||
CR790 | CR118874 | Web console does not display requestor for some requests | ||
CR803 | CR119245 | In addition to the AD blowing up when it doesn't find someone, it is also not returning the value found. | ||
CR870 | CR119477 | LPM Performance Issues | ||
CR1546 | CR122551 | When editing/saving a listener it will over-write the requestor field | ||
CR1033 | CR122576 | Database Security Enhancements for DB Listener | ||
CR1047 | CR122957 | LDAP Helper bug -- sometimes an exception can be thrown that will cause the workflow to not be executed | ||
CR953 | CR123362 | Database upgrade can fail if certain special characters exist in the workflow contexts in the database | ||
CR1163 | CR123738 | Error with approvals | ||
CR1615 | CR124133 | Requestor Field brackets are sometimes not setup properly | ||
CR1207 | CR124136 | The console can crash sometimes when attempting to setup the exception workflow | ||
CR2073 | CR124532 | Database Security Enhancements for EMail Listener | ||
CR1299 | CR124766 | Some fields in AD cannot be modified unless a value is already present | ||
CR4411 | CR124991 | SQL error occurs when connecting to remedy with SQL listener | ||
CR4416 | CR125013 | Issues with VBScript Execution |
This patch includes some database updates. The schema is updated to version 4.0.1.0 with this patch. The database update is fully automated, all you need to do is launch the database utility, and login to the database. You should then be prompted to perform the update.
Launch the Database Utility from the Start Menu
Enter the database password and then click 'Test connection'
You will be prompted to update the database, Click OK
The upgrade window will appear, press Upgrade on the bottom right.
The upgrade should complete in a minute or two
When it is done it will prompt you to save the update log.
You may now exit the utility.
Done!
There are no comments on this document
|
|||||