This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
One of the most underrated tool groups, the Documentation Category is full of gems that can help you improve the aesthetic, organization, and shareability of your workflows. Chief among them is the Tool Container Tool – in addition to better aesthetic this tool has the ability to disable all the tools within it, lending itself to a handful of functional applications as well:
The new authentication and encryption settings allow IT departments to have much greater control over the email tool. The settings in themselves are a big step towards preventing spoofing, but there is one step that must still be done on the SMTP server itself.
The Tool Container is a tool that allows you to organize your module by placing tools inside of the Tool Container. Because the Tool Container can be opened and closed without impacting the behavior of the tools they contain, you can effectively minimize sections of your module so as to bring greater clarity to the overall picture. From a visual perspective, the Tool Container encourages object-oriented design!
Another feature of the Tool Container is the ability to disable/enable an individual Container.
An example application for this is a module where you need to do some design/testing, but you do not want to write the Output file until everything is working properly. By placing your Output tools inside of a Tool Container, and then disabling the container, you will be assured that no files will be generated. Re-enabling the Output tools is a piece of cake; just uncheck the “Disabled” checkbox. This feature allows you to easily control the generation of Output files or the processing of portions of your module. For users developing complex modules, the Tool Container delivers a powerful time-saving tool for the module design process.
Now everyone loves to talk about their workflow masterpieces, however the notion of documenting them doesn't always hold the same appeal. The Comment Tool would be happy to help and can make documenting and structuring your workflow easy and straight forward. Whether you want to include images, text descriptions or categorize parts of your workflow, the Comment Tool can act as a great refresher when revisiting workflows and make it far more intuitive for work colleagues to follow along. This article provides a few examples on how.
When using the Salesforce Input tool, the following error is seen at run-time:
400: Bad Request
This may only occur on some tables
It fails almost immediately after the workflow starts running.
It may also been seen on the Salesforce Credentials screen along with the error:
invalid_grant: authentication failure
Salesforce Input tool
Version 4.0 or 4.1
Confirm where you are seeing the error. If it is on the Salesforce Credentials configuration page when you click Connect, and you see "invalid_grant", please see Solution B.
Otherwise, validate the query to get a more verbose error log.
1. Use the Query Builder option (this is the default option) and select the Table and Output Fields you want to read in.
2. Change to the Custom Query option and click the Validate button:
3. If you receive the error: "OPERATION_TOO_LARGE: exceeded 100000 distinct ids", see Solution A.
The data you are attempting to pull is too large to be returned in one call based on the Salesforce API limits used by the Salesforce Input Tool. Limit the number of results returned by modifying the WHERE Clause (SOQL) in the tool's configuration:
Please see the Additional Resources section below for a guide on SOQL (Salesforce Object Query Language). Here are some suggestions:
Try limiting date fields by relative dates :
CreatedDate = THIS_YEAR
Try limiting a string field to a certain value:
You can also combine conditions with logical operators like AND & OR:
Name='SFDC Computing' AND NumberOfEmployees>25
For more advanced comparisons, you can perform fuzzy matches by using the LIKE operator. For example, you can retrieve all accounts whose names start with SFDC by using this condition:
WHERE Name LIKE 'SFDC%'
- The % wildcard character matches any or no character. The _ character in contrast can be used to match just one character.
The credentials are incorrect. Please confirm your Username, Password, and Token are correct.
Salesforce Knowledge Base - Write SOQL Queries
Salesforce Knowledge Base - Reset Your Security Token