Sugar Automate

Overview

Sugar Automate lets administrators create easy-to-follow, visual business processes for users to complete against their Sugar records. Each Smart Guide is an end-to-end process that is split into color-coded stages, and each stage contains one or more call, meeting, or task activities that the user can complete with optional dependencies and actions on related records. This guide covers how to start using Sugar Automate as an administrator.

Note: Sugar Automate was incorporated in version 12.3 of Sugar Sell and Sugar Serve and 13.0 for Sugar Enterprise. For Sugar versions 12.2 or earlier, where Sugar Automate was available as an installable connector, please refer to the separate Sugar Automate documentation.

For users to view Sugar Automate Smart Guides, they must be assigned a Sugar Automate license. For more information please refer to the License Management page. For information on using Sugar Automate after an administrator sets up a Smart Guide, please refer to the Sugar Automate page in the Application Guide.

Prerequisites

• Sugar Automate is included with Sugar Sell Premier and Enterprise+, and it enables smart guides. Sugar Automate can also be purchased as an add-on for Sugar Sell Advanced, Serve, and Enterprise. Please contact your Sugar partner or representative to learn more.
  • If you purchased Sell Premier, users who are assigned the Sell Premier license type are granted access to smart guides.
  • If you purchased Enterprise+, you must assign the Enterprise and Sugar Automate license types to the users so that they have access to smart guides.
  • If you purchased Sugar Automate as an add-on for Sugar Sell Advanced, Serve, or Enterprise, you must assign the Sugar Automate license type and a CRM license type to users who should have access.

Understanding Smart Guides

A Smart Guide is a set of successive stages through which most customers proceed as they participate in the decision-making process. A traditional Smart Guide is often characterized by the stages of awareness, consideration, purchase, and loyalty. Depending on your business needs, you may have more or fewer stages or even several variations of the Smart Guide for different types of consumers. With Sugar Automate, administrators have the freedom to create multiple, unique Smart Guides specific to their business processes.

The Smart Guide in Sugar is presented in an easy-to-follow visual format, comprising a progression of stages and activities within those stages.

Smart Guide performance is measured in terms of progress and momentum. For more information on how these measurements are calculated and where to see them, please refer to the Understanding Progress and Momentum section of this page.

Before creating a Smart Guide template, we recommend planning the Smart Guide outside of Sugar. Take the time to fully understand the individual steps that make up the customer's decision-making process and the steps in Sugar that correlate with each part of the Smart Guide. For more complicated Smart Guides, it may help to sketch a diagram or map the Smart Guide on a spreadsheet before creating the Smart Guide template and related stages and activities in Sugar.

Configuring Smart Guide Display Settings

Smart Guides may be displayed as a panel beneath its parent record or as a separate record-view tab from the rest of the record. By default, all Smart Guides will be rendered in panel format unless the admin changes the display settings. Each Smart Guide-enabled module's display settings can be configured independently.

There are four display configurations available. The "tab" options will be grayed out and not selectable until you have saved the module's Display Type as "Tab" in Studio > Layouts > Record View as described in the steps below.

• Panel - Bottom (default): The Smart Guide panel will show at the bottom of the record view.
• Panel - Top: The Smart Guide panel will show at the top of the record view.
• Note: If "Panel - Top" is selected and tabs are enabled for the record view in Studio, then the Smart Guide will revert to the default display as a panel at the bottom of the record.
• Tab - First: The Smart Guide panel will be shown as the first tab of a tabbed record view layout. This option is grayed out and not selectable until you have saved the module's Display Type as "Tab" in Studio > Layouts > Record View.
• Tab - Last: The Smart Guide panel will be shown as the last tab of a tabbed record view layout. This option is grayed out and not selectable until you have saved the module's Display Type as "Tab" in Studio > Layouts > Record View.

Use the following steps to change a module's Smart Guides to display in the tabbed format:

1. Navigate to Admin > Studio and select the module (e.g. Accounts) for which you want to change your Smart Guides to a tabbed view.
2. Click on "Layouts" and then select the "Record View" layout to edit.
3. In the upper section of the record view layout, change "Display Type" to "Tab". Then click "Save & Deploy". For more information on changing to tabbed display type, refer to the Studio documentation in the Sugar Administration Guide.
   
4. Once you have changed the module to a tabbed view, navigate to Admin > Configure Modules in the Sugar Automate Settings section of the admin page:
   
5. Select "Tab - First" or "Tab - Last" as desired for the module and then click "Save".
   
   Note: If the "Tab - First" and "Tab - Last" options for any dropdown are disabled, then the Tab view has not been enabled for that module in Studio. To enable the Tab view, return to step 1 of these instructions.

The Smart Guides created within the selected module (e.g. Accounts) will now display as an additional tab in the record view instead of a panel below the record.

Sugar Automate Template Access

Templates created for Sugar Automate utilize three template modules:

• Smart Guide Templates
• Smart Guide Stage Templates
• Smart Guide Activity Templates

Administrator users can automatically access all of these modules to create new Smart Guide templates. To grant developer access to a regular user for creating Smart Guide templates, the user's role must have "Developer" access to all three template modules.

For regular users, a team is set on the activity template, stage template, and Smart Guide template records. Assuming the admin creates the template records using the global team, regular users without Developer role permissions will have access to all Smart Guides in Sugar, even if they are related to records outside of their team(s). Administrators should leverage the team fields on the Smart Guide template records if this is a concern.

For more information about teams and roles, please refer to the Team Management and Role Management documentation.

Creating Smart Guide Templates

The administrator composes a Smart Guide in Sugar using three steps:

1. Create a Smart Guide template.
2. Add stages to the Smart Guide template.
3. Add activities (calls, meetings, and tasks) to each stage of the Smart Guide template.

A Smart Guide template is the record that controls what users see after they choose a Smart Guide from the Smart Guide picker in the Smart Guide panel under leads, contacts, and other modules participating in the Smart Guide. Each time a user chooses to start a new Smart Guide for a record, a copy of the template with its related stages and activities is created.

Note: Running Smart Guides are automatically named "Record Name - Smart Guide Name," where the record name is the name of the record the user is viewing when they start the Smart Guide (e.g., the account's name) and the Smart Guide name is the name of the Smart Guide template that they choose.

The following steps cover creating a Smart Guide template.

1. Navigate to Admin > Templates in the Sugar Automate Settings section of the Admin page:
   
2. Click the Create button on the upper right of the Smart Guide Templates list view. Alternatively, click the three-dots menu in the Smart Guide Templates module tab to open the Actions menu and select "Create Smart Guide Template".
   
   • From list view:
     
   • From the module tab:
     
3. Refer to the Smart Guide Template Fields section of this page to complete the fields in the record view layout. All required fields are marked as such and must be completed prior to saving.
4. After completing the Smart Guide template fields, click "Save" and then move on to the Adding Stages to Smart Guide Templates section to add stages to the Smart Guide.

Smart Guide Template Fields

The Smart Guide Templates module contains the following fields:

Smart Guide Templates Module Tab

The Smart Guide Templates module tab is located on the navigation bar at the top of the Sugar screen after the administrator clicks on "Templates" on the Admin panel. Click the three-dos menu in the Smart Guide Templates tab to display the Actions, Recently Viewed, and Favorites menus. The Actions menu allows you to perform important actions within the module. The Recently Viewed menu displays the list of Smart Guide templates you last viewed in the module. The Favorites menu displays the list of Smart Guide templates you most recently marked as favorites in the module.

The Actions menu allows you to perform the following operations:

Adding Stages to Smart Guide Templates

After creating the Smart Guide template record, you must create stages for the Smart Guide. Stages are the groups of activities in the customer's decision-making process and are defined in the Smart Guide Stage Templates module.

After saving the Smart Guide template, follow these steps to add a stage to the Smart Guide:

1. Click on the Add Stage button in the panel below the Smart Guide template's fields:
   
2. Refer to the Smart Guide Stage Template Fields section of this page to complete the fields in the record view layout. All required fields are marked as such and must be completed prior to saving.
3. After completing the stage template's fields, click "Save." At this point in the design process, you may only need to populate the stage's name (e.g. "Awareness") before saving.
4. Continue creating stage templates via the Add Stage button until you have made one for every stage of the Smart Guide. For example, if the current Smart Guide will move through Awareness > Consideration > Purchase > Loyalty, you must create four separate stage templates.
5. New stages will be added to the end of the Smart Guide cycle. At any time from the Smart Guide template's design panel, you can re-order the stages by simply dragging them into the order you prefer. The stage's order numbers will adjust appropriately.
   
6. After creating a stage template for each stage of the Smart Guide and ordering the stages as desired, move on to the Adding Activities to Smart Guide Templates section to add activities to the stages.

Smart Guide Stage Template Fields

The Smart Guide Stage Templates module contains the following fields:

Adding Activities to Smart Guide Templates

Activities are the concrete actions that must be completed to move from one stage to the next. Under each stage, you can add activities in the form of tasks, calls, meetings, and milestones via the Smart Guide Activity Templates module. For calls and meetings, the connector will automatically add the activity's assigned user and the person associated with the Smart Guide's parent Sugar record (e.g. the lead or contact) as guests for the activity. This ensures that the activity appears on the assigned user's calendar and that the call or meeting shows up in the lead or contact's subpanel. Users can add or remove guests via the call or meeting's record view.

After saving a Smart Guide's stage template, follow these steps to add an activity to the stage:

1. Hover over the stage where you want to add an activity. When the stage's Actions menu appears, click the down arrow to reveal the options to add an activity:
   
   Alternatively, click "Copy" from a similar activity's Actions menu to duplicate, edit, and save a new activity in the Smart Guide.
2. Click on "Add Task," "Add Call," or "Add Meeting" to create an activity record for the stage.
3. Refer to the Smart Guide Activity Template Fields section of this page to complete the fields in the record view layout. If creating a task, select the relevant task Type. All required fields for the new activity are marked as such and must be completed prior to saving.
4. After completing the activity template's fields, click "Save."
5. Continue adding activities to this stage and all of the other stages in the Smart Guide as required by your business process. New activities will be added to the end of the Smart Guide stage. At any time, from the Smart Guide Template designer, you can re-order the activities by simply dragging them into the order you prefer. You may also drag and drop activities around from one stage to another. The activity order numbers will automatically adjust for the stage.
   

Once you have defined all activities for each stage of the Smart Guide, you may choose to add sub-activities to the activities created in this section. If so, please refer to the Adding Sub-Activities section. If sub-activities are not required by your business process, then the Smart Guide template is complete and is ready to share with users. For more information on using the templates you have created for Sugar Automate, please refer to the Sugar Automate User Guide.

Adding Sub-Activities

The activities on a Smart Guide Template may optionally contain one or more sub-activities. Simply expand the parent activity's Actions menu and select the appropriate activity type that you would like to nest underneath it. For example, an activity task called "Get Approval" could contain two sub-activity tasks for "Manager Approval" and "QA Signoff", which may be assigned to different users.

After saving a stage's activity template, follow these steps to add sub-activities under the activity:

1. On the parent activity (e.g. "Get Approval"), click the down arrow to reveal the Actions menu:
   
2. Click on "Add Task," "Add Call," or "Add Meeting" to create an activity record under the current activity. Alternatively, click "Copy" from a similar sub-activity's Actions menu to duplicate, edit, and save a new sub-activity in the Smart Guide.
3. Refer to the Smart Guide Activity Template Fields section of this page to complete the fields in the record view layout. If creating a task, select the relevant task Type. All required fields for the new activity are marked as such and must be completed prior to saving.
4. After completing the activity template's fields, click "Save." The sub-activity will be slightly indented and display the default order number x.1, where x is the order number of the parent activity.
5. To add another sub-activity to the same parent, return to the parent activity's Actions menu and select the appropriate activity type to create. Complete the activity's details and save. The second sub-activity will display the default order number x.2 when shown in the Smart Guide panel.
   
6. Continue adding sub-activities as required by your business process. New sub-activities will be added to the end of the parent activity. At any time, from the Smart Guide Template designer, you can re-order the sub-activities by simply dragging them into the order you prefer. You may not individually drag sub-activities to a new parent activity, but you can drag and drop the parent activities including all their sub-activities around from one stage to another. The activity order numbers will automatically adjust for the stage.

Once you have defined all activities and optional sub-activities for each stage of the Smart Guide, the template is complete and ready to share with users. For more information on using the templates you have created for Sugar Automate, please refer to the Sugar Automate User Guide.

Smart Guide Activity Template Fields

The Smart Guide Activity Templates module contains the following fields:

Adding Sugar Actions

Sugar Actions allow you to trigger automated or manual actions based on changes to the Smart Guide or the related parent record of the Smart Guide. Sugar Actions are created from the Sugar Actions subpanel within a guide, stage, or activity Smart Guide template. Some fields will be prefilled based on where you create the Sugar Action.

Once you have created a Sugar Action, you will select the trigger type that will define the source of the Sugar Action's trigger and the direction of the action once the trigger conditions are met.

There are two different trigger types:

• Smart Guide to Sugar Action
• Sugar Action to Sugar Guide

Smart Guide to Sugar Action

The Smart Guide to Sugar Actions trigger type can be added to any stage or activity of a Smart Guide and can either prompt a user to manually create, view, or edit a related Sugar record or trigger an automatic action to a related Sugar record based on changes to the Smart Guide.

When this trigger type is created for an activity template, the Sugar Action will appear on the activity in the Smart Guide as the icon unless you set the Display Icon field to "No" or set the Action Trigger Type field to be automatic (e.g., "Automatically Create Record"). When the user hovers over a Sugar Action icon on an activity, they will see the descriptive text used as the Sugar Action record's name.

Click on the icon at any time during the Smart Guide to perform the activity's related action. The admin also has the option to launch the action automatically when its parent activity begins or ends using the Trigger Event setting on the activity's Sugar Action record. For more information on the options available, refer to the Sugar Guide to Action Fields section. For more information on completing Sugar Actions, refer to the Sugar Automate page in the Application Guide.

When used on a stage or Smart Guide instead of at the activity level, a Sugar Action will not show as an icon; instead, it will automatically initiate when the stage or Smart Guide is set to "In Progress" or "Completed", as set in the Trigger Event field. For more information on the options available, refer to the Sugar Guide to Action Fields section. For more information on completing Sugar Actions, refer to the Sugar Automate page in the Application Guide.

To add a "Smart Guide to Sugar Action" Sugar Action to a Smart Guide stage or activity, follow these steps:

1. Navigate to the Smart Guide template record and find or create the stage or activity that should contain a Sugar Action.
2. Click on the name of the stage or activity in the template.
   
3. From the stage or activity's record view, scroll down to the Sugar Actions subpanel and click on the Create (+) button.
   
   Note: There is a limit of one active Sugar Action per Trigger Event type for each stage or activity in a Smart Guide. Attempting to add a second Sugar Action for the same Trigger Event type will result in an error on save unless one of the records has an "Active" value of "false". 
4. Set the Trigger Type field to "Smart Guide to Sugar Action".
5. Complete the other Sugar Action fields according to the Sugar Guide to Action Fields and Pre-Populating Fields via Sugar Actions sections, and then click "Save".
   • When setting the Relationship field, the first selector will always display the parent record's module name (i.e., Calls, Meetings, or Tasks) and refer to itself using the "self" identifier. If you would like to choose a record in a one-away module from the stage or activity (e.g., the opportunity related to the activity), then change the first selector to that module's name. A second Relationship selector dropdown will then appear containing the related module's name and it will now contain the "self" identifier to indicate that it is the chosen record. If you would like to choose a record in a two-away module from the stage or activity (e.g., create a contact related to the opportunity that is related to the activity), then change the second selector field to the two-away module. For this example, the two-level relationship will require three dropdown fields configured like this: 
     
6. After saving the Sugar Action, you will return to the stage or activity record view. You can now add another Sugar Action for a different Trigger Event on the stage or activity or click on the Smart Guide Template name to return to configuring the overall Smart Guide.

Pre-Populating Fields via Sugar Actions

When creating a "Sugar Guide to Sugar Action" trigger type from the Sugar Actions module, values can also be set to pre-populate in fields on the related record. When the Sugar Action is triggered and the Action Trigger Type field is set to "Manual", a new drawer will open and the values will be prefilled in the drawer which you selected in the Sugar Action record's Populate Fields section. If the Action Trigger Type field is set to "Automatic", the records will be created or updated in the background with the predefined field values.

Simply select the field that you would like to update (e.g. "Name") from the dropdown list and then type the value (e.g. "Call to schedule demo") in the adjacent field. You can populate the values of multiple fields for the related record by using the Add and Remove icons at the end of the row. If you choose to populate a date or datetime-type field, then you can either set a fixed date (or date and time) or one that occurs in the future relative to the day the action is triggered. For relate fields, simply choose the field name and then select the record to relate.

When the Sugar Action's "Action Type" is set to "Create Record" and the relationship type is a call, meeting, or task, the newly created activity will be related to the Smart Guide and show up in the Smart Guide panel. To place the new activity in a specific position in the Smart Guide, use the Populate Fields functionality to set the "Smart Guide Order" field to the numeric place that the activity should occupy in the Smart Guide.

Sugar Action to Smart Guide

The "Sugar Action to Smart Guide" trigger type can trigger a change to a Smart Guide based on changes to the related parent record fields.

To add a "Sugar Action to Smart Guide" Sugar Action to a Smart Guide, follow these steps:

1. Navigate to the Smart Guide template record.
2. Scroll down to the Sugar Actions subpanel and click on the Create (+) button.
   
3. Set the Trigger Type field to "Smart Action to Smart Guide".
4. Complete the other Sugar Action fields according to the Sugar Action to Smart Guide Fields section, and then click "Save".

Sugar Action Fields

The Sugar Actions module contains the following fields. The fields displayed are dependent on the Trigger Type selected.

Sugar Guide to Sugar Action Fields

Sugar Action to Sugar Guide Fields

Blocking Activities

Using the Blocked By field, the admin has the option to make an activity's start dependent on the completion of one or more earlier activities. For example, you can block users from starting "Meeting 2" until "Meeting 1" has been completed.

Similarly, the admin can choose to block activities until a specified stage has been completed using the Blocked By Stages field. For example, you can block users from starting the "Value Proposition Meeting" activity until the "Prospecting and Introduction" stage has been completed. 

Blocked activities display the Blocked icon (a circle with a slash) and do not have options to start or complete the activity from the Smart Guide panel. Users will also receive an error if they attempt to close the activity from its Sugar record view. Once the required activities have been completed, then the blocked activity will become unblocked.

Removing Stages and Activities from Smart Guide Templates

If you would like to remove a stage or activity from a Smart Guide template, simply expand the stage or activity's Actions menu and click on "Delete Stage" or "Delete Activity." This will apply to all Smart Guides that are started after the change has been made. Any running or completed Smart Guides will not be affected by the deletion.

Disabling Stage and Activity Actions

If you would like to remove an option from the Stage Actions Menu or the Activity Actions Menu in a Smart Guide, select the options using the "Disabled Stage Actions" and "Disabled Activity Actions" fields on the Smart Guide template record. These fields are both multiselect and are empty by default.

• Disabling a stage action will remove it from the Actions menu for all users on all of the stages in the Smart Guide.
• Disabling an activity action will remove it from the Actions menu on all of the Smart Guide's activities for all users.

Changes made to the Disabled Actions fields on existing Smart Guide templates will be applied instantly on save and apply to all new and existing Smart Guides related to the template.

Copying Smart Guide Templates

You can also create a new Smart Guide template by duplicating an existing Smart Guide's template. The Copy option is useful if the Smart Guide you want to create has similar stages and activities to an existing Smart Guide. Unlike other records in Sugar, all of the related stages and activities will also copy over to the new Smart Guide template, which you can edit, rearrange, delete, or add to later.

The following steps cover creating a new Smart Guide template by duplicating an existing Smart Guide template:

1. Navigate to Admin > Templates in the Smart Guide section of the Admin panel.
2. Click on the name of the Smart Guide that you want to copy.
3. Click the record's Actions menu and select "Copy".
   
4. The displayed record view is pre-populated with the original Smart Guide's values. Update the necessary fields and then click "Save."

Importing Smart Guide Templates

Smart Guide templates can be exported from one Sugar instance and then imported into another Sugar instance where both have Sugar Automate (e.g. from your test or development instance to your live production instance). Only files that have been exported from a Sugar instance can be imported into a Sugar instance. Exported Smart Guides will download as the appropriate .json file type for upload to the Smart Guide Templates module.

Follow these steps to export a Smart Guide template from a test instance and then import it to a production instance as an example:

Note: Both instances must have Sugar Automate.

1. In your test instance, create and configure a Smart Guide template with the desired stages and activities according to the sections covered earlier on this page.
2. When you are satisfied with the template, expand the template's record-view Actions menu and click on "Export." Save the exported .json file to your computer.
   
3. Navigate to your production instance. In the Admin panel, click on "Templates" in the Smart Guide section.
4. Click the three-dots menu in the Smart Guide Templates module tab and select "Import Smart Guide Template".
   
5. Click on "Choose File" to search for and select the .json file you saved in step 2 and then click "Import."
6. Review the template's design and settings to be sure everything imported as expected.
7. Finally, activate the Smart Guide template in your production instance by placing a checkmark in the template record's Active field and immediately test its behavior.
   

Note: You cannot import a new Smart Guide template with the same name but different ID as an existing Smart Guide template. You must change the name of the new record or use "Copy" to create a duplicate Smart Guide template.

Updating Smart Guide Templates via Import

If you have access to a test instance with Sugar Automate, you can update existing Smart Guide templates via the import tool. The existing Smart Guide template and the updated Smart Guide template must have the same record IDs. This allows you to export a Smart Guide template for maintenance without interrupting your production instance.

Follow these steps to update an existing Smart Guide template via the import tool:

Note: You must already have Sugar Automate on both your test and production instances.

1. In your production instance, navigate to the record view for the Smart Guide template that you would like to update.
2. Expand the template's record-view Actions menu and click on "Export." Save the exported .json file to your computer.
   
3. Navigate to your test instance's Admin panel and click on "Templates" in the Smart Guide section.
4. Click the three-dots menu in the Smart Guide Templates module tab and select "Import Smart Guide Template."
   
5. Click on "Choose File" to search for and select the .json file you saved in step 2 and then click "Import."
6. Navigate to the imported Smart Guide and make any changes according to the sections covered earlier on this page.
7. When you have finished testing and making changes, expand the template's record-view Actions menu and click on "Export." Save the exported .json file to your computer, replacing the previous template file if prompted.
8. Return to your production instance. Navigate to the Admin panel and click on "Templates" in the Smart Guide section.
9. Expand the Smart Guide Templates module tab and select "Import Smart Guide Template."
10. Click on "Choose File" to search for and select the .json file you saved in step 7 and then click "Import."
11. An alert will prompt you to confirm that you would like to replace the existing template. Click "Confirm" to commit the update or click cancel to without making any changes.
    

The changes you made in your test instance should now be reflected in the original Smart Guide template in your production instance. The changes will apply to all Smart Guides that are started after the import. Any running or completed Smart Guides will not be affected.

Using Smart Guides With SugarBPM

Customers using SugarBPM for workflow automation can configure their process definitions to start, cancel, or delete a Smart Guide when specified conditions are met. It is also possible to create criteria for evaluation based on sub-activity records that are part of a Smart Guide.

Starting Smart Guides via SugarBPM

Administrators can configure process definitions to start a certain Smart Guide when conditions are met for a record. For example, some opportunities may not need to engage in the exhaustive sales process, like when an existing customer requests a quote. For this scenario, the "Opportunity Quick Deal" Smart Guide could be set to automatically begin when a new opportunity is created for existing business. 

To set a condition for Smart Guides to start via SugarBPM, simply build a Change Fields action into a process definition for the affected module. For the "quick deal" example mentioned above, the affected module is Opportunities. In its simplest form, the basic process definition structure would be as follows:

• Target module: Opportunities
• Start event: New records only; Type = Existing Business
• Change Fields action: Smart Guide Template = "Opportunity Quick Deal"
• End event: Terminate

For more information on creating process definitions, please refer to the SugarBPM documentation.

Canceling and Deleting Smart Guides via Sugar BPM

Two checkbox fields exist on the Smart Guide record that, when set to "true" (checked), will either cancel or delete a Smart Guide: "Is Canceled" and "Is Deleted". An administrator can configure a SugarBPM process definition's Change Fields action to set one of these fields to "true" and thereby cancel or delete the running Smart Guide when a condition is met. For example, If an opportunity closes before a related sales Smart Guide has completed, then the Smart Guide could be set to automatically cancel.

To set a condition for deleting or canceling Smart Guides via SugarBPM, simply build a Change Fields action into a process definition for the affected module. For the example mentioned above, the affected module is Opportunities. In its simplest form, the basic process definition structure would be as follows:

• Target module: Smart Guides
• Start event: New records and all updates; Smart Guide Template = "Opportunity Quick Deal"
• Receive Message event: Opportunities "Status" changes to "Closed Won" OR Opportunities "Status" changes to "Closed Lost"
• Change Fields action: "Is Cancelled" = true
• End event: Terminate

For more information on creating process definitions, please refer to the SugarBPM documentation.

Adding SugarBPM Event Criteria Based on Smart Guides

When designing events that evaluate a set of criteria (e.g., Start event, gateways), you can add criteria that evaluate meetings, calls, or tasks that are sub-activities of a Smart Guide activity. For example, you might design a Start event that triggers a process when all of the sub-tasks under the target meeting in a Smart Guide are complete, which then notifies the creator of the meeting via email. In its simplest form, the basic process definition for this example would be as follows:

• Target module: Meetings
• Start event: Updated records only (all updates); Tasks (Child Tasks: parent_meeting_of_task_rel) when All Related Records have Status = "Completed"
• Send Message event: Send to user who created the meeting
• End event: Terminate

The module relationships that represent these sub-activities in Smart Guides can be difficult to differentiate from other relationships to the same modules but they follow a certain naming convention. If you are viewing a process definition that targets the Meetings module, the three sub-activity relationships are named as described in the following table:

The naming convention is the same when targeting the Calls or Tasks modules and the names of the relationships in the above table can be extrapolated to these target modules.

For more information on creating process definitions, please refer to the SugarBPM documentation.

Understanding Progress and Momentum

Sugar Automate measures the performance of each Smart Guide in Sugar via Smart Guide progress and Smart Guide momentum. Smart Guide progress lets you know how close to completion the Smart Guide is, while momentum measures how efficiently the Smart Guide has advanced with respect to the time-based performance standards set by the administrator. 

The following sections explain progress and momentum in detail.

Smart Guide Progress

Smart Guide progress is visually represented as a Progress Bar. The blue portion of the bar represents the percentage of points that have been completed relative to the Smart Guide's total point value.

Points contribute to the growth of the Progress Bar for running Smart Guides in Sugar. When creating activities for your Smart Guide templates, you can assign 1 to 10 points to each activity in the Smart Guide. Each time you assign points to an activity, the parent stage's total point value increases and so does the overall Smart Guide's point value. Later, when a user engages with a Smart Guide, the progress bar will grow commensurate to each completed activity's point value relative to the Smart Guide's total point value.

While an activity can have a maximum of 10 points, there is no limit to the number of points that may be attributed to a stage or Smart Guide. For more information on Smart Guide progress, please refer to the Calculating Progress section of this page.

All fields associated with Smart Guide progress are located on the activity's task, meeting, or call record. For more information on assigning progress points, please refer to the Smart Guide Activity Template Fields section.

Calculating Progress

The Smart Guide panel contains a progress bar that represents how far along a customer is in the Smart Guide based on the point values and statuses of the Smart Guide's activities. The administrator assigns the point values from 1 point up to 10 points for each activity in a Smart Guide. When an activity is In Progress, 30% of its point value is credited to the progress bar. Activities set to Held, Completed, Not Held, or Not Applicable credit 100% of their point values to the progress bar. The Smart Guide calculates its overall progress as a percentage rounded up to the next whole number: {points completed}/{total Smart Guide points}.

For example, in the Smart Guide below, the administrator has created a Smart Guide with a total of 240 points, and the activities associated with 80 of those points have been completed. Therefore, the progress bar shows that the Smart Guide is 33% complete (80/240=0.333, rounded down).

Smart Guide Momentum

For most processes, there is an optimal amount of time that should elapse between stages and activities. This is known as process momentum. Depending on the type of Smart Guide, this is sometimes called velocity, efficiency, or forward motion. Momentum functionality in the Sugar Automate allows admins to define the optimal time-to-complete between activities and stages. The performance standards can then be calculated against actual time-to-complete and used by individuals and their managers to assess process efficiency.

Momentum Points contribute to the Momentum Score for running Smart Guides in Sugar. A higher momentum point value for one activity over another would indicate the relative importance of that activity over the other. All fields associated with momentum are located on the activity's task, meeting, or call record. For more information on assigning momentum points, please refer to the Smart Guide Activity Template Fields section.

Smart Guide momentum is visually represented in Sugar as a Gauge Chart dashlet but can also be displayed as a Momentum Bar on the list view dashlet. Both visualizations show how well the Smart Guide is keeping up with expected time standards as a percentage of momentum points completed.

For more information on the momentum functionality, please refer to the Calculating Momentum section of this page.

Calculating Momentum

Smart Guide momentum reflects how well a Smart Guide is keeping up with expected time standards as a percentage of momentum points completed. When momentum is defined for one or more activities, it becomes a part of a summed score for the Smart Guide Stage as well as to the Smart Guide object itself.

The momentum of an activity contains its total Momentum Points when not yet started. The tracking of the actual momentum days or hours only begins when an activity has been started.

Below is an example of how Momentum Points and Momentum Scores are calculated for the Gauge Chart and the Momentum Bar. As an example, imagine a Smart Guide template that has been set up with two stages that have two tasks each. Each task has the following Momentum Points and Momentum Due Days set: 

In the example above, Task A is given a Momentum Point value of 100. if Task A is completed within its expected 5 days (i.e., less than 120 hours), then the Momentum Score for that task will remain 100. However, if Task A is completed after the expected 5 days, for example, it takes 6 days (i.e., 144 hours), then the score for that task will be less than 100 because there is a penalty for each hour over the projected hours that a task is not completed.

The following calculation is used to calculate the Momentum Score for an activity:

• Activity Momentum = (expected time / actual time) x potential activity points

The formula applied to Task A, which was completed in 144 hours opposed to the projected 120 hours, gives us a Momentum Score of 83 from the activity's 100 potential momentum points:

• (120/144) x 100 = 83

Assuming no other activities in our example have kicked off, Tasks B, C, and D still have perfect 100% scores and the overall Smart Guide Momentum after Task A is completed is a total 303 (83+100+80+40) out of a potential 320, or 95% (rounded up) of the Smart Guide's potential momentum points, as represented by the Smart Guide's gauge chart:

Momentum Scores are also visualized in the Smart Guide list view dashlet as a color-coded bar that follows the same color convention as the gauge chart and with a bar-length that represents the momentum score's percentage of the Smart Guide's potential momentum:

Reporting on Momentum

Smart Guide progress points, momentum points, and momentum scores are also reportable fields in the Reports module. For more information on building reports in Sugar, please refer to the Reports documentation. As an example, the following report evaluates the average rate of momentum for the activities in a given Smart Guide for all users. It helps to identify common points of delay in the Smart Guide that may need the attention of management.

Note: Before using this report, be sure that you have assigned momentum points for the activities in the Smart Guides that you want to track and that enough time has passed for momentum values to have been calculated. For more information on assigning momentum points, please refer to the Smart Guide Activity Template Fields section.

Use the following steps to create a report that evaluates the average momentum for each task in a Smart Guide:

1. Navigate to the Reports module and create a Summation Report for the Smart Guides module.
2. Define the first filter:
   • In the Related Modules panel, under the Smart Guides folder, find the "Smart Guide Stages" folder and click on the + icon to expand it.
   • Under the Smart Guide Stages folder, find the "Tasks" folder and click on the word "Tasks".
   • In the Available Fields panel, click on the Status field to add the filter to the main panel.
   • Set the filter's operator and value to "is Completed".
     
3. Define the second filter:
   • In the same Available Fields panel, click on the Smart Guide Momentum Points field to add a new filter to the main panel.
   • Set the filter's operator and value to "Greater than 0".
     
4. Define the third filter:
   • In the Related Modules panel, under the topmost Smart Guides folder, click on the words "Smart Guide Template" next to the Smart Guide Template folder.
   • In the Available Fields panel, click on the Name field to add the filter to the main panel.
   • Select your favorite Smart Guide template for the filter and enable the Run Time Filter option.
     
5. Click "Next" and then set one Group-By field:
   • In the Related Modules panel, under the Smart Guides folder, find the "Smart Guide Stages" folder and click on the + icon to expand it.
   • Under the Smart Guide Stages folder, find the "Tasks" folder and click on the word "Tasks".
   • In the Available Fields panel, click on the Subject field to add it to the main panel.
6. Click "Next" to proceed to the Display Summary step where one Display Summary line should already be set.
7. Set the following additional Display Summary:
   
   • Smart Guides > Smart Guide Stages > Tasks > AVG: Smart Guide Momentum Ratio
8. Click "Next" to proceed to the Chart Options step and choose "Vertical Bar (Grouped)".
9. Click "Next" to proceed to the final step, name the report "Average Momentum Ratio by Smart Guide Task", and click "Save & Run".

The resulting report will display a separate bar for each task in the selected Smart Guide. The bar represents what fraction of 1 (i.e., 100%) each task has achieved in momentum. Those with a value of less than 1 have lower rates of momentum based on the average of their actual vs expected completion times. In the table below the chart, you can also view the total average momentum for the entire Smart Guide.

Advanced Configurations

The following advanced options may be configured by administrators who want to enable additional modules to be used with Smart Guide templates, to define custom "closed" statuses for records used in Smart Guides, and to create Web Hooks for communicating with external systems.

Configuring Modules for Smart Guides

The Smart Guide panel will be included on records for modules that are enabled for Smart Guides via Configure Modules. By default, the Accounts, Contacts, Leads, Opportunities, and Cases modules are enabled. When you create new Smart Guide templates, the templates may include any combination of the enabled modules.

If your business converts lead records into contacts and opportunities, then you may want to design a Smart Guide template that follows the lead as it is converted in the system. For example, if you design a Smart Guide template and select Leads, Contacts, and Opportunities for the Smart Guide's Available Modules, a user will then be able to start the Smart Guide on a lead record and continue to manage the same Smart Guide after they convert the lead into a contact and, optionally, an opportunity. Please note that the contact and opportunity records must be created on the Lead Conversion screen in order for the Smart Guide to continue with those records. 

To enable additional modules to be used with Smart Guide templates, you can configure Sugar Automate's available modules via Admin > Sugar Automate Settings > Configure Modules. Conversely, you can disable modules so that they cannot be used in Smart Guides.

The following steps walk through how to make modules available for Sugar Automate for your instance.

1. Navigate to Admin > Sugar Automate Settings > Configure Modules.
   
2. In the top section, select or remove modules until the multi-select field displays the modules that you may want to use in a Smart Guide template and click "Save". When you start creating individual Smart Guide templates, you can select as many or as few of the enabled modules as you like for each template.
   Note: If you see a "No Access" label on this step, please clear your browser cache and reload the page.
   

Configuring Custom "Closed" Statuses

Many instances have been configured to use different statuses (e.g. Closed, In Progress, Invalid) for records than the statuses used in a stock Sugar instance. You may define which statuses Sugar Automate considers "closed" for your instance via the Sugar dropdown editor.

By default, Sugar Automate considers tasks as closed when they have a status of "Completed" or "Not Applicable". Calls and meetings are closed when they have a status of "Held" or "Not Held". To add or remove statuses that are considered closed in your instance, navigate to Admin > Dropdown Editor and modify the statuses for the respective dropdown list shown below:

• cj_calls_completed_status_list
• cj_meetings_completed_status_list
• cj_tasks_completed_status_list

For more information on working with dropdown lists, refer to the Developer Tools documentation in the Sugar Administration Guide.

Assignment Notifications

When a user starts a new Smarx and one or more of the activities in that Smart Guide are assigned to another user(s), the other users will receive a single, compiled "digest" style email that lists all of the activities that are assigned to them and of record type "task". No notifications will be sent to the logged-in user starting the Smart Guide for tasks that are assigned to them. For any call or meeting activities in the Smart Guide, email invitations will be sent according to the default behavior of the Sugar version you are using.

Please note that notification emails will only be sent if "Send Assignment Notification" is enabled in both the admin System Email Settings and in the user's profile.

Web Hooks

The Smart Guide Web Hooks allow you to send data to an external URL so that additional processing can be completed outside the Sugar application. This can allow you to send the data to other applications within your organization (e.g. send a Slack message) or to validate that the Smart Guide can progress on to the next stage.

Smart Guide Web Hooks are available for use with records in all of the template modules (Smart Guide Templates, Stage Templates, and Activity Templates) via the Web Hooks subpanel under each template's record view.

The following fields are available when creating a Smart Guide Web Hook:

Content-Type: application/json
X-Api-Key: xxxxxxxxx

Web Hook Example

This example will cover how to send a Slack message using the Web Hooks for Sugar Automate.

Prerequisite: To successfully set up this integration, you must be the admin for your Slack workspace or have permission explicitly granted by the Slack admin to add webhooks to your workspace via the Slack API. 

Steps to complete:

1. Navigate to https://api.slack.com/apps and create a new app for your workspace.
   
2. Activate incoming webhooks for your app:
   
3. After activating webhooks, click "Add New Webhook to Workspace" at the bottom of the screen, and in the pop-up, select the Slack channel where you want your message to appear. Copy the resulting URL to your clipboard.
   
4. In your Sugar instance, navigate to the Web Hooks subpanel under the template record (Smart Guide Template, Stage Template, or Activity Template) where you want the web hook to trigger from. Click "Create" (+) in the subpanel.
5. Configure the web hook record's fields as follows:
   
   
   • Request Method: POST
   • Trigger Event: For this example, we have selected "After In Progress", meaning that our hook will get triggered after the parent activity's status has been set to "In Progress".
   • URL: Enter the Webhook URL that you generated and copied from Slack's API in the earlier step.
   • Request Format: Set the format in which the "Post Body" will be sent. It can be a JSON string or a query string. For the Slack example, we will be sending a JSON String.
   • Custom Post Body: Enter the post body to send with your request as instructed in the Slack API documentation. For testing, we have entered:
      {"text": "This message was sent via Smart Guide webhook:tada:"}
     Note: To include variable data from the Smart Guide or its related parent record (e.g., the Smart Guide's name or fields from the account record in an account Smart Guide), refer to the Custom Post Body Variables section of this page.
6. Save the web hook record in Sugar with an "Active" status enabled.
7. Test your web hook by clicking on "Send Test Request" in the Test Webhook dashlet in the intelligence pane of the web hook's record view.
   

To test your web hook in production, start the related Smart Guide in your Sugar instance and set the relevant Smart Guide, stage, or activity to "In Progress". When this web hook triggers, you will see a message in your Slack app.

Custom Post Body and URL Variables

When sending a web hook request via POST with a custom post body, you can include field variables from the Smart Guide's parent record (the parent account or contact, for example) and from the Smart Guide, stage, and activities to which the web hook is associated. Additionally, the Current User, Assigned User, and site URL variables can be sent to the external endpoint.

The variables used for web hooks can also be used in the URL field on Smart Guide Activity records to create custom dynamic URLs that reflect data from the parent record. For example, entering the value http://www.google.com/search?q={$parent.name} will take the user who clicks the link from a running Smart Guide to a google search for the name of the parent record.

The following variables are only a few examples but serve to illustrate the format that is used. Please note that relate-type fields cannot be used as variables.

• {$site_url}
• {$current_user.full_name}
• {$assigned_user.full_name}
• {$parent.name}
• {$activity.name}
• {$stage.name}
• {$Smart Guide.name}

Test Webhook Dashlet

From the Web Hooks record view, you will see a special Test Webhook Dashboard which contains the Test Webhook dashlet. The Test Webhook dashlet lets you send a test request to validate your work. Simply save the web hook record and then click on "Send Test Request".