These 2 free Sugar 7 plugins are going to make history

When it comes to CRM, sales professionals know where their customer relationships stand when they have clear insight into past events. The best CRM systems present a historical audit trail that is simple for end users to find – and even easier for them to understand. Here are two plugin tools that make it painless for Sugar users to get a quick glimpse into those critical history items.

Worklog Field

Jerry Clark has resurrected Jon Whitcraft’s first Worklog field as a Sugar 7-friendly plugin available for download from SugarForge. The Worklog field can be used in place of a standard Sugar textarea field to insert a widget where users can log comments and events. Each entry that is made via the widget will be displayed as a line item in an ordered list. Users can see who created each entry and when they posted it.

The Worklog field is Studio-enabled so the administrator of an instance with the package installed can create a “worklog” type field and place it on any Sidecar or BWC module’s record view without assistance from a developer.

The latest Worklog Field plugin can be downloaded from SugarForge or you can Fork it on Github to configure your own version.

Historical Summary

By Grabthar's hammer, you shall have a complete Historical Summary!

Out of the box, Sugar’s Sidecar modules feature a handy “Historical Summary” option that does an excellent job of aggregating activity records (emails, notes, calls, and meetings) and displaying them in a sortable and preview-able list view. But users still need to click on individual preview buttons for a glimpse into each line item.

The extended Historical Summary plugin, also developed by Jerry Clark, mimics the all-encompassing view of activities from the ”View History” option that was available in Sugar 6.x and earlier versions. The main benefit of the enhanced tool is the ability to scroll through a slide-down drawer that displays the contents of every email, note, call, and meeting that is related to the parent record. This saves the user time and clicks when they need to quickly scan a record’s history.

The Historical Summary plugin also makes it easier for users to search for key words and phrases to quickly jump to the history item they need. A simple Ctrl+F will leverage the browser’s ability to find the relevant activity record without the user having to click into each item’s preview.

The Historical Summary plugin can also be downloaded from SugarForge or you can Fork it on Github to configure your own version.

  • Hi Jerry ,

    I have tried with that code still it is getting the same result 

    {"1564426550":{"tsp":1564426550,"usr":"5efd5a12-4bdd-11e9-8c0a-00155d71c603","msg":"this is for test"}

  • Hi Ash,

    Unfortunately, there's no easy answer to making this happen. The worklog field does not support email templates as noted in the readme. If you are an on-site customer, you should be able to modify include/workflow/action_utils.php in the process_action_update function to change:

    if (in_array($focus->field_defs[$field]['type'], array('double', 'decimal','currency', 'float')))
        $new_value = (float)unformat_number($new_value);
    } elseif ($focus->field_defs[$field]['type'] === 'multienum') {
        $new_value = workflow_convert_multienum_value($new_value);
    to be something like:

    if (in_array($focus->field_defs[$field]['type'], array('double', 'decimal','currency', 'float')))
        $new_value = (float)unformat_number($new_value);
    } elseif ($focus->field_defs[$field]['type'] === 'multienum') {
        $new_value = workflow_convert_multienum_value($new_value);
    } elseif ($focus->field_defs[$field]['type'] === 'worklog') {
        $new_value = SugarFieldWorklogHelpers::decodeJsonValue($new_value));
    *this is not tested
    As Sugar now contains the comment log field, I would strongly suggest migrating your existing field to use the comment log field as it will continue to have support and receive features. You can migrate existing fields using the documentation found here:
  • Hi Ash,

    I am not sure but you might need to override email template bean to enable parsing for worklog field separately.

    They are using parse_template_bean function to parse the bean and their fields. You can override the same function and add a piece of code to parse the worklog field type.

    Let us know if this helps.



  • How to use this worklog field in workflows .

    i added this field in email alert template and the result is getting like this 

    {"1564426550":{"tsp":1564426550,"usr":"5efd5a12-4bdd-11e9-8c0a-00155d71c603","msg":"this is for test"}.

    but the original data is 

    i want to show original data in emails so how to do that??hats

  • Comment originally made by Jerry.

    Currently no, however, I will add this as a feature request.