Eloqua Release 19A New Feature Summary Available

Lou Patrick

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

Here is an extract of all the Developer Updates:

NEW FEATURESApplication APIAdded a new Audit Log API endpoint to initiate an Eloqua audit log export using the Application API. This API endpoint enables you to specify the type of audit log you want to export within a specified date and time range. If the request is successful, a report will be sent to the email address specified in the request. Previously, initiating audit log exports were only accessible in Eloqua or using an SFTP server after exporting.A new property has been added to the Contact Fields API endpoints. The showTrustedVisitorsOnly property is a boolean that determines whether or not a contact field is displayed only to trusted visitors. A trusted visitor is a contact who has undergone an additional form of verification. A contact field where this property is set to true will only be displayed to trusted visitors.Bulk APIWe've added a new activity field that enables you to filter on the date and time a visitor was linked to a contact. This activity field is available when creating an activity export definition for page view or web visit activity types. Activity records are only returned when linked to a contact. Previously, to export all newly linked activity records, an export as far back as an activity is meaningful would need to be performed to capture newly linked records. With LinkedToContactDate, newly linked activity records can efficiently be exported without exporting activities that have already been exported. The syntax for the new LinkedToContactDate activity field is:{{Activity.Field(LinkedToContactDate)}}

       When export data is retrieved, the LinkedToContactDate will be populated with the date and time the contact was linked to a visitor.

PLATFORM NOTICES

The API endpoints for emails, landing pages, and forms are undergoing changes in updates 19B and 19C as part of the Classic Design Editor Sunset. As of update 19B, the API endpoints will not allow you to create classic emails and landing pages (request body for htmlContentwith 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 htmlContent with a type of 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. For the forms API endpoints, you will still be able to use the API to create and update classic forms. As of update 19C, all API endpoints will not allow creating and editing classic emails, landing pages, or forms. Any forms created with the API endpoints will need to be responsive. A future Product Notice will provide details on usage. For more information about the classic editor sunset, see the product notice.

RECENT CHANGES

• Oracle Eloqua deprecated TLS 1.1 on January 18, 2019. Learn more

Application API

• Resolved an issue with the Application 2.0 Custom Object API endpoints where retrieving and updating a custom object with a custom object field name greater than 50 characters would truncate the name value to 50 characters in the response. With update 19A, if the custom object field name is greater than 50 characters, there will be a validation error.
• The API endpoint to retrieve a list of activities will now only return EmailContent when depth is set to complete. The default depth for this endpoint is complete, and remains unchanged. Set the depth to minimal in the request URL to have EmailContent not returned.
• Resolved an issue where using the Application 1.0 Accounts API endpoint to find matching accounts based on a search parameter would not return all of the account fields in the response.
• The ability to mark forms as internal so that form submissions are dropped, is now available in Controlled Availability. This feature includes the addition of a new property to the Form API endpoints. You can request access to this feature by submitting a request to My Oracle Support.

Bulk API

• Resolved an issue where creating an activity export definition with ReferrerUrl in the filter would cause the export sync to fail. With update 19A, a validation error will be returned if trying to use ReferrerUrl in the filter of a page view export definition.
• The Campaign Response endpoints are now Generally Available. These endpoints enable developers to access campaign responses, to support the specific use case of updating a campaign response status in CRM via an App on Program or Campaign Canvas. These endpoints can only be used by an App service instance selected in Response Rules setup, and cannot be accessed otherwise. With this feature, the Campaign Responses Data Source for listeners will also be Generally Available.
• Resolved an issue where a Bulk API import that did not include C_EmailAddress within fields and isUpdatingMultipleMatchedRecords was set to true, did not successfully update matching records.

DOCUMENTATION ENHANCEMENTS OF NOTE

We have added a new tutorial that explains how to use the Campaign API endpoints to create a detailed campaign with steps.

There is a new campaign element reference page. This topic lists the JSON objects needed to create campaign steps when creating campaigns using the Campaigns API endpoints.

KAHDOUCHE

since this last release when i add picklist (checkbox/Rdaio buttons), to my form, in the landing page this one is not appearing ?

please kindly advise on this .

Lou Patrick

since this last release when i add picklist (checkbox/Rdaio buttons), to my form, in the landing page this one is not appearing ?

please kindly advise on this .

Is this happening via API? If so, please provide the request payload, and I'll take a look.

Mateusz Dabrowski

There seem to be some weird parts around the new Responsive Form Editor.

The fact that we can make checkboxes required without javascript is great, but it seems that despite UI shows only required validation, in the backend Eloqua is enforcing also HTML/URL Validation without any possibility to change via UI (for example to translate the message). Not a huge problem as this is for checkbox field, but still. The simillar weird thing is separate form field for Field Validation isEmailAddressCondition, which might make scripting around field counts a bit harder.

The bigger issue is that there is no option to create a template from the new editor, meaning that we cannot make the full transition to it.

A bit worrying is also the number of small changes (like the addition of guid or formJson part) that might make automated creation of Forms much harder.

On the other hand, good to see finally normal checkbox dataType.

Lou Patrick

There seem to be some weird parts around the new Responsive Form Editor.

The fact that we can make checkboxes required without javascript is great, but it seems that despite UI shows only required validation, in the backend Eloqua is enforcing also HTML/URL Validation without any possibility to change via UI (for example to translate the message). Not a huge problem as this is for checkbox field, but still. The simillar weird thing is separate form field for Field Validation isEmailAddressCondition, which might make scripting around field counts a bit harder.

The bigger issue is that there is no option to create a template from the new editor, meaning that we cannot make the full transition to it.

A bit worrying is also the number of small changes (like the addition of guid or formJson part) that might make automated creation of Forms much harder.

On the other hand, good to see finally normal checkbox dataType.

Thanks for the feedback!

FYI @Piyush Kumar Eloqua-Oracle