Bizarre things
The project I am on recently upgraded to Remedy Version 7.1 patch 4. We had previously done a lot of testing on our staging server with no issues. Soon after we upgraded the Production server, all manner of hell broke loose.
First, BMC changed the way Remedy handles the ARDBC LDAP plugin's date formats. In 6.03, dates coming from an Active Directory were handled correctly. For instance, if I used a Vendor table pointing to an AD class through the LDAP to search for records that had been recently modified, I could run a query like:
modifyTimestamp >= "2008/10/31 7:00:00 AM"
This, of course, would return all records modified since 7AM on the 31st. 6.03 converted that date into 20081031070000.0Z. Version 7.1 converted it to 20081031070000Z. Note the subtle difference. This would cause a No Matching Requests popup.
What I discovered is that I had to set a new field on the LDAP Configuration form called LDAP Date-Time Format to AD Generalized Time.
Our testing showed no problem since, as per usual, our staging environment can't link to the AD. So, we couldn't really test the LDAP. Fun, eh?










