Eloqua Release 19D New Feature Summary Available

Lou Patrick
Lou Patrick Posts: 194 Bronze Trophy
edited Oct 21, 2019 2:57PM in Developer Tools

The Eloqua Release 19D New Feature Summary is now available - Eloqua Release 19D New Feature Summary.

Here is an extract of all the Developer Updates:

APPLICATION APIWe've added new ways you can filter landing pages when using the Retrieve a list of landing pages endpoint:Filter by content sourceFilter by vanity URLFilter by user who created or last updated the landing pageThe Retrieve a list of landing pages API endpoint will now return a landing page's vanity URL (relativePath) at minimal depth.You can now search for forms by content source using the new query parameter contentSource, specifying content source by ID:classic forms = 0responsive forms = 3We've modified the Retrieve a list of activities endpoint so that an email DeploymentId now appears in the response for emailOpen, emailSend, and emailClickThrough activity types. The DeploymentId allows email activities to be associated with a specific deployment.We've made changes to the Landing Pages endpoints so that minimal depth will return relativePath, and using the search URL parameter with name when retrieving a list of landing pages will return matches for name and relativePath.The Form endpoints will now return htmlName at minimal depth.The Classic Design Editor changes are coming in our 20A release (February 2020). Eloqua’s new, fully responsive, Form Design Editor launched with the 19A release (Feb 2019), is now the default form editor for Eloqua. As such, we will be sunsetting some functionality contained in our Classic Form Design Editor in order to maintain a modern, consistent experience for customers.BULK APIResolved an issue where creating activity export definitions and setting maxRecords would correctly create the definition and respect the maxRecords property, however the maxRecords property was not appearing when creating or retrieving the definition. The maxRecords property now appears as expected in these scenarios.Resolved an issue where creating a Bulk API import with the contact fields {{Contact.Field(EmailIsBounced)}} and {{Contact.Field(EmailIsSubscribed)}} would result in an incorrect email status. This issue has been resolved.Documentation enhancement of note: The new Bulk API Best Practices section has become a growing list of best practices when using the Bulk API, such as reusing definitions and how to best retrieve data.