|
1 | 1 | Marketo MA Changelog |
2 | 2 | --------------------- |
3 | 3 |
|
4 | | -Marketo MA 8.x-1.x, 2016-08-31 |
| 4 | +Marketo MA 7.x-1.x, 2016-08-13 |
5 | 5 | ------------------------------ |
6 | | -- Initial 8.x-1.x version created from 7.x-2.x commit eeb522a40cd083973e360ccb5157fa512911b939 |
| 6 | +- drush mma-fields now requires drush 6 or higher and allows display of |
| 7 | + additional field attributes. See 'drush help mma-fields'. |
| 8 | +- #2335897: Hooks added to provide modules an opportunity to modify lead data. |
| 9 | +- #2190655: Introduced Marketo Forms 2.0 tracking method for Webforms. Webforms |
| 10 | + can now override the default tracking method and when using Forms 2.0 can |
| 11 | + specify the Marketo form which should be targeted. |
| 12 | +- #2507733: User Integration now allow mapping core user object fields. |
| 13 | +- #2567255: Resolved undefined property error when saving user object. |
| 14 | +- #2765039: Ensure Marketo javascript is only loaded once. |
| 15 | + |
| 16 | +Marketo MA 7.x-1.5, 2014-08-20 |
| 17 | +------------------------------ |
| 18 | +- #2293425: SOAP request/response XML now included in log on syncLead errors |
| 19 | +- Cleanup additional variables on uninstall |
| 20 | +- Addition of automated testing with Behat and Travis |
| 21 | + |
| 22 | +Marketo MA 7.x-1.4, 2014-08-20 |
| 23 | +------------------------------ |
| 24 | +- No change. Bad version. |
| 25 | + |
| 26 | +Marketo MA 7.x-1.3, 2014-04-21 |
| 27 | +------------------------------ |
| 28 | +- #2137397: Tracking will now be OFF when role visibility is set to |
| 29 | + "Only the roles selected below" and no roles are selected |
| 30 | +- #2135305: Removed mma-get-activity from drush commands and moved functionality |
| 31 | + to improved mma-get-lead command. Activity is now retrieved by adding the |
| 32 | + --activity option to mma-get-lead. |
| 33 | +- #2139977: Corrected issue related to removal of a mapped field from the field |
| 34 | + definition list. When a field is removed, any currently mapped fields will |
| 35 | + remain intact and display as an "Undefined Field (fieldname)". |
| 36 | +- #2140487: Message is now displayed when webform configuration has been saved. |
| 37 | +- #2142243: Permission "administer marketo webform settings" now works properly. |
| 38 | +- #2215199: Undefined index no longer returned on webform submissions with |
| 39 | + unmapped fields. |
| 40 | + |
| 41 | +Marketo MA 7.x-1.2, 2013-11-14 |
| 42 | +------------------------------ |
| 43 | +- Updated README.txt to reflect changes since 7.x-1.1 |
| 44 | + |
| 45 | +Marketo MA 7.x-1.2-beta3, 2013-11-13 |
| 46 | +------------------------------ |
| 47 | +- #2132635: Improved webform configuration experience |
| 48 | + Configuration is now managed on a single page at node/{ID}/webform/marketo |
| 49 | +- Performance improvements for Marketo MA Webform module |
| 50 | +- #2133163: Corrected method for determining active flag |
| 51 | +- #2134953: Fixed undefined variables when SOAP API not configured |
| 52 | + |
| 53 | +Marketo MA 7.x-1.2-beta2, 2013-11-09 |
| 54 | +------------------------------ |
| 55 | +- #2127663: Updated default value of user action triggers to be "on" |
| 56 | +- #2127679: 0 now displayed in column when no webform components are mapped |
| 57 | +- #2127659: Display message when no fields are available to be mapped |
| 58 | +- Refactored where constants are defined |
| 59 | +- #2130395: Resolved undefined index on webform component sort |
| 60 | +- Users with only a single lead activity record and users associated with more |
| 61 | + than one lead will now display lead information properly |
| 62 | +- #2132165: Remove field from fieldmap on delete |
| 63 | + |
| 64 | +Marketo MA 7.x-1.2-beta1, 2013-11-04 |
| 65 | +------------------------------ |
| 66 | +- #2053673: Handle submission structure changes made in Webform 4.x |
| 67 | +- #2062165: Added CHANGELOG.txt |
| 68 | +- #2062181: Create rule action to retrieve lead data from Marketo |
| 69 | + Rule action "Add data to Marketo lead" has been changed |
| 70 | + to "Send lead data to Marketo" and underlying function has changed name |
| 71 | + from "add_lead" to "marketo_ma_rules_action_add_lead". |
| 72 | +- #2066465: Added basic drush support |
| 73 | +- #2068255: Added keyType auto-detection when querying Marketo for lead data. |
| 74 | + Function "_marketo_ma_get_lead" renamed to "marketo_ma_get_lead", it is safe |
| 75 | + to call this function directly. |
| 76 | +- #2067857: Variable marketo_ma_webform_fields_soap is now deleted upon uninstall |
| 77 | +- #2067861: Added ability to view lead and activity information for a given user |
| 78 | +- #2123391: Modified marketo_ma_add_lead function to pass marketoCookie param |
| 79 | + _mkto_trk cookie value will now be sent to Marketo when using either of the |
| 80 | + SOAP methods and the request to save the lead was made by either an anonymous |
| 81 | + visitor or by the lead updating their own data. |
| 82 | +- #2126019: Added settings for including or excluding tracking based on user role |
| 83 | +- Reorganized admin settings form to use vertical tabs and display more |
| 84 | + information related to webform configuration. |
| 85 | +- #2123395: Added default rules which can be used as examples or extended to do |
| 86 | + something more useful, perhaps adding more data to the list of values being |
| 87 | + sent. If using the marketo_ma_user module these three rules should not be used |
| 88 | + as they duplicate functionality already in place. |
| 89 | +- #2126709: The marketo_ma_user module now allows for mapping user fields to |
| 90 | + Marketo fields and defining which events should trigger updates. |
0 commit comments