Can you please provide example code to use a parser to update the related_fields? It's a lot of work to update N instances of SugarCRM where one has to download the record.php for Quotes, create a custom version, and upload it via module loader.

From talking with a few of the engineers, there is not a simple way to do this customization. One option for you is to investigate how to use SidecarListLayoutMetaDataParser with a custom action/endpoint. upgrade/scripts/post/7_ConvertPopupListView.php has some sample usage.

Will there be a migration path for the next OP release for Elasticsearch? Until now, there was always a release which supported both the old and the new version (e.g. 7.8 with ES 1.4.4 and 1.7.5)

Answer:

The upgrade to Elasticseach5.4 has breaking changes. Mappings in ES5.4 are different than ES1.7.5; therefore, we could not support both versions of Elasticsearch for the Sugar 7.10 release and that is also the case with the next OP release.

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.

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?