Hello Sugar lovers, In some of our projects, certain objects have MANY relationships. This results in sometimes over 15 subpanels on the detail page. While users can sort the panels (have to actually, since you can't force an order system-wide), it becomes hardly usable after some time. Have you already encountered this issue? Have you envisaged grouping the subpanels in tabs? Ex on a account page: Relationships: contacts, subsidiary companies, etc. Contracts: opportunities, contracts, subscriptions... Support: cases, bugs etc. Activity: meetings, notes, emails, tasks... Marketing: campaigns, surveys... That could make the interface less cluttered. Before we dive into a Proof of Concept, we wnated to check with the community for experiences and hints. And maybe info from the SuagrCRM people on future changes in that direction that would make this (potentially heavy) development useless in a few months :) Thanks all! Damien

Improve sub panel management in detail page via tabs?

Hello Sugar lovers,
In some of our projects, certain objects have MANY relationships. This results in sometimes over 15 subpanels on the detail page. While users can sort the panels (have to actually, since you can't force an order system-wide), it becomes hardly usable after some time.

Have you already encountered this issue? Have you envisaged grouping the subpanels in tabs?

Ex on a account page:

Relationships: contacts, subsidiary companies, etc.
Contracts: opportunities, contracts, subscriptions...
Support: cases, bugs etc.
Activity: meetings, notes, emails, tasks...
Marketing: campaigns, surveys...

That could make the interface less cluttered.

Before we dive into a Proof of Concept, we wnated to check with the community for experiences and hints. And maybe info from the SuagrCRM people on future changes in that direction that would make this (potentially heavy) development useless in a few months :)

Thanks all!

Damien

Parents

0 Björn Canales Pfisterer over 1 year ago

Hi Damien Pochon,

in some projects it helped to discuss with the teams ( sales, service, marketing, support, CEO, leaders, etc) which modules are interesting and which not. This mostly ends in we could define visible modules per roles that shrinked the list of submodules to the modules that are realy needed. The rest have been taken out via role access.

Bests

Björn
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Björn Canales Pfisterer over 1 year ago

Hi Damien Pochon,

in some projects it helped to discuss with the teams ( sales, service, marketing, support, CEO, leaders, etc) which modules are interesting and which not. This mostly ends in we could define visible modules per roles that shrinked the list of submodules to the modules that are realy needed. The rest have been taken out via role access.

Bests

Björn
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Damien Pochon over 1 year ago in reply to Björn Canales Pfisterer

Hi Björn Canales Pfisterer,

Thanks for your input! We tried that, and in many cases it works because not everyone needs all information.

However there are many cases in which users *need* a full 360° view that is more detailed than what graph dashlets could give. And even with a dozen subpanels, the interface quickly feels cluttered and disorganised.

Did you try other things?

BR,

Damien

Damien Pochon

CRM & Digital consultant @ ITS4U Group
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel