CRM Software (Customer Relationship Management) and Contact Management Solutions

Access Rights for User-Defined Fields: Previously, under certain circumstances Maximizer users were able to modify user-defined fields when the users' security rights were set to read-only.

Maximizer Enterprise 7 Version 7.5 Service Release 1 - Series 1344
Released on October 27th, 2003

Type of Release:	Service Release
PSN Prefix:	N/A
Files Modified:	Not available

Changes:

Hotlist Task and Appointment Import from ACT!: Previously, in some circumstances when Calls, Meetings, and To-dos from ACT! were imported into Maximizer Enterprise, the Contact and User association was lost. This issue has been resolved.
Program Error in Import from GoldMine 3.x: Previously, when importing data from GoldMine 3.x to Maximizer Enterprise, a program error would occur. This issue has been resolved.
Email Addresses Not Imported from GoldMine 5.x: Previously, in some circumstances, email addresses for some Contacts from the Contact tab in GoldMine were lost when imported to Maximizer Enterprise. This issue has been resolved.
Basic Field Import from GoldMine 5.x: Previously, when importing data from GoldMine 5.x to Maximizer Enterprise, some of the basic fields, which did not exist in Maximizer Enterprise, were imported as user-defined fields and the values were not matched to the appropriate fields. These basic fields included: Source, Asst., Contact Type, Industry, Interest, Acc. Manager, and Open. This issue has been resolved.
License Check Stopped Users from Logging In: (This issue applies only to computers that act as IIS servers for Portals) Previously, in some environments, users were unable to login into the Employee Portal even though sufficient licensing had been applied. This issue has been resolved.
Passwords Saved in ISAPI Log File (This issue applies only to computers that act as IIS servers for Portals): Previously, when the log level for the Maximizer Web Server component, was set to greater than 3, the resulting ISAPI log file could contain passwords displayed in plain text. This issue has been resolved.
Logins Denied for the Customer Portal (This issue applies only to the Customer Portal on the computer that acts as the Application Server): Previously, the Customer Portal was using the rights granted in the "Partner Portal Administration Users" (P_ADM) security group rather than the "Customer Portal Administration Users" security group (C_ADM) to validate the Customer Portal Administrator login and to determine the visibility of the News Manager, Login Manager, and Discussion Manager main menu options. As a result, users were denied access to Customer Portal's Administrator and an "Unauthorized internal user" message was displayed. This issue has been resolved.
Email Alerts for the Customer Portal Were Not Delivered (This issue applies only to the Customer Portal on the computer that acts as the Application Server): Previously, in the Customer Portal, after an administrator added a news story and elected to send an email alert, not all email recipients that should have received the alert were receiving it. The problem occurred due to the server running out of database resources to perform the query. This issue has been resolved.
Email Alerts for the Partner Portal Were Not Delivered (This issue applies only to the Partner Portal on the computer that acts as the Application Server): Previously, in the Partner Portal, after an administrator added a news story and elected to send an email alert, not all email recipients that should have received the alert were receiving it. The problem occurred due to the server running out of database resources to perform the query. This issue has been resolved.
Some Tasks and Appointments Not Visible in Hotlist Window: Previously, selecting and deselecting the "Carry forward unfinished tasks" option for the Hotlist in the Preferences > Calendar/Hotlist tab would cause problems with the Hotlist filter, resulting in some tasks and appointments not to be displayed in the Hotlist window. This issue has been resolved.
User-Defined Field Search: Previously, when searching Address Books that contain a large number of table user-defined fields, User IDs were displayed as selection criteria, rather than the matching user-defined field items. This issue has been resolved.
Maximizer User Access Rights: Previously, when changing logins from a user with access rights to a particular Maximizer window to a user without rights to this window, an "insufficient rights" message was displayed. This issue has been resolved. The message is no longer displayed and the corresponding window tab is not visible to the user with insufficient access rights.
MTI Empty String Value: Previously, when importing data using MTI (Maximizer Transfer Interface), alphanumeric user-defined fields with null values appeared blank. The proper behavior is for these fields to be ignored. This issue has been resolved.
Company Name Change: Previously, when a Company and the associated Contact entry were opened consecutively using the Enter key under specific circumstances, the Company name may have been changed. This issue has been resolved.
Some Email Messages Not Visible in the Inbox: Previously, in some cases when a user's mailbox was on a Microsoft Exchange Server, not all messages were visible in the Inbox of Maximizer's email window. This issue has been resolved.
Slow Opening of the Email Window: Previously, if a user's mailbox was on a Microsoft Exchange Server and a large number of items were contained in the server's Public Folders, opening the Email window in Maximizer would require a long time. This issue has been resolved. By applying this service release, the Public Folders on the Microsoft Exchange Server will no longer be visible.
Default Entry Does Not Retain Security Group: Previously, if the Owner field for the Default entry was a security group, when a new record was created it was saved with the user ID of the logged-in user as the Owner, not the security group. This issue has been resolved.
Global Edit Does Not Work with Default Entries: Previously, performing a Global Edit on users' default entries did not edit the default entries. This issue has been resolved.
Saved Email with Attachment Not Forwarded: Previously, email with an attachment stored in Maximizer's Documents tab did not get sent when forwarded. This issue has been resolved.
Changing Email Folders Causes Program Error
Previously, if a user's mailbox was on a Microsoft Exchange Server, and the user opened and closed an email message using the email service provider's editor, navigated to different folder, and then continued to open and close email messages, a program error occurred. This issue has been resolved.
Error Linking to Maximizer through ODBC Using Microsoft Access: Previously, using the Maximizer ODBC driver to link to Maximizer tables in Microsoft Access, Access reported an Invalid Argument error and would not link the tables. The problem appeared on machines where Windows Update had recently updated the msjet40.dll file with a newer version. This issue has been resolved. Now, during linking to external data source in Microsoft Access, the user has to specify a unique index (combination of fields) for each linked table in order for that table to be updateable. This does not apply to tables that are read-only by design -- they will remain read-only.
MTI Imported Records Not Set to Public by Default
Previously, when logged in as a user other than MASTER, imported records were set as Private to a user when an owner was not specified, rather than being set to Public. This issue has been resolved.
MTI Imported Records Not Set to Specified Owner: Previously, when importing Address Book entries using MTI, the specified record owner was ignored and records were imported as Public. This issue has been resolved.

Maximizer Enterprise 7 Version 7.5 Hot Fix No. 6 - Series 1320
Released on May 16th, 2003

Type of Release:	Hot Fix Release
PSN Prefix:	N/A
Files Modified:	Madata6.dat

Changes:

Some Email messages not visible in the Inbox: In some cases when a user's mailbox was on a Microsoft Exchange Server, not all messages were visible in the Inbox of Maximizer's email window. This issue has been resolved.
Slow opening of the Email window: If a user's mailbox was on a Microsoft Exchange Server and a large number of items were contained in the server's Public Folders, opening the Email window in Maximizer would require a long time. This issue has been resolved. By applying this hot fix, the Public Folders on the Microsoft Exchange Server will no longer be visible.

TOP