SugarCRM is a CRM system with a a simple user interface, industry-leading customer experience, and an intuitive customization platform.

This is an open source component template for Sugar CRM which is developed specifically to run on elastic.io platform. You can clone it and change it as you wish.

In order for the elastic.io platform to authenticate with SugarCRM, the following tasks need to be completed:

• An admin must manually create an OAuth App on the SugarCRM instance through SugarCRM's UI (step by step instructions below)
• If using a version of SugarCRM that was released after Winter '18, you must register a platform on your SugarCRM instance
  • With Sugar 8, this can be done through the UI (step by step instructions below)
  • It is also possible to load new platform values by creating and installing a module Developers use the platform parameter to distinguish their custom platform from other clients when using the Sugar API. For example, when a user accesses Sugar via the desktop client and the mobile client simultaneously without being logged out of either, it is because the API recognizes that they are different platforms due to their unique platform identifiers. The platform identifier also makes it easy for a Sugar administrator to configure which API platforms are allowed to access their instance via Admin > Configure API Platforms. To learn more about platform identifiers, please refer to the Sugar Developer Blog in the SugarCRM Community.
• Finally, authentication information for your Sugar instance must be entered into the elastic.io UI (step by step instructions below)

In order the platform to connect to your SugarCRM instance, an app needs to be created on that instance. Below are the steps to do so. Once that is done, you will provide a valid username and password to the elastic.io platform. The platform will exchange that username and password for a token. In a production system, the best practice is to create a dedicated user for the elastic.io platform. This user should have the minimum required permissions.

1. As an admin on your SugarCRM instance, go to the Administration panel

   

2. Select OAuth Keys

   

3. In the top bar, select the dropdown for the now visible OAuth Keys option

   

4. Select Create OAuth Key

5. Fill in the following values:

   1. Consumer Key Name: Pick a name that is convenient to remember
   2. Consumer Key: Pick a strongly random string. You will need to provide this information as part of the SugarCRM component account information
   3. Consumer Secret: Pick a strongly random string. You will need to provide this information as part of the SugarCRM component account information
   4. OAuth Version: OAuth 2.0
   5. Client Type: Sugar User
   6. Description: Optional value for your convenience

   

6. Click Save

1. As an admin on your SugarCRM instance, go to the Administration panel

   

2. Select Configure API Platforms

   

3. Enter a value of your choosing for the new platform and click Add and then Save.

   

Fill in the following for your account:

• Name Your Account: Name to identify this account on elastic.io
• Your SugarCRM domain: URL of your Sugar CRM instance
• Your login: Username used to login to SugarCRM instance
• Your password: Password used to login to SugarCRM instance
• Your OAuth 2.0 Consumer Key: Value created in step 5ii.
• Your OAuth 2.0 Consumer Secret: Value created in step 5iii.
• Custom Platform Value: Platform value registered above.

For real-time tasks please use separate oauth keys to avoid login conflicts.

Parameter platform should be set to some custom string but should be unique per sugar component in order to avoid any potential login conflicts. So now platform is "$TASK_ID:$STEP_ID".

It is possible to fetch any type newly created and/or updated object in your SugarCRM instance. Select the trigger Fetch new and updated objects and then configure the following:

• SugarCRM module to fetch: Type of object to fetch
• Number of records to fetch: Maximum number of records to fetch per call. If left blank then the default set on your SugarCRM instance.

It is possible to have new and updated objects be pushed to the elastic.io platform via webhooks. In order to do so, select Fetch new and updated objects (getObjects - Webhook). When a flow with this trigger is started, the elastic.io platform will register webhooks on the SugarCRM instance. When the flow is stopped, this webhook will be destroyed by the platform.

It is possible to have the ids of deleted objects be pushed to the elastic.io platform via webhooks. In order to do so, select Fetch deleted objects (getDeletedObjects - Webhook). When a flow with this trigger is started, the elastic.io platform will register webhooks on the SugarCRM instance. When the flow is stopped, this webhook will be destroyed by the platform.

Given an object, looks up the object with that ID. You must select the type of object to lookup.

• SugarCRM module to lookup - dropdown list where you should choose the module, which you want to lookup. E.g. Accounts.
• Pass binary data to the next component (if found object has it) - a checkbox, if it is checked and found object has a binary field (type of file) then its data will be passed to the next component as a binary attachment.

Lookup a list of objects satisfying specified criteria.

• SugarCRM module to lookup - dropdown list where you should choose the module, which you want to lookup. E.g. Accounts.
• Output method - dropdown list with following values: "Emit all", "Emit page", "Emit individually".
• Number of search terms - text field where you can specify a number of search terms (not less than 0 and not greater than 99). Default value is 0 (if provided value is not allowed).

Depending on the configuration field Output method the input metadata can contain different fields: Output method - "Emit page": Field "Page size" - required positive integer that defaults to 1000; Field "Page number" - required non-negative integer (starts with 0, default value 0);

Output method - "Emit all": Field "Maximum number of records" - optional positive integer (default value 1000);

Output method - "Emit individually": Field "Maximum number of records" - optional positive integer (default value 10000);

Note that the number of records the component emits may affect the performance of the platform/component.

Groups of fields for each search term go next:

Field "Field name" - string represents module's field (a list of allowed values is available); Field "Field value" - string represents value for selected field; Field "Condition" - one of the following: "=", "!=", "<", "<=", ">", ">=", "STARTS WITH", "ENDS WITH", "CONTAINS", "IS NULL", "NOT NULL", "IN", "NOT IN";

Between each two term's group of fields:

Field "Logical operator" - one of the following: "AND", "OR";

Output data depends on the configuration field Output method: "Emit page", "Emit all" - an array of records; "Emit individually" - a record;

Given an object, deletes the object with that ID. You must select the type of object to lookup.

Update an existing entry if the id provided. Otherwise create a new entry. You must select the type of object to lookup. Input metadata is fetched dynamically from your SugarCRM account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.

• Module - Input field where you should choose the object type, which you want to find. E.g. Note
• Utilize data attachment from previous step (for objects with a binary field) - a checkbox, if it is checked and an input message contains an attachment and specified object has a binary field (type of file) then the attachment is put into object's binary field.

When Utilize data attachment from previous step (for objects with a binary field) is checked and this action is used with Local Agent error would be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'

Provides a simple interface for quickly creating large amounts of objects.

• Module - dropdown list where you should choose the object type to perform bulk create operation. E.g. Cases.

• Objects - an array of the objects that will be created. Example of format SugarCRM objects

Result is an object with a property result: array. It contains the list of newly created objects.

Provides a simple interface for quickly updating large amounts of objects.

• Module - dropdown list where you should choose the object type to perform bulk update operation. E.g. Cases.

• Massupdate_params - an object contains array of uid's and new values for updated objects. Action allows not only update primitive fields but also add or replace values in the lists. Please, take a look SugarCRM Mass Update documentation for examples.

Result is an object with the 2 properties:

• failed - numeric, how many objects were failed to update.
• status - string, if operation were successful status="done". Operation could consider successful even if failed > 0

Note: SugarCRM server doesn't return errors in case of a wrong uid.

Provides a simple interface for quickly deleting large amounts of objects.

• Module - dropdown list where you should choose the object type to perform bulk delete operation. E.g. Cases.

• Massupdate_params - an object contains array of uid's for deleted objects. Please, take a look SugarCRM Mass Update documentation for examples.

Result is an object with the 2 properties:

• failed - numeric, how many objects were failed to delete.
• status - string, if operation were successful status="done". Operation could consider successful even if failed > 0

Retrieve a set of records filtered by an expression utilizing the SugarCRM REST API filter endpoint. (See for details - https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_9.1/Integration/Web_Services/REST_API/Endpoints/modulefilter_POST/)

• SugarCRM module - dropdown list where you should choose the module, which you want to lookup. E.g. Accounts.
• Output method - dropdown list with following values: Emit all, Emit individually.

In the Intergator mode a request can be built by filling the following fields:

• Filter expression - JSON object representing the filter expression. E.g.

  [
    {
      "billing_address_country":
      {
        "$in": ["England","France"]
      }
    }
  ]

• Maximum number of records - maximum number of records to return. Default is 20.
• The number of records to skip - number of records to skip over before records are returned. Default is 0.
• How to sort the returned records - how to sort the returned records, in a comma delimited list with the direction appended to the column name after a colon. E.g. "name:DESC,account_type:DESC,date_modified:ASC".

In the Developer mode a request can be built utilizing all features by providing a JSON object (for more information go to the link above). E.g.:

{
  "filter": [{
    "$or": [{
        "$and": [{
            "billing_address_country": {
              "$not_in": ["DE", "India"]
            }
          },
          {
            "acc_float_c": {
              "$is_null": ""
            }
          }
        ]
      },
      {
        "billing_address_country": {
          "$equals": "England"
        }
      }
    ]
  }],
  "fields": "id,name,billing_address_country,parent_name,accdate_c,acccheck_c,acc_float_c",
  "max_num": 42
}

Note that the number of records the component emits may affect the performance of the platform/component.

Output data depends on the configuration field Output method: Emit all - an array of records. Emit individually - a record.

For the local testing (e.g. spec-integration) ELASTICIO_TASK_ID and ELASTICIO_STEP_ID envs should be provided.

This component interacts with version 10 of the SugarCRM REST API. It has been tested with SugarCRM Enterprise, Version 7.9.1.0 (Build 1074) and SugarCRM Enterprise, Version 8.0.0 (Build 211) (Spring '18).

Apache-2.0 © elastic.io GmbH