CRM stands for Customer Relationship Management – still a little bit confused? Well, what if we said that we get rid of all of those boring, tedious spreadsheets and present all of the information in easy to read sections of your own application? Winner I say!

So, why should SugarCRM be a part of your business?

ENHANCES YOUR CUSTOMER RELATIONS

 We enable businesses to create extraordinary customer relationships with the most innovative and affordable CRM solution on the market. With SugarCRM keeping a good overview of your customers is at the end of your fingertips, we strive to ensure that our different editions suit the needs of you and your customers. Using data analysis on existing customers’ history to enrich your relationships with them, in turn driving up sales.

OPTIMIZES MARKETING STRATEGIES

 Who else is guilty of typing up email address after email address just to send one mail shot? You’re not alone! Many companies still manually add customers to mailing lists when doing email marketing, this is where we can help. SugarCRM has a fully integrated marketing system, which enables you to directly pull customers information at the click of a finger to be used in marketing campaigns. Optimizing your marketing strategies creates time for your marketing department to use their skills to the full.

REGISTER LEADS AND CONTACTS

 Have you ever been in a position where a sales representative has left your company, but hasn’t left any of their lead or contacts and your stuck trying to pick up where they left off? With us, every bit of contact made with a potential or existing customer is logged in the platform making sure that you can just pick up where someone has left off. The detailed system of CRM makes it easy to see where you or a co-worker is with a customer and helps keep those relationships stable.

ROOM FOR GROWTH

 Currently using a spreadsheet to note down all of your interactions with customers? It may work on a small scale, but when you reach 50-100 customers, recording everything on a spreadsheet becomes tedious. This is where we come in. No matter how small or large your company is we make it easy for you to get everything you need. No matter how much you want to grow your business, we will always be on hand to help.

 A SERVICE NOT A PRODUCT

We do all of the hard work, so you don’t have to. With SugarCRM, you are getting a service not a product! We are here from the design and consultation stage to the final product support stage, we are here to ensure that your integration from any other CRM company to SugarCRM runs seamlessly from the start. We offer long-term support and training with SugarCRM because we know that being thrown in the deep end with new software can be extremely daunting.

If you are interested in hearing more about how SugarCRM could impact your business, then get in touch with us. Our sales team are on hand to answer any questions you may have.

The post 5 Reasons Why SugarCRM Should Be Part Of Your Business appeared first on Sugabyte.

Sugar 8 was released in April 2018 and will reach planned End-of-Life and End-of-Support on April 30, 2020.

As software advances and new versions are released, vendors are unable to provide continuous support for older software versions. This is the case with all software and is not specific to SugarCRM or CRM’s in general – (although this is sometimes the general consensus.)

Sugar 8 was first released in April 2018 – following Sugars Support Policy, End-of-Life and End-of-Support will commence on April 30th, 2020.

Why is this important?

Where we may continue to support you as your Implementation/Support partner from a consultative standpoint – helping to identify issues and consult with your users regarding any obstacles they face, Sugar will no longer release vital security updates or bug fixes if your version of Sugar has reached End of Life.

This means, although your software may perform as expected at present – your data and internal process configurations are not entirely secure, due to the lack of forthcoming improvements to the software version you operate on.

It is highly advisable to remain on supported software throughout your organisation to avoid any potential risks or failures in your software versions.

Upgrade Information

One huge advantage of migrating to Sugar’s Cloud product offering is that customers remain on the latest Sugar software versions and are automatically upgraded to newer versions as and when they are released. Sugar make this migration as simple and cost-effective as possible to customers already using Sugar.

If you are still using Sugar Version 8 – we would strongly recommend arranging a free consultation call with one of our expert consultants. We can help you to realise the different deployment options available to you in upgrading your Sugar – as well as the latest innovation and feature enhancements available for you to leverage moving forward.

Click the link below to arrange your free consultation call.

We offer complete SugarCRM upgrade services, ensuring your data is safe and secure and providing a seamless migration to the latest version.

If you have already upgraded your Sugar, we thank you for your on-going support and loyalty – If there is any other information you would like to discuss please get in touch, we will be more than happy to help you!

Contact Us

The post Sugar 8 End-of-Life – All you need to know! appeared first on Sugabyte.

These flow elements can be added and connected via paths and the route your process will take depends on certain conditions you set within those elements, which can then make changes to your triggered record and related records over multi-levels or send out email alerts. The possibilities are endless when building multi-step flows with Advanced Workflow.

Within the visual design canvas, there are 6 different types of elements that can be built into a Process Definition, see below for more information on each element.

Start Events

A Start event is used to define the conditions that have to be met to begin your process. Next to setting start conditions, the Start event can be triggered on record creation or record update. The latter is further divided by triggering on the first record update or any record update if the conditions are met.

Intermediate Events

These events happen during the normal operation of the process and can send messages, receive messages or cause the process to wait for a period of time.
– Send Message: This element sends an email configured in “Process Email Templates” to the defined recipient.
– Receive Message: This element waits for a record to be updated and to meet a condition defined in this element before the process can proceed.
– Wait: Waits for a static amount of time or a fixed date in the system.

Activities

These are the only elements that may require a user response (as opposed to automation). An Activity can either be an Approve/Reject or a Route option (to learn more about Activities in SugarCRM click here.)
– Approve/Reject: A user must decide if a circumstance is approved or rejected.
– Route: A user must review a record that has been routed to them.

Actions

Actions are automated elements to either execute a Business Rule, create a record or update a Sugar record. They are completed within the Advanced Workflow tool and do not require manual interaction to execute. Following options are available:
– Business Rule: A Business Rule is set up by Administrators in the “Process Business Rules” module and is used to create reusable rules that can then be implemented as an Action within a Process Definition. These can be anything from updating the “Assigned to” user of a record to a certain user based on Lead Source or setting triggers that can then be used later on in the Process Definition, the possibilities are endless.
– Assign User: This updates the user that will be responsible for the remaining part of the process. These actions should be followed by an activity for the process user to complete. Within this action, the record’s “Assigned to” user can also be updated to the same as the chosen process user.
– Round Robin: These action types will assign the overall process flow to a member of a Team in a “take-your-turn” fashion. These actions should be followed by an Activity for the process user to complete. Within this action, the record’s “Assigned to” user can also be updated to the same as the chosen process user.
– Change Field: This Action will allow one or more fields to be changed on the target record or in related records over multiple levels.
– Add Related Record: This Action will create a new Sugar record and relate it to the target Sugar record or a record related to the target record.

Gateways

Gateway elements are used to control the flow of a process via merging and splitting. When several activities may result in a common outcome, a gateway serves as a merging mechanism or a “Converging” element. When a single activity may result in several different outcomes, a gateway serves as a splitting element or a “Diverging” element. There are four types of gateways:
– Exclusive Gateway: When divergent, determines a single outgoing path based on data conditions. When convergent, accepts only the flow that reaches it first.
– Inclusive Gateway: Evaluates all criteria to determine one or multiple outgoing paths.
– Parallel Gateway: When divergent, begins the concurrent execution of all outgoing paths. When convergent, waits for completion of all concurrent paths.
– Event-Based Gateway: Evaluates wait and receive message events.

End Event

End Events signal the completion of a process. See below the three end event options:
– Do Nothing: Ends the thread of a flow, will not affect any other threads that are running.
– Terminate Process: Ends the thread of a flow but also terminates the entire process regardless of any parallel events in the Process Definition.
– Send Message: Ends the thread of a flow and sends a message configured in Process Email Templates to specified recipients.

If you have any further questions about the visual design canvas please contact us by using the below button.

The post How to navigate the Visual Design Canvas for Process Definitions appeared first on Sugabyte.

How to favourite products

Product Catalog records can now be marked as favourites by users, this will aid the users that deal with certain products more frequently than others as they will be easily accessible via the “Products Catalog Quick Picks” dashlet.
A product can be marked as a Favourite via the below methods:

– Products List View (Admin users only): In the column to the left is a new “Star” button. If this is marked, the product will display as a favourite

– Products Record View (Admin users only): In the Product Name field is a “Star” button. If this is marked, the product will display as a favourite.

–Products Catalog Dashlet (for non-admin users): In the Products dashlet which can be found in the Opportunities and/or Revenue Line Items modules, end users can select the icon to the left of the Product Name which will open the Product in Record View, allowing the Favourite option to be selected.

Quick Picks Dashlet

Once products have been “Favourited”, they will display in the “Favourites” tab of the dashlet, whereas all recently used products will display in the “Recently Used” tab of the dashlet, allowing users easy and clear access when creating Opportunity and Revenue Line Item records.

If you have any further questions about the Quick Picks dashlet, please contact us using the below button.

The post Quick Picks Dashlet in SugarCRM appeared first on Sugabyte.

Administrator users can access the Process Management page via Processes > Process Management or Admin > Process Management. This will show all processes that have been triggered and their current status.

Most statuses are self-explanatory. However, users often wonder what the difference is between “Terminated” and “Cancelled” Processes.

Terminated Processes

There are two scenarios that will cause Advanced Workflow to terminate a process.
– If a record that has triggered the Start Event of the process is later deleted, then the process will no longer continue and this will be marked as “Terminated” in the Process Management view.
– Advanced Workflow will set a process to terminated if the record that triggered the Start Event of the process meets the “Terminate Clause” configured by an admin user within the Process Definition.

A Terminate Clause can be set up/amended/reviewed by right-clicking in the Design Canvas of the Process Definition and selecting “Process Definition”. Enter a criteria in the “Terminate Process” area. In the example below the process is set up to terminate if at any point the Lead Status is equal to “Converted” or “Dead”.

Cancelled Processes

There is only one scenario that causes a process to be cancelled and that is if an admin user manually cancels the process via the Process Management page which could be for any number of reasons.

It is imperative to know the difference between the process statuses when troubleshooting why a record did not update as expected.
For example, if the Process Status is highlighted as “Terminated” on the Process Management page, it is then known that either the record that triggered the process was deleted or the Terminate Clause was met. A good tip to identify immediately if the record was deleted or if the Terminate clause caused the process to terminate is to check if the “Record Name” in the process management page is populated or empty. If empty then the record has been deleted.
If the Status is highlighted as “Cancelled”, then it is known that this decision was made by an admin user making the decision to not allow the process to continue.

If you would like more information on the differences between Terminated and Cancelled Processes, please contact us using the below button.

The post Advanced Workflow: Terminated Vs Cancelled Processes appeared first on Sugabyte.

Reports can also be scheduled in Sugar, this means that based on the timeframe set, the report will be emailed to the user. In order for the user to receive the scheduled report they must have export rights, not only for the Reports module but for the module for which the data is based on. Without these access rights set via Role Management in Sugar, users will be unable to schedule a report to be sent to themselves.

When a report is sent it will be attached to an email as a PDF to the users Primary Email Address in Sugar.

Please Note: Reports that contain a chart in Sugar will not have a chart displayed in the emailed PDF version.

Requirements to schedule a Report

A personal outgoing email account must be configured by the user scheduling the report.

An outgoing mail server for the Sugar system must be configured by the administrator.

The “Run Reports Generation Scheduled Tasks” scheduler must be activated by an admin user.

Please Note: Scheduled Reports may arrive after the set time based on the cycle for the Run Report Generation Scheduled Task set by an administrator in your system.

How to schedule Reports

1. Navigate to the Reports module and create a new schedule via one of the below methods:
   1. Open the Actions menu in a reports Detail View
   2. Select “Create Schedule”

   Or

   1. In the Reports module tab in the menu bar click on the down arrow and select  “Report Schedules”
   2. Click on the blue “Create” button at the top of the List View page.
2. Give the schedule a name such as “Sugabyte Daily Report”
3. Select the report that you would like to schedule.
4. Set the Start Date and Time that this schedule should commence

Once the report schedule has been created and saved, a “Users” subpanel will show beneath the Report Schedule Record View where further users can be linked if the report should be sent to multiple users.

Please Note: When scheduling a report, users can choose a start day, time and interval. However, if you are configuring the report to be sent for multiple users, Sugar will convert the time to UTC so that each user receives the report simultaneously regardless of time zones.

1. Set the Repeat Type to how frequently the report should be sent
2. Ensure the “Active” checkbox is set to True and save.

Please Note: If you would like to stop receiving the report at any time, access the Report Schedule and set the “Active” checkbox to False and save.

The post How to schedule Reports with SugarCRM appeared first on Sugabyte.

This latest SugarCRM Mobile release will significantly benefit customers through the features introduced in this release:

• Adds downloading of quote PDFs from Quote records using the templates configured on your Sugar instance
  • Note: Available for instances on Winter ’19 (8.3) and above.
• Adds uploading files and images to records while running SugarCRM Mobile in Offline Mode.
  • The attachments will be queued and synced to the Sugar instance once the connection is restored.

This release also includes fixes for issues identified in prior releases of SugarCRM Mobile.

More details about this update may be found through the following release notes:
SugarCRM Mobile for Andriod Release Notes 6.4.0
SugarCRM Mobile for iOS Release Notes 6.4.0

SugarCRM Mobile 6.4.0 is compatible with Sugar 8.0 and above. Please review the Mobile Supported Platforms page for more information about device compatibility.

All existing installations of SugarCRM Mobile will be upgraded through the phone or tablets native upgrade functionality. Alternatively, upgrades can be performed by searching for “SugarCRM Mobile” in the application store for your device or using the following links.
Google Play Store
Apple App Store

The post SugarCRM Mobile 6.4.0 is Live appeared first on Sugabyte.

The Process Validator allows users to validate a process definition on import or on an as-needed basis. The purpose of this feature is to detect any configuration errors or sequencing mistakes within the process definition.

With this new feature, there is the introduction of three new buttons in the Process Definition design canvas.

Validate

The validate button when selected triggers an action to inspect the process and each element within the design. On inspection, the validator will verify that evaluations and settings are valid if the validator finds an error or a warning this will be displayed as a badge on the affected elements and in the Error Console in the lower part of the screen. When hovering over the “Show/Hide Errors” button the number of issues found will be displayed, clicking on this button will cause the Error Console to appear/disappear from view.

Save and Validate

The save and validate option combines the above validate option along with also saving your current process definition.

Show/Hide Errors

Clicking this button will show or hide the error console displayed at the bottom of the page. The console will display warnings or errors that were found in the last validation.
Please Note: Any new changes to the Process Definition may not be reflected in the error console if a new validation has not run.
In order to gain the most accurate information, it’s best practice to click on either “Validate” or “Save and Validate” immediately after repairing errors.

Auto-Validate option

In addition to the above, Administrator users have the ability to switch on “Auto-validate process definition on auto-save” this setting can be found by navigating to Admin > System Settings > (New) Advanced Workflow panel > selecting the checkbox to enable the auto-validate. This means that when process definitions are auto-saved after a certain time period (the autosave time period can be set up in this same panel and can range from “never to every 5 minutes”) a validation will automatically run on this save without the end user needing to select a validate option.

This enhancement to the Advanced Workflow tool will greatly improve the end users experience when building/updating process definitions and minimise the errors made.

If you have any questions about this new feature then please click on the button below to contact Sugabyte directly.

The post Process Validation with SugarCRM appeared first on Sugabyte.

When adding a related record the user creating the process definition will be presented with the below screen:

Related Module
– If the record that is to be created directly relates to the target record then select that module here. For example, if the process definition is triggered from an Account record and upon progressing through this process definition a Call record should be created and directly relate to the Account record then Calls must be selected in the first-level module relationship area.
– If the record that should be created is a “two-away” record (a record that will be related to a record that is directly related to the target record) then the intermediate module should be selected for the “Related Module”, not the target module and not the module of the record that you would like to create.

Filter
If the record that should be created is a two-away record then a filter can optionally be applied on the first-level module relationship. For example, if the first-level module is Contacts then a Call record can be created that is related to all Contacts related to the target module and if a filter is entered then a Call record can be created against only Contacts that have the “Do Not Call> is not equal to > yes.
Please Note: If the first-level module relationship is on the one-side of a one-to-one or many-to-one relationship then the filter option will be greyed out.

Related To
Optionally, set the second-level module relationship to Calls if a Call record should be created for Contacts filtered out in the first-level module relationship.

From here all fields that should be auto-populated for the created Call record can be set in the “Fields” section.

For more information on how to create a related record in a process definition please contact Sugabyte by clicking on the below button.

The post Creating Related Records Through Multi-Layer Relationships appeared first on Sugabyte.

When accessing the change field action within a process definition in Sugar Winter ’19 (8.3), it can be seen that the layout has changed to reflect this new feature. The module as always will default to the target module of the process definition to and users can as normal select fields to update. The module can be updated to a related module and again users can select a field to update, however, the new element is the filtering section. In the example shown below we have selected to update the “Notes” fields in Calls related to an Account, but only for related Calls that have the Status of “Scheduled”.

Before the release of 8.3 this filtering option was not available and so it could not be set up to only update related records that meet certain criteria.

In addition to filtering on related records, users can now select to update records related to the related record and filter on those as well!

For example, if in a process definition if users wanted to update a field on a Note record, but not a Note record related to the Account but a Note record related to the Accounts related scheduled Calls, but, only if the Note Type is “Internal Note”. This is now possible with this new feature release.

In the example above we have selected to update the Description in a Note field, but only for Note records where the Note Type is “Internal Note” and the Note record is related to a Call that has the Status of “Scheduled” and the Call record is related to the Account record that has triggered this process definition.

The addition of these new features will greatly enhance the end user experience as it will allow a more streamlined approach to updating records via Advanced Workflow.

For more information on how to set up change field functions in a process definition please contact Sugabyte by clicking on the below button.

The post Changing fields through Multi-Layer relationships in Sugar appeared first on Sugabyte.