Oracle Eloqua Developer Release Notes - 23A

Lou Patrick

A list of developer-facing new features, significant recent changes, and platform notices for Oracle Eloqua release 23A:

Application API

• Retrieve visitor data change: When retrieving visitor data using the Retrieve visitor data Application API 2.0 endpoint visitorId will now be a BigInt. Previously, visitorId was an Integer.
• Eloqua Form Application API changes: When a form is created, updated, or retrieved using the Application API 2.0 endpoints, the response body will return all mapped and unmapped fields present on the form for the processing steps to update Contacts, Accounts, and Custom Objects with form data. Previously, only fields included within the processing steps when the form was created or updated were returned by the response body. For more information, see the product notice.
  • The following Application API 2.0 processing step endpoints are impacted:
    • Create a form POST /api/rest/2.0/assets/form
    • Retrieve a form GET /api/rest/2.0/assets/form/{id}
    • Update a form PUT /api/rest/2.0/assets/form/{id}
    • Partially update a form PATCH /api/rest/2.0/assets/form/{id}
  • The following processing step types are impacted: 
    • "type": "FormStepCreateUpdateContactFromFormField"
    • "type": "FormStepCreateUpdateAccountFromFormField"
    • "type": "FormStepCreateUpdateCustomObjectFromFormField"
• 409 Concurrent Form Update Error: Multiple concurrent updates for forms using the Oracle Eloqua UI or the Application APIs 1.0 and 2.0 endpoints will now be prevented. A 409 Conflict response will be returned via API, and in the UI a warning box will appear. For more information, see the product notice.
  • The following endpoints now return a 409 Conflict response:
    • Update a form version 1.0 PUT /api/REST/1.0/assets/form/{id}
    • Update a form version 2.0 PUT /api/rest/2.0/assets/form/{id}
    • Partially update a form PATCH /api/rest/2.0/assets/form/{id}

See the Changelog for more details and examples.