Author 诗语

Creating a Feed for the Agile CRM Add-On

SummaryCreate a FeedFeed Settings ScreenCreating a New ContactCreating a New TaskConditional Logic

Summary
Before the Agile CRM Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, contact and task data being sent to Agile CRM.
Create a Feed
To create a feed to Agile CRM using the Agile CRM Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Agile CRM.
Once within your desired form, hover over Settings and click on Agile CRM.
Click Add New to create a new feed. You will be presented with the Agile CRM feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshots below.

A Feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
For Action, chose either Create Contact or Create Task. This will define the action that is performed when the feed is triggered by your form.

Creating a New Contact
When Create Contact is chosen as the Action, the Contact Details will display.

Map Fields: Fields accepted by Agile CRM are listed on the left, with form field dropdowns to the right. Use the dropdowns to select the fields within your form that will be used for the corresponding values. Additional fields may also be used when using the left side dropdown.
Tags: Assign any tags that you would like to be associated with this contact. These values are comma separated and accept both static values as well as merge tags to dynamically insert tags based on field values.
Select the checkbox labeled Update Contact if already exists if you would like to update the contact if it already exists in Agile CRM. If selected, an additional dropdown will appear allowing you to either replace existing information or simply append any new data. If this is not selected, an existing client will simply be discarded.

Creating a New Task
When Create Task is chosen as the Action, the Task Details will display.

Define the Subject of the task. This field supports both static values, as well as merge tags to dynamically insert field values.
The Days Until Due field allows you to determine the due date of new tasks submitted. This field requires a numerical value and will set a due date this many days in the future.
Priority: Use the dropdown to set the Priority. Options are High, Normal, and Low.
Status: Use the dropdown to set the Status. Options are Yet To Start, In Progress, and Completed.
Type: Use the dropdown to set the Type. Options are Call, Email, Follow Up, Meeting, Milestone, Send, Tweet, and Other.
Select the checkbox labeled Create Note for Task to create a new note on that task. Additional fields will appear allowing you to set the Note Subject and Note Description. These fields support both static text, as well as merge tags to dynamically generate content based on field submissions.
If the Assign Task to Created Contact checkbox is selected, a contact will be created upon submission and the new task will be assigned to the newly created contact.

Conditional Logic

Conditional Logic: If unchecked, every successful form submission will be sent to Agile CRM. If you wish to set specific conditions for sending form data to Agile CRM, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Creating a Feed for the Campfire Add-On

SummaryCreate a FeedFeed Settings Screen

Summary
Before the Campfire Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, form data being sent to Campfire.
Create a Feed
To create a feed to Campfire using the Campfire Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Campfire.
Once within your desired form, hover over Settings and click on Campfire.
Click Add New to create a new feed. You will be presented with the Campfire feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
The Campfire Room dropdown allows you to determine what room notifications will be broadcasted in.
Once the room is selected, a Message field will appear. By default, a generic mix of static text and merge tags displays. You may modify this as you see fit.
Select the Highlight Message checkbox to highlight the message for better visibility in chat,
Conditional Logic: If unchecked, every successful form submission will be sent to Campfire. If you wish to set specific conditions for sending form data to Campfire, then check the 「Enable Condition」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Creating a Feed for the Capsule CRM Add-On

SummaryCreate a FeedFeed Settings ScreenCreating a New PersonCreating a New TaskConditional Logic

Summary
Before the Capsule CRM Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, person and task data being sent to Capsule CRM.
Create a Feed
To create a feed to Capsule CRM using the Capsule CRM Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with Capsule CRM.
Once within your desired form, hover over Settings and click on Capsule CRM.
Click Add New to create a new feed. You will be presented with the Capsule CRM feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshots below.

A Feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
For Action, chose either Create New Person or Create New Task. This will define the action that is performed when the feed is triggered by your form.

Creating a New Person
When Create New Person is chosen as the Action, the Person Details will display.

Map Fields: Fields accepted by Capsule CRM are listed on the left, with form field dropdowns to the right. Use the dropdowns to select the fields within your form that will be used for the corresponding values. Additional fields may also be used when using the left side dropdown.
In the About field you can enter static text as well as merge tags. To review and insert available merge tags, click the button to the right of the field.
Select the checkbox labeled Update Person if already exists if you would like to update the person if it already exists in Capsule CRM. If selected, an additional dropdown will appear allowing you to either replace existing information or append any new data. If not selected, an existing client will simply be discarded.
The Assign To options allow you to assign the person to a new case and/or opportunity. These individual checkboxes will present more details upon selection. Both support static values as well as merge tags.

Creating a New Task
When Create New Task is chosen as the Action, the Task Details will display.

Define the Description of the task. This field supports both static values, as well as merge tags to dynamically insert field values.
The Detail field allows you to provide additional details regarding the task. This field also supports merge tags.
The Days Until Due field allows you to determine the due date of new tasks submitted. This field requires a numerical value and will set a due date this many days in the future.
Status: Use the dropdown to set the Status. Options are Open and Completed.
Category: Use the dropdown to set the Category. Options are Call, Email, Follow-up, Meeting, Milestone, and Send.
Owner: Use the dropdown to select the Owner.
The Assign Task option allows you to assign the new task to the newly created contact when used with the Create New Person action.

Conditional Logic

Conditional Logic: If unchecked, every successful form submission will be sent to Capsule CRM. If you wish to set specific conditions for sending form data to Capsule CRM, then check the 「Enable」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Creating a Feed for the Coupons Add-On

SummaryCreate a FeedFeed SettingsFeed Settings Screenshot

Summary

Before the Coupons Add-On can be used with Gravity Forms, you will first need to create a feed. A Coupon feed allows you to integrate the Coupons functionality with a Gravity Forms form to create a Coupon Pricing Field. The Coupon field works in conjunction with the other pricing fields, taking the total of all of the fields and applying a discount.

Note: It is required that you include one at least one Product field and one Total field to use the Coupon Field.

Create a Feed

To create a feed for Coupons using the Coupons add-on for Gravity Forms, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.Click on Coupons in the left side Forms menu.Click Add New to create a new feed. You will be presented with the Coupons feed settings screen.

Feed Settings

The following fields are available within the settings screen. Refer to the screenshot of the settings below.

Select the form you wish to add a Coupon field to from the Gravity Form drop down.Fill in the information under Coupon Basics. Coupon Name: The name you would like your Coupon to have. Coupon Code: The coupon code you would like your customer to input upon checkout. This can consist of letters or numbers of any order. Coupon Amount: The amount of the coupon. Select Flat($) or Percentage(%). If you select Flat($), the customer will receive a certain dollar amount off of their product. If you select Percentage, the customer will pay a certain percent less on their product.Fill in the information under Coupon Options. Start Date: The date you want your coupon to be valid. Your customer will not be able to use this coupon until on or after this date. End Date: Determines when the coupon expires, rather than when it becomes valid. Usage Limit: The amount of times your customers can use this coupon. Stackable: By default this option is not enabled. Check this box if you would like your customers to be able to use multiple coupons in one purchase.Click the Update Settings button to save your options.

Feed Settings Screenshot

Creating a Feed for the Dropbox Add-On

SummaryCreate a FeedFeed SettingsFeed Settings Screenshot

Summary

Before the Dropbox Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, files being sent to Dropbox.

It is required that you include a File Upload field on your form to use the Dropbox Add-On.

Create a Feed

To create a feed for Dropbox using the Dropbox Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard.

Click on Forms in the left side menu.Select the form that you want to use with Dropbox.Once within your desired form, hover over Settings and click on Dropbox.Click Add New to create a new feed. You will be presented with the Dropbox feed settings screen.

Feed Settings

The following fields are available within the settings screen. Refer to the settings screenshot below.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.The File Upload Field option allows you to either define a specific file upload field to be used with Dropbox or allow all file upload fields to relay the upload to Dropbox.The Destination Folder defines the folder where your uploads will be saved. If you would like to create a new folder, you will need to do so within Dropbox, then access the settings page again.Conditional Logic: If unchecked, every successful form submission will be sent to Dropbox. If you wish to set specific conditions for sending form data to Dropbox, then check the 「Enable Condition」 box and fill out your required criteria.Click the Save Settings button to save your options.

Feed Settings Screenshot

Creating a Feed for the EmailOctopus Add-On

SummaryPre-requisitesSteps to Create a FeedFeed Settings Screen

Summary
Before the EmailOctopus Add-On can be used with Gravity Forms, you will first need to create a feed. Your feeds allow you to integrate a form with your EmailOctopus account and feed user information in real time to their service when a form is submitted. This allows you to automatically add subscribers to your list at form submission.
Pre-requisites

You have completed setup the EmailOctopus add-on, including registering the API key.
You should already have a form setup within GF that you wish to use as the source of feed submissions.

Steps to Create a Feed
If all pre-requisites are complete, do the following from your WordPress Admin Dashboard:

Click on Forms in the left side menu.
Select the form that you want to use with EmailOctopus.
Once within your desired form, hover over Settings and click on EmailOctopus.
Click Add New to create a new feed. You will be presented with the EmailOctopus feed settings screen. See below for information on the fields presented there.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshot below.

A Feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
Select the EmailOctopus List you would like to add the subscriber to. The drop-down should offer the lists already setup within your EmailOctopus account.
Map Fields: Map each of the list fields to the desired form field that you wish to be the source for that information.
Conditional Logic: If unchecked, every successful form submission will be sent to EmailOctopus. If you wish to set specific conditions for sending form data to EmailOctopus, then check the 「Enable Condition」 box and fill out your required criteria.

Creating a Feed for the FreshBooks Add-On

SummaryCreate a FeedFeed Settings ScreenSetup FreshBooks Invoice or Estimate

Summary
Before the FreshBooks Add-On can be used with Gravity Forms, you will first need to create a feed. A feed simply allows form submission data to be sent to another source. In this instance, form data being sent to FreshBooks.
Create a Feed
To create a feed for FreshBooks using the FreshBooks Add-On for Gravity Forms, do the following from your WordPress Admin Dashboard.

Click on Forms in the left side menu.
Select the form that you want to use with FreshBooks.
Once within your desired form, hover over Settings and click on FreshBooks.
Click Add New to create a new feed. You will be presented with the FreshBooks feed settings screen.

Feed Settings Screen
The following fields are available within the settings screen. Refer to the settings screenshot below.

A feed Name is required. It is only used for identification and will not be shown anywhere other than your feed listing.
Client Settings: Map the fields on your form with fields available within FreshBooks by selecting your form fields in the dropdowns to the right of each item.
In the Notes field you can define any custom notes you would like to be placed into FreshBooks. This field also supports merge tags to dynamically generate content. To view the available merge tags, click the icon to the right of the field.
Invoice/Estimate Settings: Create an invoice or estimate within FreshBooks when the field is submitted. For more information on these, take a look at our Invoice/Estimate Settings in Freshbook Add-On Feeds article.
Conditional Logic: If unchecked, every successful form submission will be sent to FreshBooks. If you wish to set specific conditions for sending form data to FreshBooks, then check the 「Enable Condition」 box and fill out your required criteria.
Click the Update Settings button to save your options.

Setup FreshBooks Invoice or Estimate
One of the options available when setting up a FreshBooks Feed is the ability to create an invoice or estimate when a form is submitted. This is an optional step that will allow you to jumpstart the invoice or estimate process by creating one when a form is submitted. This will allow you to then go into FreshBooks and complete the invoice or estimate, saving you time in the process.
To create an Invoice or Estimate follow these steps:

Select 「Invoice」 or 「Estimate」 from the 「Also Create」 option when setting up or editing a FreshBooks Feed.
Map the PO Number field to an available Form Field. This is optional.
Set a default discount percentage to apply to any invoice or estimate that is created with this feed. This is optional.
Setup your line items by choosing fixed costs and quantities, or opt to pull costs and quantities from available form fields. You an add additional line items by clicking the plus icon. This is optional.
Enter default invoice or estimate notes.
Enter the default terms for the invoice or estimate.
Now that you have setup a FreshBooks feed, when the form you selected is submitted, it will automatically send the data you have selected to FreshBooks and automatically create (or update) a client, invoice, or estimate.

Centering an Entire Form

Here』s a quick CSS snippet used to center an entire form. Replace 2 in #gform_wrapper_2 with the id of your form.

/* keep it mobile friendly by only applying these styles for larger viewports */
@media only screen and (min-width: 641px) {

body #gform_wrapper_2 {
max-width: 50%;
margin: 0 auto;
}

body #gform_wrapper_2 .gfield .ginput_container,
body #gform_wrapper_2 .gfield .gfield_description,
body #gform_wrapper_2 div.ginput_complex label,
body #gform_wrapper_2 input:not([type='radio']):not([type='checkbox']):not([type='submit']),
body #gform_wrapper_2 select,
body #gform_wrapper_2 textarea {
text-align:center;
}

body #gform_wrapper_2 .top_label .gfield .gfield_label {
text-align: center;
display: block;
}

body #gform_wrapper_2 .gform_footer,
body #gform_wrapper_2 .gform_page_footer{
text-align: center;
}

}

Reference: Where to Put Your Custom CSS

If using any caching solution, be sure you have flushed the cache and turned it off while making CSS changes.

Chained Selects Change Log

1.5 | 2020-09-241.4 | 2020-05-111.3 | 2019-08-071.2 | 2019-05-151.11.0

1.5 | 2020-09-24

Added support for Gravity Forms 2.5
Fixed an issue with cache expiration when using the gform_chainedselects_import_file filter.

1.4 | 2020-05-11

Added translations for Hebrew, Hindi, Japanese, and Turkish.
Fixed an issue where the import stalls with the spinner displayed if the uploaded csv contains malformed UTF-8 characters.
Fixed an issue with Gravity Forms 2.4.15.5+ where the placeholder choice is replaced with a duplicate first choice when the select is populated by the Ajax request.
Fixed an issue where dynamic population parameter names are lost when re-importing the csv file.
Fixed choices being imported from the csv file with leading and trailing spaces which could prevent the selected choice being saved on submission.

1.3 | 2019-08-07

Added security enhancements.

1.2 | 2019-05-15

Updated the entry list page field filters to include a choice for each select instead of one choice for the entire field.
Fixed an issue where Chained Selects conditional logic is evaluated for any field with the matching ID when multiple forms are on the page.
Fixed a PHP notice which can occur when using the gform_chained_selects_input_choices filter and the choice isSelected property is not defined.
Fixed an issue where pre-selected choice in first dropdown does not correctly populate choices in second dropdown.
Fixed a PHP warning on form display when the {all_fields} merge tag is used in the review page content.
Fixed calculations and conditional logic not being triggered when the isSelected property is enabled for a choice using the gform_chained_selects_input_choices filter.
Fixes issue where input names are overwritten when import file is re-imported.

1.1

Added index parameter to gform_chained_selects_input_choices filter.
Added gform_chainedselects_column_unique_values_limit filter to bring the gravityformschainedselects_column_unique_values_limit filter inline with RG naming conventions.
Added support for better error messages when uploading a CSV for a Chained Selects field.
Added support for honoring isSelected field on chained select choices (can only be set programmatically).
Added GPL to plugin header.
Updated file import filter feature to not cache empty files (preserving existing choices).
Updated Plugin URI and Author URI to use https.
Fixed issue where a chained select with no choices used the first select's choices.
Fixed an issue where the wrong choice could be selected when the field is redisplayed post paging.
Fixed a PHP fatal error which could occur when conditional logic evaluation is triggered by GravityView.
Fixed an issue where choice values of 0 were not imported resulting in some choices appearing in the wrong drop downs.
Fixed issue with chunking file uploads (introduced in GF 2.3).
Fixed issue where choice values were not properly sanitized when populating the next select's choices.

1.0

Updated output of field value in entry detail and all fields merge tag.
Fixed conditional logic support; miscellaneous bugs.
Added support for Chained Selects conditional logic on Notifications and Confirmations.
Fixed issue with poorly formatted import file.
Fixed a timing issue with the inclusion of the GF_Chained_Field_Select class.
Fixed issue where unsaved changes warning showed even after clicking update.
Updated choice UI to include left and right facing arrows to better indicate navigational direction between drop downs.
Update drop down preview to be clickable; navigates to the select drop down edit view.
Added warning if deleting choice with children.
Updated "Choices" field setting label to match new styling in GF2.0.
Added confirmation prompt if modal is closed with unsaved changes.
Added "Update" button in Manage Choices modal; data is only saved when Update button is clicked.
Added support for resizing vertically-aligned chained selects based on largest select.
Updated "Add Choices" label to "Manage Choices".
Updated modal styles and resizing behavior when new choices and drop downs are added.
Fixed issue where chained selects with "Hide Inactive Drop Downs" setting disabled would still hide inactive drop downs after first selection.
Everything is awesome!

Chained Selects Field

SummaryCommon SettingsAppearanceMore InformationMerge TagsUsageModifiers

Summary

The Chained Selects field is available when using the Chained Selects Add-On. With the proper setup, this field will allow you to create selection fields that will dynamically change based on the previous selection, this creating a cascade of dependent field choices.

Chained Select field as displayed in the Field Library

Example view in the Form Editor

How it would look in Form Preview

Common Settings

This field uses mostly common field settings for the General, Appearance, and Advanced settings. For a description of each of the common field settings, refer to this article. Below you will find descriptions of specialty settings that are particular to this field.

Appearance

SettingDescriptionDrop Down AlignmentSets the alignment of how the chained selects will be displayed (horizontally or vertically).Drop Down DisplayAllows the hiding of inactive dropdowns. If this option is enabled, dropdowns in subsequent steps will only be shown if the prior step has been selected.

More Information

For the process of creating and populating the data for a chained select field, refer to this help guide.

Merge Tags

Usage

{Field Name:2}

Notes:

The first of the merge tag parameters above, Field Name, is optional and is simply the field name for easier identification.The second parameter defines the field ID within the form. In the example above, it would be field ID 2.If accessing a specific option within the field, it can be accessed by separating the values with a period. For example, 2.3 would be the value of the 3rd choice from field ID 2.

Modifiers

This field does not have any modifiers.