Before you crucify me, I'm not advocating writing the SLXMobile in native iPad, iPhone, et al languages....

What I'm suggesting (the idea) is that the SLXMobile Icon needs to appear in my list \ pages of iconized Apps on my mobile device.....click\touch the app and it automagically launches the supported browser, goes to the stored settings URL, etc.

We need to get beyond the open the browser, type in a URL, type in a UserName password login info stuff....KISS for the user, it's what they're used to (LinkedIn, FaceBook, et al), and it's much easier when on a train to downtown. One Thumb operation to get to the SLXMobile App Icon, click on it, presented with your Account list (or what have you).

AND

You can download the app and Search for it in the app store (did someone say MARKETING?). Reviews, hits, buzz, etc.

My customers tell me they want to spend less time creating unique ways to send files from the sales library, or specific attachments. When they are in their mail client (Outlook) web users need to quickly find library documents and attachments (to accounts, tickets, etc) and include one or more in an email. 

The web client actually took part of this feature away, it appears. Users of the web client cannot locate library documents to include in an email. This is an important job to get done, that competitors have been getting done for a long time. 

I think a long look at how customers do their work would help greatly to reinforce the need expressed in this idea, as well as the best design to make the experience of getting this job the best it can be.

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!!

Due to multiple imports and the nature of our business, we have many, many duplicate contacts in our database.  Unfortunately, many have been entered with generic names - General Manger, etc. rather than given names.  It is a real pain to have to create a contact group for each account then merge through list view.  No, Parabus does not work for us in this area either.

What we would love is to be able to click on the Contact tabs while in the account screen, highlight two (or more) duplicates, and merge them right there.

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!

Please make deployments specific to projects. We have started using the debug button in AA to build, deploy, and open our default deployments. It is very handy. However, when sharing a database with other developers and uing local project files we cannot use the debug button as our deploy configurations are different. There currently can only be one default deployment per database.

Thank you!

Timmus Agersea

Customer Systems, Inc.

Am I the only one tired of clicking through the "External Assembly Reference" dialog when adding business rules?  Or just the only one using external assemblies?

Here is what I would like:

* a set of attributes: [OnBeforeInsert], [OnBeforeUpdate], [BusinessRule]

* maybe some parameter for the attributes to be able to define post and pre steps: [OnBeforeInsert(Order=Post)]

* decorate the methods in the assembly with those attributes

* point AA to the assembly.  Have it automatically link the business rules and entity events.

* Bonus points:

  + pull the XMLDOC and put it as description on the business rules.

  + "prune" missing methods (the ones that are still defined in AA but got removed from the assembly)

It should also be possible to create such a tool externally, if anyone is interested in an open source (or commercial) endeavor.

This might not be a big deal in a production environment, but in development, you might have a couple different projects for the same database, or in some cases, you might have various projects for different databases all on the same server. It would be nice if the build path could be designated for each project, rather than always using the same path for each. 

Becki Blackburn

This deficiency existed in the LAN as well, but we were occasionally able to work around it by using the standard Lookup control against the UserInfo table.

The User Lookup control groups the SLX Users according the their SLX License type. This is of limited, if any, use for data entry purposes in anything other than an Administrative application. More often we find that it confuses the end-users that are simply trying to choose an Account Manager or some such property value.

Desired User Groupings:

• Group Users by the SLX built-in groups  (Teams, Departments, Roles)
• Group by a designated property (ex. User.Title, or User.<YourCustomFieldHere>
• Group by an expression (complex expression to all of for multiple property combinations, concatenations, etc.)
• Group by primary address field(s) - Country, State/Province, City)

Configurable - Important:

It is very important that we have ability to define (developer designation, not end-user) which user groupings we wish to make available for each UserLookup control we place on a form (i.e.. not a global settings, needs to be definable for each time we use the control).

A few more user fields:

Consider allowing the user control to define what the displayed information will be such that we could show not only the user name, but 2-3 other information fields  - things like Title, SupervisorName, Phone,City, State, etc. serve to help the end-user clarify that they are, in fact, selecting the correct user.

Also Desirable:

It may also be useful if we could incorporate a bit of the standard Lookup Control functionality where (optionally) we could show the user list in a grid.

Maybe some thing that looks pretty much like the standard lookup control, but with ability to not only filter on the lookup results grid columns (as standard lookup does), but also filter by the user groupings mentioned above.

Submitted for Lincoln Financial by John Gariepy:

Make the Web Client login error messages more descriptive.  For example:  "The username or password entered is invalid, please try again or contact your SLX Administrator."

The lookup control is really limited and needs to be expanded to allow multiple criteria selection.

I created a view and tried to tie the lookup control to hit the view but unfortunately it didn't work. Sage needs to have a new expanded lookup control.

(7.5.x web) 

When the lookup dialog is invoked from a lookup control such as the Contact field on the Ticket Detail screen users can only search by a single field.

What a lot of our customers with larger data sets want is the ability to specify search criteria on multiple fields - as is provided in the "MainView Lookup" accessed by right clicking the NavBar.

Customers upgrading from the legacy web platform miss the "advanced lookup" functionality.

Has anyone overcome this?  If not can it be included in SP3 / v8? 

The ability for marketers or sales persons to understand not just what conversations are going on about their products and services, but where the conversations are going on. The social customer is no longer allowing us to sell to them, they are buyers in control. Twitter is not the only place these conversations are taking place, so this solution would have to allow for any social outlet to be plugged in, to use a SLX term.

BTW, here's what our competition is doing

Microsoft CRM Social Accelerator

I thought I had sent this already but I guess I forgot to hit Post, so here goes - sorry I am cutting it a bit short because I don't feel like retyping it all...

I would like a "Repair" option in App Architect that would rebuild the database schema based on the project's metadata.  

Key advantages:

* avoid need to separately bundle schema changes when shipping a web customization

* ease distributed development scenario (in case each developer have their database)

* serve as an "integrity check" of the project's metadata (the problem is that if there is a field missing in the database you will not find out about it until visiting the page where SalesLogix tries to access that field)

Thoughts:

* How to handle indexes and joindata?  

* Can picklists be handled in the same way (at least creating empty picklists where needed) - this might require associating the field with a picklist when editing an entity

* This should be interactive so that the user has a chance to review the changes before applying 

Would be useful to be able to sort the Project Workspaces grid based on any column.

Also, please add columns for CreateDate and ModifyDate so we can sort on those.

I suppose an ability to change the column layout order might be nice as well while I'm asking for other changes on this grid.

This feature request came from Kevin Flynn at SyncSite: Recently, while troubleshooting an HTTP 401 error during a push to the BES, we found that the BES had "Push Authentication" setting enabled. Disabling this does constitute a bit of a security hole; if possible, Mobile should offer a way to send authentication to the BES when it does a push request, so that this setting can remain enabled.

For any discussion of this issue, please contact Kevin Flynn at SyncSite.

Many of our customers schedule timeless phonecalls in SalesLogix, and have them set to rollover automatically. Therefore, over time, if they haven't been completing them, there can be dozens of these timeless activities for a given day.

The older pre-7.5x Intellisync engine allows you to granularize which appointments you want to pass over to Outlook. You have the option of not syncing timeless activities. With the newer 7.5x Intellisync engine, ALL appointments are synced with Outlook. We have numerous customers who do not want it to work this way. We have one customer who specifically turned off Advanced Outlook Integration due to the timeless phone calls showing up in Outlook, which in many cases end up crowding up their Outlook day view to where they can't even see the timed section. Now that this customer has upgraded to 7.52, they are seeing these phone calls passed over to Outlook via Intellisync, and the users are complaining. I am requesting that Sage works with Nokia to add back in a way to filter out these timeless activities. I realize that Intellisync is not controlled by Sage, and therefore, it may not be doable, but I am putting in this request just the same.

I was told by support that ExchangeLink also does not have any timeless filtering. It would be nice to have this there as well, and might be easier, since ExchangeLink is a Sage controlled application.

Thanks!

Becki Blackburn