Thread Details
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 368 subscribers
  • Views 954 views
  • Users 0 members are here
Forum Actions

What are your Sugar 7 Record View customization use cases?

Matt Marum

Hey Sugar 7 Developers!

I wanted to make sure the community is aware of our planned refactor of the Sugar 7 Record view in Sugar 7.8.  The main point of the refactor is to move the Record view header pane out of the scrollable DIV that it is inside today.

For some more of the technical details, check out the related post on the Sugar Developer blog.

Sugar Engineering needs to make sure we understand all of your Record view customization use cases so that we can be prepared to make you prepared.

I've collected some of the common Record view customization use cases that I know about below.  

  1. Adding custom field validation (such as validation tasks) to Record view (Example from Sugar Developer Guide)

  2. Adding buttons to Record view including overriding view controller to implement a custom action (Example from Sugar Developer Guide)

  3. Adding event listeners to Record context or layout (Example from Sugar Developer Guide)

  4. Adding metadata customizations such as new custom fields, panels, or Sugar Logic dependencies (Via Studio, Extensions framework, or custom directory)

  5. Adding custom views to Record layout (Example from Sugar Developer Blog)

Are we missing your use case?  Please post your thoughts into this Sugar Community thread or send them to developers@sugarcrm.com. We will also have Sugar Engineers on hand to discuss this topic at UnCon at SugarCon.

  • 0
    Hello,
    We use it for more:
    • Specific dependencies that can not be mapped to the standard dependencies (e.g. dependend on user,role, user action or dependend on data (separate api call))
    • Buttons to open some other views
    • Icons or fields in header pane (e.g. Facebook-icon, title field etc.)
    • Addresscheck on the fly
    • etc.
    Affect the change also create view?
    Is there an elegant way to add a custom js to create and record-view without copying it in both?
  • 0
    Hi,

    We've made quite a few changes - they may be covered by the points above, but to clarify a couple:

    • We create new buttons in metadata but call a function after calling this._super('_render') to propagate the objects with the returned values from an API call.
    thanks





  • 0
    Hi Matthew,

    On of our use case is nesting recordviews. 
    We have a one to one relationship between module1 and module2.
    We've added a button alongside dataview and activity stream buttons in the filterpanel for the related module(s) when clicked we pull the recordview from the related module. we also map values using the context.

    View attached image for reference
  • 0
    Hi.
    It would be great to get WYSIWYG field available through studio.

  • 0
    actually you can add a wysiwyg editor via code, on the record view just add 
    'type' => 'htmleditable_tinymce',