Develop an Oracle Eloqua app menu service
The menus service is all about context. With menus, you can build an App that enables a marketer to launch an externally-hosted application from within Eloqua via a menu dock. This menu dock floats on the right side of the screen in the Eloqua's Campaign Canvas or the asset editor screens. When a marketer clicks on your menu app, Eloqua calls out to your service via the action URL, passing along context-specific data to your app.
Suppose AwesomeApp has a menu service. When a marketing user clicks on AwesomeApp, they are directed to the callout URL: https://example.com/awesome/callout. The call can include contextual information for your app to use. Available attributes include:
siteIdandsiteName: these describe the Eloqua "site", generally the company or organization of the useruserIdanduserName: the Eloqua username and id for the user who selected the menu serviceuserCulture: the linguistic profile of the user. Eloqua uses Microsoft’s CultureInfo class to define culture. For example, for English (United States), the code isen-US; for French (Canada),fr-CAassetIdandassetName: the ID and name of the asset that the user was viewing when they opened the menuassetType: the type of asset, that the user was viewing when they opened the menu. Assets include account, campaign, contact, landing page, template, and so on.
The actual call to AwesomeApp would then resemble:
GET https://example.com/awesome/callout?siteId=123&siteName=Eloqua&userId=1234&userName=Docs.Example&userCulture=en-US&assetId=4&assetName=Docs%20Example%20Campaign&assetType=Campaign
Eloqua signs all outgoing calls with OAuth 1.0a so the receiving system can validate that the call was sent by Eloqua. Refer to the OAuth 1.0a spec or OAuth 1.0 RFC for more information.