Feature Suggestions for Maximizer CRM

Your votes COUNT! We have finished a number of ideas already. Many are being considered and worked on.

More ideas will be selected each month. So please keep voting and help us understand what matters MOST to you!

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Combine Address Book, User-defined fields, Notes, Documents, Contacts, Hotlist, and e-mail in one view.

    The desktop version of Maximizer enabled the user to view 'tiles' of the Company/Individual/Contact record in the Address Book with User-defined fields, (other) Contacts, Notes, Documents, Hotlist, and an Outlook display -- all in one view, without switching screens.

    As you know, the Maximizer LIVE screen enables the user to see the Address Book data and User-defined fields, and EITHER the (other) Contacts, or Notes, or Documents, or Hotlist, with no view of e-mail.

    I've gotten used to this limitation, but I would be able to work much faster if the lag-time between switching screens between Contacts, Notes, Documents, Hotlist,…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  2. Search by full name

    How is it that we can simply type in Christian and Last name when creating an Appointment to search for an Individual or Contact.
    Yet we can't do the same in the Addressbook search box?
    The fastest way by far of locating a contact or individual is to type Christian and Last name which will always have the least duplicates.
    Can the Addressbook search box get the Appointment functionality?

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  3. "Allow Public Entries" Expansion

    In most cases, the "allow public entries" is really limited to whether the user can create public Address Book entries or not. However, I think the concept is more granular than that.

    I want users to be able to create public Address Book Entries, Notes, and Documents - but for the vast majority of users, I do not want them creating public Column Setups / Search Catalogs / Email Templates / etc. Often times, users will create these items without realizing what the implications are and it leads to clutter across the program. Certain users (department heads, admins, power users,…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  4. Clean up user objects without deleting the User ID

    When a user stops working for a company, most people will delete that user ID from the database. However, by doing so, the user is no longer available and stops showing up in various search functions (Case Owner, Opportunity Team Leader, etc.). For historical reference purposes, it would be good to keep the User ID around. However, doing this results in the various Column Setup / Favorite List / Coloring Rules / Search Catalog / Dashboard / Email Template / Action Plan screens becoming cluttered with data of users that no longer work for the company.

    There needs to be…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  5. Coloring Rules Dialog

    The Coloring Rules setup dialog needs to be similar in functionality to the Column Setup / Search Catalog dialog screens. It needs the "Show All" / "Show Mine" toggle and the Full Access / Read Access values need to be visible in the grid. It's impossible to quickly determine details about a Coloring Rule setup without drilling down into each rule separately.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  6. Formula UDF - using a field with the same name as a system field

    If you have a UDF with the same name as a system field, then try to use it in a Formula field, the UDF won't be used if it is in the root folder - it will always use the system field.

    I suggest either of 2 possible changes:

    Firstly, change the way fields are referenced in formulas to use a unique identifier. That way the correct field always gets used.

    Or secondly, adding a duplicate check when creating UDFs to at least make the user aware that creating a matching field can cause issues.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  7. Key Fields Grid

    In the Web Access Administrator, the Key Fields maintenance grid only shows 2 columns:

    Name
    Requested By

    This can be easily expanded to also display:

    Full Access
    Read Access
    Description
    Applies to Modules
    Creation Date
    Created By
    Currently, it's impossible to quickly review this information. You have to manually drill-down into each list. With more than 60 lists defined in the database, doing any meaningful analysis is next to impossible.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  8. User Setup Grid Sorting

    Currently, when the user setup grid in the Web Administrator module is sorted on any column other than "user id" the sort is lost when returning to the grid after editing a user's details. The grid needs to retain the sort order between user edit operations.

    It's incredibly slow and painful to continue to have to re-sort the grid when making many changes to a specific group / department of users.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  9. User / Group Security Matrix Update

    With the advent of large-screen monitors, the access rights UI for Users and Security Groups should be updated to take advantage of the full width of the screen.

    All permissions, privileges, and roles should be visible without having to scroll. It would make reviewing permissions much faster and accurate.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  10. All All / Remove All Buttons on User Setup

    When administering a user in the Web Access Administrator, there is no way to quickly remove a user from all of their Group / Team memberships. Each box must be clicked (which triggers a postback) and then the Remove button must be clicked to execute the operation.

    In the Windows Administrator, the list item could be double-clicked to remove it - or ALT+R could be used for even faster performance. The Web Access Administrator is too inefficient when working with a large number of users on a large number of Groups / Teams.

    Since ALT+R would not work in a…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  11. Multi-Group Ownership Expansion

    In the Address Book, the Full Access and Read Access fields support multiple Security Groups. This needs to be extended to:

    UDF Setups
    Column Setups
    Search Catalogs
    Notes

    This would significantly decrease Security Group complexity where users from multiple departments require access to the same UDF.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow configurable mandatory fields for user creation

    When creating a new Maximizer User, it should be possible to define which fields are mandatory on a per-database basis, similar to how mandatory system fields can be configured for the Address Book, Opportunity, and Customer Service modules.

    This would allow administrators to define certain fields (like First Name) that must be filled in prior to the creation of a new User. Currently, only User ID and Last Name are mandatory for on-premise databases.

    This needs to be expanded to increase the accuracy of data available for each User and simultaneously allows for greater personalization options in the application.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add custom sort order to Key Fields selector drop-down

    Add a "Move Up" and "Move Down" feature to the Key Fields listing in Administrator, thus allowing a custom sort order to the Key Fields selector drop-down. Similar to what can be done for table field items.
    In Key Fields an ordering can be forced by numbering or lettering, but this becomes untidy, and therefore a user experience is requested that is similar to table field items.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  14. Group / Team Descriptions

    Often times Security Groups and Sales Teams are created by one regime and inherited by the next one. As such, the intended purpose for many Groups / Teams is lost over time. It would nice to support some of the attributes found in the UDF Setup functionality:


    • Description

    • Requested By

    This is in addition to the other Group / Team stuff that has already been requested. :)

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  15. Address Book Permission Refinement

    Currently, user / group permissions control access to the "Address Book" as a single entity. However, there are frequently cases where the permissions need to be more granular than this.

    For example, a customer has no use for the concept of "Individuals" and they want to prevent users from inadvertently adding this kind of record into the database. Currently, the only front-end solution is to deploy a MenuBuilder customization which removes all references to "Individuals" from the various record creation menus.

    Ideally, this should be handled by separating the user / group permissions into buckets for:


    • Company

    • Individual

    • Contact

    Business…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  16. Default Entry Management

    This needs to be added to the Administrator module. There is currently no way for an administrator to review the Default Entries for the users.

    In the Windows Access application, an option to "View Default Entries" existed for each of the modules, but this does not exist in the Web Access application, nor is there any way for the Administrator to review and alter Default Entries without being logged into Web Access as the user in question.

    In an on-premise deployment, this can be easily done via SSMS, but that's obviously not an option in CRM Live.

    We need to…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  17. Clear user permissions

    Nearly every Maximizer database I've seen does not correctly implement group-level permissions. Instead, permissions are a mixture of user-level permissions and group-level permissions. Trying to clear all user-level permissions to go with a 100% group-based security structure is a nightmare because each user has to have their user-level permissions manually un-checked. There is no easy way to quickly clear all user-level permissions.

    In an on-premise world, a SQL trace could be executed and reverse engineered to clear these values directly in the database, but the user tables are typically the most complex to interact with manually and updating the columns…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  18. CSV Import

    The Contact # field isn’t available in a column layout so it’s not possible to export a list of existing Contacts to then match to your new CSV data to be imported (using VLOOKUP for eg) to provide the Contact Number field for importing which is required for matching along with the Identification field.
    The Import functionality is lacking in a few other aspects as well which is a pain in real-world usage as they really make life difficult :
    - Table type UDF’s use to be able to be populated by the import process, but this no longer happens.…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  19. Global Edit shortfalls

    The Opp Stage & Status are unavailable in Global Edit, nor in the CSV Import function

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  20. use email as username

    Have the ability to use the email address as the username.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Usability - User Experience  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 11 12
  • Don't see your idea?

Feedback and Knowledge Base