change_history Add-On Framework
Defining Minimum Add-On Requirements
As of Gravity Forms 2.2, add-ons can now easily define requirements that are needed before the add-on can be used. Defining requirements are as simple as overriding the minimum_requirements function in the GFAddOn class.
IntroductionThe generic_map field type, part of the _autolink_settings-api, allows the user to map custom keys to custom values, based on submission or other data.
In some cases, you may want to process a feed asynchronously. The gform_is_feed_asynchronous filter will allow you to do so.
DescriptionThe $_async_feed_processing property allows you to define a feed as asynchronous. By using this property, the feed will be processed asynchronously instead of at the same time other feeds are.
DescriptionThe $redirect_url property defines the URL that a user is redirected to upon submitting the form. This value is typically the location of a payment gateway to complete payment.
DescriptionThe $_supports_callbacks property defines if your payment add-on supports callbacks. By enabling this property within your payment add-on, you can easily receive and process callbacks.
DescriptionThe $_requires_credit_card property allows you to easily define if a credit card field is required by a payment add-on.
The gform_addon_field_map_choices filter can be used to override the choices available in the field map drop down.
The simple_condition Helper
IntroductionWhen using the _autolink_settings-api there may be times when you need a field type which allows the user to define a simple conditional logic rule, that's where the simple_condition() function helps.
DescriptionAdds action links to feed items. SLUG is replaced with the add-on slug.Usage[php] add_filter( 'SLUG_feed_actions', 'your_function_name' ); [/php].