Eloqua Release 19B New Feature Summary Available

Lou Patrick

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

Here is an extract of all the Developer Updates:

NEW FEATURESApplication APIAsynchronous form processing via API is released under our Controlled Availability program.IMPORTANT: You can request access to this feature by submitting a request to My Oracle Support. A future Product Notice will provide details.A new property has been added to the Application 1.0 and 2.0 Custom Objects API endpoints. The deleteLinkedCustomObjectData property is a boolean that determines whether or not custom object records are deleted when linked contact records are deleted. Does not apply to records that are unmapped or account deletion. Deleting records is irreversible and data cannot be recovered. The default value is false.IMPORTANT: This feature is released under our Controlled Availability program. You can request access to this feature by submitting a request to My Oracle Support.Bulk APIWe’ve added two new activity fields: WebVisitSavedId and PageViewSavedId. WebVisitSavedId is available when creating an activity export definition for web visit activity types to include the id of when web visits were saved. PageViewSavedId is available when creating an activity export definition for page view activity types to include the id of when page views were saved. You can use the new activity fields in the activity export definition filter to successfully export web visit and page view activities periodically without missing any.The syntax for the new activity fields:               WebVisitSavedId: {{Activity.Field(WebVisitSavedId)}}               PageViewSavedId: {{Activity.Field(PageViewSavedId)}When export data is retrieved, the WebVisitSavedId will be populated with the unique identifier for when the web visit was saved, and PageViewSavedId will be populated with the unique identifier for when the page view was saved.PLATFORM NOTICESAs of release 19C, all API endpoints for emails and landing pages will not allow creating and editing classic emails and landing pages. Classic forms will still be allowed to be edited through release 20A, but no new classic forms will be allowed to be created starting in 19C. Any forms created or updated with the API endpoints will need to be responsive starting in 19C. A future product notice will provide details on usage. For more information about the classic editor sunset, see the Email and Landing Page product notice and the Form product notice.With the arrival of Eloqua release 19C (Aug 2019), Oracle will be modifying its supported cipher suites used for Transport Layer Security (TLS) connections to Eloqua. This includes programmatic access to Eloqua via APIs. Learn moreRECENT CHANGESApplication APIAs part of the Classic Design Editor Sunset, the API endpoints will not allow you to create classic emails and landing pages (request body for htmlContent with a type of StructuredHtmlContent). However, you can still use the API to edit emails and landing pages. Any new emails and landing pages created using the API endpoints should have a request body for htmlContentwith a type of RawHtmlContent. If this is not specified, the API endpoints will still default to creating new emails and landing pages with RawHtmlContent. Creating emails or landing pages with the htmlContent type ResponsiveHtmlContent is not supported. If you use the ResponsiveHtmlContent type, we cannot guarantee your email or landing page will be responsive. As of release 19C, all API endpoints for emails and landing pages will not allow creating and editing classic emails and landing pages. Classic forms will still be allowed to be edited through release 20A, but no new classic forms will be allowed to be created starting in 19C. Any forms created or updated with the API endpoints will need to be responsive starting in 19C. A future product notice will provide details on usage. For more information about the classic editor sunset, see the Email and Landing Page product notice and the Form product notice.A new property, isHidden, that stores the “Form Visibility” form setting, was added to the Application API Form endpoints. For more information, see the product notice.Bulk APIResolved an issue where performing an activity export for Subscribe, Unsubscribe, and Bounceback activity types using the statement {{Activity.Field(EmailAddress)}} could result in email addresses being returned in a case different than the case set on the contact currently. Performing an activity export for these activity types, and using this statement, will now return email addresses in the current case of the contact.Resolved an issue where creating an activity import sync and then syncing invalid data to the import definition would result in the sync status being active instead of error.Optimizations have been made to Bulk API custom object imports that include a large number of fields and records.Bulk API Contact export definitions with an EXISTS() Segment filter, e.g. EXISTS('{{ContactSegment[<id>]}}'), will only allow up to two system updated or created date criterion. For more information, see the product notice.