Sugar Developer Webinar - Fall '19 (9.2.0)

Slides: Sugar Developer Webinar - Fall ‘19 (9.2.0)

Agenda

  • Portal updates and improvements
  • Business Centers module added to Sugar Sell
  • Javascript Library and Bootstrap component updates
  • Customizing the Portal
  • Addressing common questions about new SugarCRM product lines
  • More best practices for developing for the Cloud
Michael Shaheen
Parents

  • Hello Everyone,

    I would like to add a clarification about enabling new modules on the new portal. If you attempt to do that, please make sure your new module's portal layouts (list.php and record.php) start from a portal module and not from a base module. As an example, you could start from Case's portal layouts (modules/Cases/clients/portal/views/record/record.php and modules/Cases/clients/portal/views/list/list.php) and manually tweak everything that is required (eg: the module name and the field changes).

    This is to make sure you will not accidentally add fields that make sense only to the base application UI to your portal.

    Specifically, it was reported to us that if the Teams field is added to the portal layout, it prevents the loading of the record view. Teams is not a concept that currently applies to the portal, and therefore it should not be added to any portal module.

    Hope this helps you further smooth your customisations attempts.

    Cheers

Comment

  • Hello Everyone,

    I would like to add a clarification about enabling new modules on the new portal. If you attempt to do that, please make sure your new module's portal layouts (list.php and record.php) start from a portal module and not from a base module. As an example, you could start from Case's portal layouts (modules/Cases/clients/portal/views/record/record.php and modules/Cases/clients/portal/views/list/list.php) and manually tweak everything that is required (eg: the module name and the field changes).

    This is to make sure you will not accidentally add fields that make sense only to the base application UI to your portal.

    Specifically, it was reported to us that if the Teams field is added to the portal layout, it prevents the loading of the record view. Teams is not a concept that currently applies to the portal, and therefore it should not be added to any portal module.

    Hope this helps you further smooth your customisations attempts.

    Cheers

Children
No Data