Skip navigation

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

 

Here is an exert of all the Developer Updates:

NEW FEATURES

 

Application API

  • You can now use the Landing Pages Application API 2.0 endpoints to create, update, retrieve, and delete landing pages.
  • You can now use the Forms Application API 2.0 endpoints to create, update, retrieve, and delete forms.
  • You can now use the Form Data Application API 2.0 endpoints to create, retrieve, and delete form data.

 

PLATFORM NOTICES

 

App Developer Framework

  • There is now a Scheduling option available for app action steps on Campaign and Program Canvases. If a user sets certain days and hours under Scheduling, records that enter the step outside of the selected days and hours, will remain in an “Awaiting action” status until within the selected days and hours, at which time the Notification URL call will then be sent to the app.
  • The ability to mark forms as internal so that form submissions are dropped, will be in Controlled Availability in Eloqua Release 18D and 19A. This feature includes the addition of a new property to Form API endpoints. You can request access to this feature by submitting a request to My Oracle Support.
  • Oracle Eloqua will be deprecating TLS 1.1 on January 18, 2019. Learn more

 

RECENT CHANGES

 

Authentication

  • Resolved an issue where calls to Eloqua's OAuth 2.0 token endpoint would return an empty response body if there was an error with the request. Error requests made to Eloqua's OAuth 2.0 token endpoint will now return a detailed message. The token endpoint is https://login.eloqua.com/auth/oauth2/token.
  • We modified the Eloqua OAuth 2.0 authorization flow initiation to only accept one initiation per minute for any given user of an app. For more information, see the product notice on Topliners.

 

Application API

  • The processingStepErrors property has been added to the response to submitting a form using the Application 1.0 and 2.0endpoints. This property was previously in Early Preview status in Release 18C. This property provides more detailed information about form processing step errors. For more information, see the product notice on Topliners.
  • A new form field validation property has been added to the Application 2.0 Form endpoints called PreventXSSCondition. This field validation is being added to prevent form data from being saved if HTML is present in a field. For more information, see the product notice on Topliners.
  • The requirement property has been added to the response when submitting form data with invalid values using the Application 1.0 and 2.0 endpoints. This property provides more information about invalid form data being submitted to a form field. See the Eloqua Help Center for more information about form field validation.
  • Resolved an issue where a campaign import could modify the end date of a campaign that is Completed or Active, causing campaigns to end before the intended end date. Campaign imports will no longer be able to modify the end date of campaigns that are Completed or Active.
  • As mentioned in the Eloqua 18C changelog, the resendLimit property introduced in 18A was removed from the processingSteps type FormStepSendEmail for Application API Form endpoints. For more information, see the product notice on Topliners.
  • As mentioned in the Eloqua 18C changelog, the Create an external activity Application API endpoint will no longer create External Asset Types or External Activity Types if they do not exist. A new Action Permission, "Register External Activities", is required to use the Create an external activity Application API endpoint. Learn more

 

Bulk API

  • You can now include Contact.Id for Bounceback, Subscribe, and Unsubscribe activity export definitions. This enhancement enables developers to include Contact.Id on export definitions for all activity types.
  • You can now include user fields for EmailOpen, EmailClickthrough, and EmailSend activity export definitions. One use case this enhancement enables, is allowing including sender and user attributes on email activities exported via the Bulk API, so that the activity can be properly assigned to the correct user in CRM. Discover user fields using the Retrieve a list of user fields endpoint: GET /api/Bulk/2.0/users/fields. User fields can be added with the following statement: {{Activity.User.Field(<Field Name>)}}

Filter Blog

By date: By tag: