[MKTAUT-102] DOC: user can configure whether individual fields or forms are used Created: 06/Feb/20  Updated: 26/Feb/20  Resolved: 26/Feb/20

Status: Closed
Project: Marketing Automation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Julie Legendre Assignee: Julie Legendre
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MKTAUT-101 Make selection of fields for form con... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: DOC: Marketing Automation add-ons documentation 1.0
Sprint: Add-Ons 31, Add-Ons 32
Story Points: 2

 Description   

Update module page and overview for change in behavior:

  • Marketo can now be individual field selection.
  • Saleforce can now be form selection.
  • Add subFormId property to config.yaml.
  • Document subform definition (under module/dialogs/subForm.yaml).
  • Bumping up to 2 pts because of possible terminology tweaks.


 Comments   
Comment by Julie Legendre [ 25/Feb/20 ]

https://documentation.magnolia-cms.com/display/DOCS62/Marketing+Automation+module

https://documentation.magnolia-cms.com/display/DOCS62/Marketing+Automation+Connector+Pack

Updated pages with current state of dev. Conversation started in addons room about the location of the config and the subFormId name. Both should change. So text in red in the pages will also be updated.

Comment by Julie Legendre [ 26/Feb/20 ]

Closing this ticket as work is done. Creating another doc ticket to document the dev changes (MKAUT-105) caused by this ticket.

 

Will ask for a review at the end of documenting the following dev ticket.

Comment by Julie Legendre [ 26/Feb/20 ]

Cf MKTAUT-106

Generated at Mon Feb 12 10:12:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.