- Welcome to the Knowledge Base
- Desktop Environment
- Forecasts & Quotas
- Importing Data
- Marketing Campaigns
- Upload Library
- Workbooks Web Insights
- Using HubSpot with Workbooks
- People & Organisations
- Introduction to Reporting
- Displaying Reports
- Creating Reports
- Reporting Explained
- Emailing Scheduled Reports
- Sharing Reports
- Using Formulae
- Displaying reports within Record Views
- Audit Reporting
- Introduction to Transaction Documents
- Credit Notes
- Customer Orders
- Supplier Orders
- Contract Management
- Adobe Sign Integration
- Introduction to Zapier
- Available Triggers and Actions
- Linking your Workbooks Account to Zapier
Setting up Zaps
- Posted Invoices to Xero Invoices
- Xero payments to Workbooks Tasks
- New Case to Google Drive folder
- New Case to Basecamp Project
- Jira Issue to new Case
- New Workbooks Case to JIRA Ticket
- Wufoo Form Entry to Sales Lead
- Eventbrite Attendee to Sales Lead and Task
- Facebook Ad Leads to Sales Leads
- Posted Credit Note to Task
- Survey Monkey responses to Tasks
- Multistep Zaps
- Outlook Connector
- Exchange Server Sync
- Workbooks Mobile Client
- Introduction to System Administration
- Users & Security
- Email & Integration
- Creating & Modifying Picklists
- Creating Custom Fields
- Report-based Custom Fields
- Linked Fields
- Record Templates
- Form Layouts
- Customising relationships between parties
- Opportunity Stages
- PDF Configuration
- Releases & Roadmap
- Workbooks Glossary
- Contact Support
Editing a Web Key Form
Because a web form is provided with no style and little formatting (as well as including all the fields from your Case or Lead record), you'll probably want to edit the form before publishing it on your website.
The information provided below relates to Leads but the same techniques apply to Case forms too.
Fields with [Required] appended to their label are required by Workbooks, and a form submission will fail if these fields are omitted.
Then the class='required' is added to each required element, for example:
<label for="person_lead_party[name]">Name [Required]</label><input name="person_lead_party[name]" class='required'/>
Now before the form is submitted the user will be informed of any fields they haven't filled in that are required.
<label for="last_contacted">Last contacted</label><input name="last_contacted" class="date"/>
You may wish to replace date fields with a more user friendly date picker, so long as the date is submitted using the same field name and format this is allowed.
Time fields should be submitted as HH::MM using the 24 hour clock. This is checked by adding the class "time" to the field.
Date Time Fields
Date time fields should be submitted as "<date> <time>" ie, a date and a time in the above formats concatenated together. They can be validated in the same way as Date fields.
By default when a form submission succeeds Workbooks generates a basic Success page. If a submission fails then Workbooks generates a failure page, with some error messages describing the failure. These messages are intended to help you ensure your form is correct.
Within the form there are two hidden fields which allow you to specify a page on your site to redirect to on failure, and a page to redirect to on success. The hidden fields are shown below. When you generate a sample form they are placed in comments; you need to remove the comment and change the value attributes when you use the form on your site.
<input type ='hidden' name='success_url' value='/success.html' /> <input type ='hidden' name='failure_url' value='/failure.html' />
The value is the URL you want to redirect to, it should be a full URL, for example:
The failure page will be redirected to with query parameters added to the URL, for example:
When using web-to-case the success page is redirected to complete with query parameters added to in the URL identifying the case which was created (the case_reference), for example:
Where CASE-AAAA is the Case Reference for the successfully created Case and B is its Id.
If you have the capability to have server generated pages then you could create a page that rendered these messages to your end user. This would require that you created a page using a server side technology such as PHP, .NET or JSP.