Download the PHP package augustash/ash_salesforce without Composer
On this page you can find all versions of the php package augustash/ash_salesforce. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download augustash/ash_salesforce
More information about augustash/ash_salesforce
Files in augustash/ash_salesforce
Package ash_salesforce
Short Description Sends Drupal form submissions to Salesforce through the Web-to-Case or Web-to-Lead form the client's Salesforce admin generates.
License proprietary
Homepage https://github.com/augustash/ash_salesforce
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package ash_salesforce
Ash Salesforce
Sends webform and contact form submissions to Salesforce as Cases or Leads, through the Web-to-Case or Web-to-Lead form the client's Salesforce admin generates. No connected app, no API login.
How it works
- Paste the generated form at Configuration → Web services → Salesforce form mappings → Salesforce forms. The HTML Salesforce generates is the whole description of the org: endpoint, org ID, field IDs, max lengths and picklist values. The page shows what it read, so a bad paste is obvious.
- Add a mapping. Pick the site form and the Salesforce form, then walk through the site form one field at a time and click the Salesforce field it goes to. The likeliest target is offered first, outlined and marked Suggested; Don't send keeps a field on the site only. Obvious non-data (buttons, markup, CAPTCHAs, elements hidden from the form) is skipped.
- Set fixed values: the record type that routes the record, an origin that says which site and form it came from. Picklists are stored by option label, not by ID.
- Review and save. Edit opens on the summary; any one choice can be changed without walking the form again.
Submissions are queued on save, sent at the end of the same request, and retried by cron if Salesforce is down. A 4xx is logged and dropped.
Origin: which site, which form
One org usually takes records from several sites, and from several forms on
each. So a new mapping suggests Case Origin (or Lead Source) as
<site label> <form label>, e.g. Metro Contact the MAC, editable before
saving. Set the site label under Settings; empty uses the site name.
The client's admin has to add each value to the Origin picklist and enable it for the record type, or a restricted picklist drops the record silently.
One mapping, several orgs
Custom field and picklist IDs differ between a sandbox and production. Paste
each org's form as its own Salesforce form. Mappings key everything by stable
names (the standard field name, or a custom field's label), so pointing an
environment at another org is one override in settings.php:
To keep an environment from sending at all:
Things to know
- Web-to-Case answers 200 even when it drops a record. The reason goes only to the debug email in the client's Web-to-Case settings, so ask them to keep one. Values are also cut to the field's max length before sending, because Salesforce rejects an overrun the same silent way.
- Inputs are capped at the Salesforce field's length. Every mapped
element gets the field's
maxlength, so the visitor meets the limit on the form. Disabled mappings count too, so the form reads the same in every environment. - Turn off Web-to-Case's own reCAPTCHA. Submissions are posted server-side and can't solve it; guard the site form with its own CAPTCHA.
- Assignment and auto-response rules run as they do for any Web-to-Case record.
- Contact forms are sent on submit, not on save. Without contact_storage a message is never stored, so there is no insert to hook.
- Webform drafts are sent once, when completed.
Tests
Tagged aai and ash_salesforce. Salesforce is mocked; nothing is posted.
