Marketo Form Profile Service

[yesil]

This is about enhancing Marketo Form component with:

• A Profile URL that;

  • will be defined in the cloud config
  • will be called via XHR at the frontend during form rendering
  • will return the list of unknown fields in a given form, so that all the known form fields can be removed from the form
  • e.g: { "fields": ["Company"] }

• An option to enable Profile Service in the form component dialog

• An option to auto-submit the form if all the form fields are known(pre-filled)

• An alternate verbiage for the submit button in the event all the form fields are known

• A Destination URL to redirect to once the form submission is successful

The form component dialog options should appear only if the Profile URL is defined in the cloud configuration

[yesil]

I would like to use a render condition to display the Profile Service specific options in the form dialog only if the Profile URL is defined in the Marketo cloud config.

The question is if I extend com.adobe.dx.admin.rendercondition.AbstractRenderCondition do I need to put my marketo specific render condition in the admin module in which case I cannot use com.adobe.dx.content.marketo.models.internal.MarketoConfBasicInfo? to map the marketo config.

Alternatively I can add a CloudConfigPropertyRenderCondition in the admin module which will check if a given property is defined in a given cloud config?

Which one is preferable?

[npeltier]

@yesil definitely the later, as it will not break the modularisation.