Let’s say you have 2 custom action buttons in your form - one creates an Account record, and the other uploads 3 images to Attachments object.
Although these push actions are separate, all button requests are sent behind the scenes to Salesforce regardless.
And this means that one custom action can easily affect another.
For example: if you fill in account details, upload 3 files, and then press on the “create account” custom button - this will send the account details along with the files behind the scenes - and if the files weigh more than 30MB (which is the limit) - this will make the account push action fail.
Ok - so in this version we’ve added an option to the custom Salesforce action called: request optimization.
Once this checkbox is turned on it will only send this specific button request when it is pressed, so if a limit is reached for another action it will not affect it.
* Please note that this option is good for:
- Custom buttons
- Custom action triggered by a condition
- Custom action triggered from a Salesforce table
Watch how to use the Request optimization option in the custom action
Enjoy!
- Asking us questions is the fastest and most affective way to get assistance.
- Got a question? Check out our FAQs pages for answers to commonly asked questions.
- Check out our complete index of the FormTitan Topics organized by categories.
- Browse our topics directory to find the feature you are looking for.
- ContactStill haven't found what you were looking for? no problems... simply send us your inquiry.