- Workflow Builder Reference Guide Introduction
- AudienceWorkflow Builder Application
- Workflow Builder OverviewWorkflow-Building Exercises
- How to Solicit Post-Transactional Surveys via EmailWorkflow Blocks
- Assign Case to Agent
- Bright Pattern Create Object
- Bright Pattern Delete Object
- Bright Pattern Search Object
- Bright Pattern Update Object
- DB Execute
- Exception Handler
- Fetch URL
- Get Next Record
- Get User Configuration
- Internal Message
- Microsoft Dynamics Create Object
- Microsoft Dynamics Delete Object
- Microsoft Dynamics Search Object
- Microsoft Dynamics Select Account
- Microsoft Dynamics Update Object
- RightNow Create Object
- RightNow Search
- RightNow Select Account
- RightNow Update Object
- Salesforce.com Delete
- Salesforce.com Insert
- Salesforce.com Search
- Salesforce.com Select Account
- Salesforce.com Update
- Send Message+
- ServiceNow Create Object
- ServiceNow Search
- ServiceNow Select Account
- ServiceNow Update Object
- Set Variable
- Start Another Workflow
- Transfer Case to Service
- Zapier Invoke Zap
- Zapier Select Account
- Zendesk API Request
- Zendesk Create Object
- Zendesk Search
- Zendesk Select Account
- Zendesk Update ObjectReference
- Standard Fields for CRM Objects
- String Expressions
- Integer Expressions
- Floating Point Expressions
- Built-In Functions
The Salesforce.com Search workflow block is the part of Salesforce.com Integration with Bright Pattern Contact Center.
This block executes the specified Salesforce.com (SFDC) record selection statement written in either the Salesforce Object Query Language (SOQL) or Salesforce Object Search Language (SOSL). Workflow variables can be used in this statement in the $(varname) from. Consider this example of an SOQL statement that uses the $(ANI) variable: SELECT id, name FROM Accounts WHERE phone = ‘$(ANI)’.
The columns of the first record of retrieved recordset are stored in variables <recordset_name>.<column_name>. For that statement, the results will be stored in variables Recorset.id and Recordset.name.
The number of returned records is stored in variable <recordset_name>.__count__ (e.g., RS.__count__). (Note the double underscores in front and after count; they are used to reduce the chance of confusing the name of this variable with a column name in a recordset.)
To iterate through the recordset, use Get Next Record block.
The Salesforce.com Search block may take one of the following conditional exits: Failed or No Data.
The Failed conditional exit is executed if the search operation failed.
The No Data conditional exit is executed if no data matching the specified search criteria is found.
Title text is the name of the instance of the block. Enter a name in the text field and the new name of the block appears in the flowchart.
Name the retrieved recordset
This is the name of the recordset that will be retrieved via this search operation. Name of the retrieved recordset is a mandatory field.
Query language is the language used for the data query. Possible language options include the Salesforce Object Query Language (SOQL) and Salesforce Object Search Language (SOSL). Unlike SOQL, which can only query one object at a time, a single SOSL query can be used to search multiple objects, which can both simplify and improve the efficiency of searches, especially in large SFDC environments. For more information, see Salesforce docs.
Statement refers to the record selection statement in the selected Query language. It may contain application variables in the $(varname) format.
The code and the body of the received HTTP response is stored in local variables $(integrationResultCode) and $(integrationResultBody), respectively. For troubleshooting purposes, use the EMail or Internal Message block to obtain the content of responses indicating a failed search attempt. For more information, see the description of the variable $(integrationResultBody).