Sugar Fall ‘17 (7.10) Overview for Sugar Developers

Alexandre Tremblay asked during the webinar:

any potential pitfalls when customizing the emails module. I saw it's not available inside studio. Any other limitations with out-of-the-box features like adv. Workflow?

Answer:
Can you provide some more details on what you're planning to customize?  

Some general advice:
The record view and list view are now in Sidecar, so they can be customized the same as any other view.  However, there are some caveats:  

• The recipients fields (to/cc/bcc), which are collection fields, shouldn't be added to the list view due to performance issues.
• The OOTB fields (from/to/cc/bcc/email body etc) shouldn't be removed from the record view because they are required in order for the email to be sent.

Steven Parsley presented a session on UnCon on the Do's and Don'ts for Using Email APIs.  You can get the slides here.

Hi Lauren,

In my case, we have few big clients with specific use cases regarding emails.

Case management (Inbound Emails)
Group emails round-robin assignment (Inbound Emails)
Email Signatures
Email Tags
Custom ACL

I do understand that the email module is in a special case and implementations that follow usual best practices can still encounter design problems with it. On a high-level, it will look like this.

Standart Dashlets, list, report, etc
- That should be all good and bazillion times better than the old UI. Does sugar plan to develop specific dashlets for further improving the UX?

Metadata Extension Framework
- Extra fields or relationships will be needed, the module is not available in Studio but is the metadata extension framework a viable option? The special email table structure was not allowing it before.

Custom ACL rules (Extension Framework)
- Visibility rules will also need to be implemented, is the Email ACL can be extended like other modules?

Roadmap on Advance Workflow
- The Email module is still not available in the adv workflow. Is this in the roadmap for a near future?

Any potential issues with existing workflows?

Thanks for the performance concern, I do understand that list displayed information will need to be optimised for systems containing a huge quantity of emails.

Alexandre Tremblay I tracked down some answer for you:

Standart Dashlets, list, report, etc
- That should be all good and bazillion times better than the old UI. Does sugar plan to develop specific dashlets for further improving the UX?

It’s on the backlog to provide a couple of OOTB dashlets, currently planned for Summer '18 (subject to change). If you have specific requests, please email products@sugarcrm.com.

Metadata Extension Framework
- Extra fields or relationships will be needed, the module is not available in Studio but is the metadata extension framework a viable option? The special email table structure was not allowing it before.

Additional columns can be added to the Emails table using the extension framework. There is currently no extension endpoint for customizing the emails_text, emails_beans, and emails_email_addr_rel tables.

Custom ACL rules (Extension Framework)
- Visibility rules will also need to be implemented, is the Email ACL can be extended like other modules?

You can extend visibility and ACL's the same as any other module.  Be careful not to create conflicts with the rules that are defined in the OOTB strategies.

Roadmap on Advance Workflow
- The Email module is still not available in the adv workflow. Is this in the roadmap for a near future?

Can you email this question to products@sugarcrm.com?

Alexandre Tremblay I tracked down some answer for you:

Standart Dashlets, list, report, etc
- That should be all good and bazillion times better than the old UI. Does sugar plan to develop specific dashlets for further improving the UX?

It’s on the backlog to provide a couple of OOTB dashlets, currently planned for Summer '18 (subject to change). If you have specific requests, please email products@sugarcrm.com.

Metadata Extension Framework
- Extra fields or relationships will be needed, the module is not available in Studio but is the metadata extension framework a viable option? The special email table structure was not allowing it before.

Additional columns can be added to the Emails table using the extension framework. There is currently no extension endpoint for customizing the emails_text, emails_beans, and emails_email_addr_rel tables.

Custom ACL rules (Extension Framework)
- Visibility rules will also need to be implemented, is the Email ACL can be extended like other modules?

You can extend visibility and ACL's the same as any other module.  Be careful not to create conflicts with the rules that are defined in the OOTB strategies.

Roadmap on Advance Workflow
- The Email module is still not available in the adv workflow. Is this in the roadmap for a near future?

Can you email this question to products@sugarcrm.com?