Appendix – Transporter Sync

List of Supported and Unsupported Assets

The following lists the supported & unsupported child assets for a specific asset. Please note that for Unsupported assets, user action is required in the target.

* All the steps that is marked with “*“ will have a status of ‘Action Required’ upon deployment.  This means that the users have to complete the recommended actions in the target instance.

NOTE: This will only happen if the asset that the component is pointing to is not in the target instance..

Data Access Policy for the Transporter Sync App

This document explains what data gets read or written to in a client’s instance

The Transporter Sync app doesn’t touch the PII (Personally Identifiable Information) data from your instance – at all.

The app needs to move an asset and associated assets across instances, it needs to read the data related to that asset. Under the hood, this app is moving the metadata across instances. The app reads the metadata from the source instance, and hence needs only read access – and since the app writes to the destination instance, it needs read and write access in the destination instance.

So, what does it read and write?

Each asset is of a different nature. For example, an email contains both content & meta-data, but a campaign contains no content but configurations of the flow of the campaign. So, the following table helps us know the specifics.

Asset Transporter Sync

Known Issues Transporter Sync

Here are some of the known issues with Transporter Sync, and how to resolve them:

Refresh Token Expired

The Error / Warning

Here is a sample of the error that we may see when the Refresh Token Expires.

It could ask us to: contact your administrator to reinstall the application. And if you know how to reinstall, you don’t need the rest of this doc – that’s exactly what we need to do to fix this issue.

The Why: Why we see this warning?

Portqii’s Transporter Sync app communicates to Eloqua using the industry standard OAuth 2.0.

This process includes managing two types of tokens:

• Access token, and
• Refresh token.

Access tokens expire in 8 hours and Refresh token expire in 365 days.

Upon expiration, a new access token can be generated by using a refresh token.

Generating a new access token generates a new refresh token which is to be stored in the application. The two tokens are cyclic and interdependent.

If the refresh token is corrupt (for reasons unknown), then we see this warning/error message.

Reference: Here is a detailed doc from Oracle about OAuth.

The Solution: What can we do about this?

The most bankable solution for this error is to: Reinstall the Application.

The Who: Who should reinstall this application?

Only the Eloqua admin who has access to adding and removing applications can carry out the steps of re-installation.

The How: How should we reinstall the application?

Here are the steps to reinstall Transporter Sync:

Step 1: Click on the Gear Icon (Settings)

Step 2: Click on the Apps link in the Platform Extensions section.

Step 3: Search for the App by using the Search Box:

Step 4 : Click the app that needs to be re-installed – and then click on the Down Arrow (Re-Install)