Cruise Control

If the User is 100% sure that the actions and alternate assets for dependency management and removal can be from the default settings in the admin page, and doesn’t want to go through the Manage Dependency process, then the User can go for Cruise Control option. Cruise Control is a single click Dependency Management and Clearing process that applies actions from admin page and removes the dependencies. Cruise Control is very powerful and fully automated process of Dependency Management where the User just adds the asset whose dependencies have to be removed and takes a decision whether to only clear the asset’s dependencies or clear it’s dependencies along with deletion of the asset from Eloqua. 

To remove Dependency using Cruise Control:

  1. Once the assets are selected into the package, click on ‘Save’.

  1. Switch on Cruise Control.

  1. Once Cruise Control is switched on, the User can select ‘Manage & Clear’ or ‘Manage & Delete’.

‘Manage & Clear’ will apply the actions and alternate assets from default settings and will clear all the dependencies. This process will not delete the asset whose dependencies are being removed, from Eloqua. Whereas ‘Manage & Delete’ will do the above and also delete the asset whose dependencies are being removed, from Eloqua. The actions and the alternate assets for managing and clearing the dependencies will be picked up from the default settings in the admin page of the app. 

Eg: Admin settings for managing Email’s dependency:

After applying the actions and alternate assets from Admin Settings, the Clear Dependency process will complete the Dependency process. 

Managing Asset Dependency on a Completed Campaign #

If an asset’s dependency is a Campaign that has status as ‘Completed’, then it’s dependency can’t be removed as the Completed Campaign cannot be edited. This is as per Eloqua design. The only way to remove dependency is if the Completed Campaign can be deleted from Eloqua. So the User is given the following options:

  1. To add the Campaign automatically into package.
  2. To add the Campaign manually by the User 

If the User wants to a controlled yet automatic addition of Completed Campaigns, then the User must select the folders from which the Completed Campaigns can be included into the Package. The app only adds those Completed Campaigns if they are in folder listed by the User.

Selection of ‘Include All Folders’ means that the application can add all the Completed Campaigns listed as dependencies into the package automatically. 

If no folder is selected in the Admin, then the application won’t add the Campaign automatically. User can click on ‘Manage Dependency’ for that asset and click on ‘Add to Package’ for that dependency. 

Once the Completed Campaign is added to the package, the User can click on ‘Manage & Delete’ to delete the Completed Campaigns. 

Example: To Remove dependency of a Segment where Completed Campaigns are it’s dependency. The folder ‘TRX_D_Campaign_Folder’ has been included in the Admin settings.  

  1. Add Segment into the package using Asset Dependency Manager. Click on Cruise Control. Click on Manage & Delete.
  1. Once the process is complete, the status of the Segment will change to ‘Delete Unsuccessful’ since the dependency couldn’t be removed due to Completed Campaigns. Note that the Completed Campaign that is present in TRX_D_Campaign_Folder only gets added automatically into the package and not the other Completed Campaigns.  

Clicking on Manage Dependency for Segment shows the other Completed Campaign that was not added to the package since it was not in the specified folder. 

  1. To continue the process of deletion, the Use can click on Manage Dependency for the Campaign OR ‘Manage & Delete’ in case of Cruise Control. This will manage the dependency of Campaign and delete both the Completed Campaign and the Segment. In this case, since Segment still has dependency on the other Complete Campaign which hasn’t been removed, the Segment will not be deleted.