This article reviews some of the testing tools that are available for end users of Apps. Not every App that is hosted on cloudconnectors.eloqua.com has every test option outlined below. They are typically found on connectors and feeders (the difference is explained here).

 

NOTE -

This document is not for testing the DEVELOPMENT of Apps. It is meant for end users

 

Accessing the Test Tools

When you are looking at the configurtion window for an app, you will see a series of buttons along hte left hand side. Click on the "Test" button:

test tools.png

 

You will see a potential mix of different tabs, depending on the app you are looking at. The options are as follows:

 

Step Members:

step members.png

This tab shows records that are in the step in Program Builder or Canvas, and what "state" they are in. IF a record appears in a step, but is not represented here, then the Program or Canvas has not executed yet. Clicking the "Refresh counts" button will refresh the number of records in each state.

Awaiting Action - These are records that are waiting for the App to process

In Progress - The app has started processing these records

Complete - The app has finished processing these records (but they are still in the step in PB or Canvas)

 

Under the "Action area, you can select the drop down and change the state of a record to either "Awaiting Action, "In Progress" or  "Complete". You select the option that you would like, and click "Go"

 

Run Manually

Run Manually.png

Run Manually allows you to manually execute the App. It is typically used in both Connectors and Components

You have 2 options:

Dry Run - A dry run executes the call, either on the contacts in a step OR for the relevant contacts in a feeder. There MUST be records in the step within Eloqua. IT DOES NOT modify the data within Eloqua. If there is a per transaction cost with the 3rd party, this will typically NOT use those calls

Full Run - A full run executes the call, either on the contacts in a step OR for the relevant contacts in a feeder. There MUST be records in the step within Eloqua IT DOES modify data within Eloqua. If there is a per transaction cost, it will be incurred.

 

Both run modes display the information back from the third party within the screen. Both only execute off 10 records

 

 

Sample Data

Sample Data.png

Sample Data is typically used with connectors. It allows you to define a contact (which does not need to be within the step in Program Builder or Canvas).

To use, place 1 email address per line. A contact MUST exist in Eloqua with the email address that is inputed.

By default, Sample Data runs as "Dry Run" mode above (where data is displayed, but not committed to Eloqua). If you want to have the data pushed to Eloqua, click on the "Full Run" button.

Click "Test Contacts" in order to execute.