Campaign folders are nodes in the explorer tree. Based on their type, they contain certain types of data.
A view is a specific folder which does not contain any data but displays data that is physically stored in other folders of the same type. For example, if you turn a delivery folder to a view, this folder will show all the deliveries. This data can then be filtered.
To distinguish views from standard folders, their name is displayed in light blue instead of black.
Note that you can assign permissions to folders to restrict access to certain data. Learn more
Use built-in folders to make it easier for every person involved in the project to use, maintain and troubleshoot the application. Avoid creating custom folder structures for recipients, lists, deliveries, etc., but use the standard folders such as Administration, Profiles & Targets, Campaign management.
Create sub-folders, for example save your technical workflows under the built-in folder: Administration > Production > Technical Workflows, and create sub-folders per workflow type.
Define and apply a naming convention, for example you can name the workflows in alphabetical order, so that they appear sorted in the order of execution, such as:
A1 – import recipients, starts at 10:00;
A2 – import tickets, starts at 11:00.
To create a folder, right-click on an existing folder and use the contextual menu.
To create the same type of folder than the one you selected, choose the first option in the contextual menu. For example, from a Recipients folder, select Create a new ‘Recipients’ folder.
You can drag and drop the new folder to organize Campaign explorer tree as you need.
To create another type of folder, right-click on an existing folder and select Add new folder. You can create all types of folders, depending on the data to be stored.
These changes apply to all Campaign users.
A view is a specific folder which does not contain any data but displays data that is physically stored in other folders of the same type.
You can turn any folder to a view, but the folder must be empty. Any data stored in the folder is deleted as you turn the folder to a view.
A view displays data and provides access to it, even if the data is not physically stored in the view folder. To have access to the content, the operator must have the appropriate permissions in the source folders, at least Read access.
To grant access to a view without granting access to its source folder, do not grant read access to the parent node of the source folder.
In the example below, we will create a new folder to display only US deliveries, based on their internal name.
Create a Deliveries folder, and name it US Deliveries.
Right-click this folder and select Properties….
In the Restriction tab, select This folder is a view. All the deliveries in the database will then be displayed.
Define the filter criteria from the query editor in the central section of the window: only the deliveries corresponding to the filter are displayed in the folder.
Learn how to design queries in this page
When managing transactional messaging events, the Real time events or Batch events folders must not be set as views on the execution instances, as this could lead to permission issues.
By default, a new folder is added on the top of the hierarchy.
Browse the Sub-folders tab of a folder properties to organize its sub-folders.
You can move the folders with the arrows on the right or select the Sort the sub-folders in alphabetical order option to sort them automatically.
To filter data stored in a folder, access to the folder properties and select the Restriction tab.
For example, the folder below will contain only contacts with an email address and whose origin is not flagged as ‘External’ - or is empty.
Use permissions on folders to organize and control access to Campaign data. Learn more about permissions on folders in this section.