It would be great to avoid phone calls from users, to log off all users from slx with a short message.

I do not know if this is possible in web but it would be great to let the users know that you are doing something in the system which requires them to log off.

Or post some global message which can be seen by all users.

Something like this!!

With the release of Windows2008 R2 and the big push for 64 bit desktops/laptops it's time we have an option in the install that would give us 64 bit versions of all the SalesLogix applications. 

This does not have to be a "mixed" (32/64 bit) on a given system but should allow us to install either the 64 bit or the 32 bit on a given platform. What would be really nice is that it does an auto-discovery (this should be very easy) if the platform is 32 or 64 bit and "default" to the correct one. 

I would like to see Inactive Contacts appear greyed out in the Account View Contact Tab. 

This idea would work great with Brain's Tool for managing groups or at least add a "last access date".

One of the most powerful aspects of SalesLogix as a CRM is the ability to create your own groups and filter data. A customer suggested to me recently that it would be nice to set the colour of those group tabs that run along the top. Users can then effectively "group" their groups and assign a colour to their grouped groups.

E.g

Opportunity Entity

 Closed Won Opportunity Group

  Closed-Won Opps This Month

  Closed-Won Opps Last Month

  Closed Won Opps This Year

  My Closed Won Opps

  Add On Closed Won Opps

 Closed Lost Opportunity Group

  Closed-Lost Opps This Month

  Closed-Lost Opps Last Month

  Closed Lost Opps This Year

  My Closed Lost Opps

  Add On Closed Lost Opps

 Ongoing Opportunities 

  My Open Opportunities
  Opportunities Not Contacted in 28 Days

You get the idea. Being able to group the groups and assign colours would really build on SalesLogix's already fantastic group functionality and will help those users that have their groups set up like the attached below.

Adding this functionality for both the web and LAN would be fantastic as we have a few big SalesLogix clients that use their groups religiously. This will make the system considerably more attractive for future upgrades to them and will make life easier for those that utilise SalesLogix's group functionality properly.

This idea comes from Brian Jonas' post in another forum: 

Group Last Accessed Date
Many customers have upwards of 5,00 to 10,000 account/contact/opportunity groups. I just did a count and found that we (The Seattle Times Co) have 2,200 groups, with 1,470 of them being account groups. Group creation gets out of control due to users creating lists but seldom taking the time to delete old groups. The administrators can purge some lists but for most groups we don’t know what can be safely deleted other than unshared lists created by retired users, and the ones the Administrators created.

In our implementation (v7.0.1), one serious impact of having so many groups is demonstrated whenever I log into the client as the Administrator. Since that login sees all the groups, it can take up to 5 minutes to open up to the list view.  I can’t imagine how long it takes other customers their groups!

In the CAB meeting I suggested that a field be added to the Architect that is a time stamp of the last date the group was accessed. That would really help us purge out the dead groups! There was a lot of vocal support to that suggestion – I hope it is possible for Sage  to create.

Great idea Brian!

The replace data maintenance function was very useful in the LAN client for modifying a lot of data at once based on groups. The function is missing in the WEB client.

Thank you.

Regards,
Marco

Not sure how possible or likely this is, however here goes.

With the advent of the job server and having just been through a load balanced install utilising an app server for shared components, It would be really great to have a configurator within AA, within this configurator you would state where the SLXServer is located, where the job server is located, where the cache server is located, where the messaging server is located in addition whether you want to use windows authentication or slx authentication.

Plumb in all this information and all the relevant *.config files are deployed with the correct settings for the relevant servers and authentication methods.

Hacking around in config files with limited or no documentation for specific scenarios in this day and age is archaic.

Please provide us with some sort of mechanism to set up the configurations which are deployed to the relevant servers instead of having to mess around in config files.

Regards

Craig

I don't care at all for the existing customer portal implementation. It never seems to be what my customers want. Instead of it being this separate application, they want it to be more "embeddable" into other existing customer websites they already have.

Having clear defined integration points for the customer portal and embeddable parts that could be used in other websites could make the customer portal far more attractive to support organizations. At minimum, having the base customer portal use themes or skins that could easily change it's look & feel would make it easier to at least look like the existing customer websites even if they are two separate websites. It would really be cool to even have the screens that make up the customer portal be reusable UserControls (or simple pages that one could load into frames).

Having the customer portal look like "SalesLogix" just isn't something that most companies want.

It'd be nice if the default message when you navigate away from a record in SalesLogix Web gave you the ability to save the record ie if the message said "There are unsaved changes on this page, press yes to save the changes and continue, or no to return to the {account/contact/opportunity} without saving changes"