No similar topics found.
Free, open source customer relationship management platform built in Ruby on Rails. Share your input!
Supporting cases such as:
- List all contacts created between July 2010 and November 2011 that are male, under 40 and have no account associated with them
- List all all accounts that are tagged as "edu", have an "edu type" of "secondary school", order results by most recently updated
The ability to free text search within those results also desirable.
I like the approach taken by the brilliant Mingle product. That could be a jumping off point for us as we design.
Well, we've got a huge distance into this now.
- You can create very powerful filters on any field and through to the fields on associated records (e.g. show contacts that were created this week AND that are associated with an account that has a name containing "Goldman")
- You can save advanced searches as named "lists" so you can easily get back to them later.
Two complementary features (which I'll make as separate topics) are desired to come after this
- Users can view lists of results in a table format with configurable columns
- When users save a "list" the save includes their various view preferences
We would like to see fuller support for applications that require API access to FFCRM. This would probably mean extending the permissions system to handle Applications as well as Users. The goal of FFCRM itself is to stay lightweight, customizable and extensible, so integrating other applications via the API is really one of the most important things to get right.
Support through the web configuration of custom fields for contacts, accounts, campaigns etc.
This is largely completed in terms of functionality. However, it is still in progress because...
- improvements to the UI design for the admin screens are still under discussion
- A few bugs may yet be lurking so additional QA testing and bug reporting is appreciated
- We need to write up how this feature works and/or provide a screen cast
Latest UI mockup ideas proposed by Mike Dvorkin (feedback welcome)
A few comments:
- Instead of horizontal buttons I suggest to show the sidebar and create a menu widget. We can use slightly different colors/shapes to distinguish the menu widget from static "Recent Items" panel.
- There is no explicit notion or extra step of creating a Field Group. User is entirely focused on creating custom field and nothing else distracts her from this goal.
- Within [Create Custom Field] form user can a) create or select a group (which is required) and b) create a select group tag (optional). Implementation might be a bit tricky since we want to reload available tags when selecting a group, but I think it's doable.
- Going forward I think it makes sense to use autocomplete control instead of standard dropdown for "create or select" fields. As I recall there is a fork that does that for Account field in [Create Contact].
- Listing custom fields is pretty much self-explanatory. There are edit/delete controls shown on mouseover for individual fields and groups. Editing a group invokes a short form with two fields: Group and Group Tag.
- Expanding/collapsing groups (i.e. clicking on [-] or [+] icon next to group name) is nice to have but not required.
When converting a Lead to an Account, any information entered in the "Company" textbox on the lead should be copied as the default Account name.
I agree. Our most common use case is that a lead signs up via our web form. The we form captures a variety of detail including contact, account detail, interests and so on. We then do some follow up and we may subsequently wish to convert this material into a contact and/or account. But we don't wish to lose any of the information captured during the lead process.... not just the account name.
If a task is mistakenly marked as complete, there is no (apparent) way to restore it to incomplete. Suggestion: display the checkbox for completed tasks also, allowing it to be cleared if mistakenly ticked.
Customer support service by UserEcho